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.

CCS/TMS320F28377S: XDS510USB unable to properly connect

Part Number: TMS320F28377S
Other Parts Discussed in Thread: TMS570LS3137

Tool/software: Code Composer Studio

I bought an XDS510 galvanically isolated USB JTAG emulator, and can't seem to get it to connect properly.

I'm running Win10 x64, and have the CCSv7 installation with the Spectrum Digital drivers. The Wiki mentions that only the 64-bit versions on Linux and MacOS don't support the XDS510USB and that the Windows version of CCS is 32-bit and does support this debugger.

The error I get while trying to debug from CCS is:

Error connecting to the target:
Error 0x80000240/-2082
Fatal Error during: Initialization, OCS,
Device driver: Emulation Connection Loss Detected on Target CPU.
It is recommended to RESET EMULATOR. This will disconnect each
target from the emulator. The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.

I get this error on both CCSv7.1 and CCSv5.5. This happens in the "configuring debugger" phase, and I can hear the "hardware disconnected" and "hardware connected" sounds chime, like the debugger is being reconnected.

Device manager and SDConfigEx both seem recognize the debugger.

SDConfigEx  "Ports Available" button console output:


** Checking for available USB ports

$$ XDS510USB connected on:
$$ EmuPortAddr=0x510
$$ EmuSerialNumber=S223220035112522

Emulator --> Test console output:

** Using emulation application from directory c:\ti\ccsv5\ccs_base\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

Emulator --> Reset console output:

** Using emulation application from directory c:\ti\ccsv5\ccs_base\emulation\drivers
ERROR >> XDS510USB Reset failed
ERROR >>Emulator failed reset

Both "reset" and "test" give me the "hardware disconnected" and "hardware connected" sounds when clicked.

I get the same errors whether or not there is power to my target CPU (TMS320F28377S).

I have tried two different computers and get the same errors on both.

I have tried removing all versions of CCS and starting with a clean install - same errors.

Any advice is appreciated :)

  • Is the board a custom board or the TI Launchpad? 

    Vishaal Varahamurthy said:
    ** Using emulation application from directory c:\ti\ccsv5\ccs_base\emulation\drivers
    ERROR >> XDS510USB Reset failed
    ERROR >>Emulator failed reset

    This test appears to have been done with the CCS 5.5 installation. Does the emulator reset fail the same way with CCS 7.1 as well? Since the emulator reset is failing, I think the issue is at the JTAG level. I would suggest starting with this page and reviewing the JTAG troubleshooting tips provided there. You can also contact Spectrum Digital as they may have additional tips for troubleshooting their drivers.

  • Thanks for the reply, Aarti.

    - The board is a custom board, but it has been working with an XDS100v2 probe flawlessly for a couple years over multiple versions of CCS. As of today I have tried it on two custom boards that I have been able to program using an XDS100v2 debugger before. The processors I am using are the TMS570LS3137 and the TMS320F23877S. 

    - When I installed CCS5.5 it replaced SDConfigEx with the "old" version. I had tried this out before installing CCS5.5 and got the same error using CCS7.1. 

    - I've been through the troubleshooting tips on the wiki and it seems like none of them are similar to the error I am getting. I'll contact Spectrum Digital and see what tips they have as well.

    Thanks!

  • The problem was on the target boards' JTAG interfaces. For the XDS100v2 debug probe, a 100 ohm current limiting resistor is placed between pin 5 of the JTAG (VCC) and the target power supply 3.3V. The XDS510 pulled enough current to pull the voltage at this pin down by 1V, so it was not reading the correct VCC. Changing the resistor value has gotten it to work.
  • Vishaal,

    Thank you for the update and for letting us know the root cause and fix.