TMS320F28P659DK-Q1: Facing issue while using XDS200 debugger for C2000 Microcontroller TMS320f28P650DK

Hello,

The cable break far message means that CCS can communicate with the debug probe, but there is an issue between the pod and the target. It could be a problem with the cable (connections or damage) or the header on the board.

There is some more information here: https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html#cable-break

Are you able to connect to the board with a different debug probe like an XDS110?  If that works then the header is fine.

Best,

Matt

we have two debuggers with similar issue here is the log of another debugger!

[Start: Texas Instruments XDS2xx USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\SANDEE~1.MOG\AppData\Local\TEXASI~1\
CCS\ccs1271\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 560/2xx-class product.
This utility will load the program 'xds2xxu.out'.
The library build date was 'Sep 26 2024'.
The library build time was '14:57:19'.
The library package version is '20.0.0.3178'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '13' (0x0000000d).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

This emulator does not create a reset log-file.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-233' (0xffffff17).
The title is 'SC_ERR_PATH_BROKEN'.

The explanation is:
The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
with a stuck-at-ones or stuck-at-zero fault.

[End: Texas Instruments XDS2xx USB Debug Probe_0]

Hi,

Can you try resolving the error -233 found on the second debugger? We have debug steps you can follow in the C2000 MCU JTAG Connectivity Debug Guide, specifically Section 4.1.

If we can get the second one working, we can rule out the possibility of a software-related issue with the first debugger (displaying the cable break error).

Best,

Matt

yes, we can able to connect with board with different debugger but not with this one.

I checked 4.1 section and below is my observation:

1 & 3: with another debugger we are able to access Hardware

2. second point is obsolete as facing same issue for 2 pin or 4 pin JTAG,

4. point is also not valid as we can see code is running as communication is working.

Hi,

From my understanding:

You have two XDS200 debuggers (A and B). Debugger A is not able to connect to the device is giving a cable break error (-183). Debugger B is able to successfully connect to the device. 

Since Debugger B is able to connect to the device, that rules out the possibility of an issue with the header on the board. That means there's most likely a problem with the cable (connections or damage) on Debugger A.

Please correct me if I'm not on the same page.

Best,

Matt

yes, we have 5 debuggers in total out of which I am facing issue with 2 debuggers for which i reported error code above and raised concerns. With other debugger i am able to flash the code and debug it. now I want to make two faulty debuggers working. Can you please let us know how we can make the other debugger working.

Hello,

The probes may be defective? What are the vendors of all the XDS200 debug probes (working and non-working)?

all are from BlackHawk

Assuming the below is accurate with the SAME EXACT BOARD:

Matt Kukucka said:

You have two XDS200 debuggers (A and B). Debugger A is not able to connect to the device is giving a cable break error (-183). Debugger B is able to successfully connect to the device. 

I would have to agree with Matt's comment below:

Matt Kukucka said:

That means there's most likely a problem with the cable (connections or damage) on Debugger A.

Hence:

Sandeep Moghe said:

all are from BlackHawk

I would suggest contacting blackhawk support directly: https://www.blackhawk-dsp.com/support

Thanks

ki