Hello.
I am trying to debug connection with XDS200USB for F28388D, but the following error has occurred.
When I checked it with the F28335 that I own separately, it worked without any problems, so I think it's a problem between the CPU and the debugger.
Do you know the direct cause?
thank you.
[F28388D&XDS200]
[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\develop\AppData\Local\TEXASI~1\
CCS\ccs1120\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 'Mar 17 2022'.
The library build time was '19:20:23'.
The library package version is '9.7.0.00213'.
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]
[F28335&XDS200]
[Start]
Execute the command:
%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity
[Result]
[Print the board config pathname(s)]--
C:\Users\DDM\AppData\Local\.TI¥693494126\
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 'Aug 20 2013'.
The library build time was '23:33:52'.
The library package version is '5.1.232.0'.
The library component version is '35.34.40.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '12' (0x0000000c).
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.
[Perform the Integrity scan-test on the JTAG IR]-
This test will use blocks of 512 32-bit words. This test will be applied just once.
Do a test using 0xFFFFFFFF. Scan tests: 1, skipped: 0, failed: 0 Do a test using 0x00000000. Scan tests: 2, skipped: 0, failed: 0 Do a test using 0xFE03E0E2. Scan tests: 3, skipped: 0, failed: 0 Do a test using 0x01FC1F1D. Scan tests: 4, skipped: 0, failed: 0 Do a test using 0x5533CCAA. Scan tests: 5, skipped: 0, failed: 0 Do a test using 0xAACC3355. Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.
The JTAG IR Integrity scan-test has succeeded.
[Perform the Integrity scan-test on the JTAG DR]-
This test will use blocks of 512 32-bit words.
This test will be applied just once.
Do a test using 0xFFFFFFFF. Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000. Scan tests: 2, skipped: 0, failed: 0 Do a test using 0xFE03E0E2. Scan tests: 3, skipped: 0, failed: 0 Do a test using 0x01FC1F1D. Scan tests: 4, skipped: 0, failed: 0 Do a test using 0x5533CCAA. Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.
The JTAG DR Integrity scan-test has succeeded.
[End]
