This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SD XDS510USB & C6701

Other Parts Discussed in Thread: TMS320C6720

We are in the process of upgrading out C6701 system from CCS2 (yes, very old) to CCS4. We need to get JTAG working (it was never used with CCS2, so this is the first time we use the JTAG sub-system at all).

We have created what we believe are the right connections, but things are not working (hence this post).  These are the symptoms:

- In SDConfigEx: "jtag ir scan test failed" error

- In CCS: "bad target silicon revision number"

After a lot of review on the boards I could not find a direct solution, only several tips, which I have not quite been able to follow. These are my first set of questions to try to debug this:

- In one post I saw that we should look at the JTAG signals (make sense), and it suggested to put SDConfig in "auto-scan" mode, which would create a constant set of signals in the JTAG data & clock ports, so that we could scope them. Unfortunately SDConfigEx (the "Ex") version, does not seem to have an equivalent mode. So, first big question:

1) What would I expect to see in the JTAG signals with a scope? How do I configure either SDConfigEx or CCS4 to create those signals?

This will allow me to confirm the hardware connections are fine.

Second, the CCS4 distribution does not seem to have a "configuration" for a C6701 in the standard lists of xml's. The SD website says that all drivers are distributed with CCS4, hence I have to come to this forum to ask:

2) What configuration do I use in CCS4 to get the JTAG working with a C6701?

Our configuration process was:

  1. CCS4 -> Target -> New Target Configuration... -> Give it a name -> Finish
  2. Connection -> Spectrum Digital XDS510USB Emulator
  3. Device -> TMS320C6720 (the closest we could find, as the description says "C67x+ Floating-point DSP"
  4. Save
  5. Target -> Debug Active Project [Project compiles, links]
  6. USB Enumaration starts -> get error:

Error connecting to the target:
Error 0x80000200/-1063
Fatal Error during: OCS,
Bad Target Silicon Revision Number
Please check your multi-processor configuration.
The number of devices in the JTAG scan path
must be correct for the silicon revision to be read.
Or, you may have selected the wrong DSP device driver.

We also tried:

  1. New Target -> Advanced Tab -> New -> SD XDS510 USB
  2. Add -> CPUs -> C670x
  3. Save

We get the exact same error.

In SDConfigEx we get (after closing CCS4):

  1. Open -> It finds the SCS510USB@510 immediately
  2. Emulator -> Test

Spectrum Digital Configuration and Diagnostic Utility

Supports:
Printer Port: XDS510PP, XDS510PP+, SPI515, eZdsp
ISA Bus:      SPI510, XDS510
PCI Bus:      SPI525
USB Bus:      XDS510-USB

** Using emulation application from directory c:\program files\texas instruments\ccsv4\emulation\drivers
** Checking for a valid emulator/eZdsp

  $$ You are connected to:
  $$ EmuProductName=XDS510USB
  $$ EmuPortAddr=0x510
  $$ EmuPortMode=USB
  $$ ProductId=510
  $$ ProductVersion=84


** Checking emulator/eZdsp scan connection

** Emulator Test **

 $$ EmuProductName=XDS510USB

 $$ EmuPortAddr=0x510

 $$ EmuPortMode=USB

 $$ ProductId=510

 $$ ProductVersion=84

 ** Emulator Scan Test

ERROR >> JTAG IR scan test failed


  >> Check power to your emulator/eZdsp
  >> Then check your port mode/address

My guess is that we need to check the JTAG hardware connections first, and then we have to deal with the configuration, since at this point there is no JTAG information from the DSP... so if we can start with question 1, that would be great, then we can move on to 2.

Thank you!

Alvar

PS, We need to get the C6701 working because we have these processors aboard the International Space Station, we do not have the luxury to upgrade them!

 

  • Alvar, here's some suggestions...

    First, I would suggest posting this on the Code Composer forum.  The folks monitoring posts there will know the answer straight-away.

    Also, I wouldn't assume 6720 and 6701 are comparable.  So not seeing 6701 ( a very old device) concerns me.

    In CCS 3.3 for example you should see support for C670x to support 6701.

    Can you consider using CCS 3.3 as a test trial?

     

     

  • Re-posted to the CCS forums (took so long because I did *not* get automatic e-mail notification that a reply was sent, oh well).

    Its going to be hard for us to use CCS 3.3, hopefully someone has other ideas either in this forum or in the CCS one.

     

    Thanks,

    Alvar