CCS/TMS320F28069: The JTAG DR Integrity scan-test has failed.

Hello,

Are you using a custom board? If so, have you tried to narrow down the problem between hardware and software?

A few other questions,

1) Can I please see your target configuration?

2) Are you able to detect the XDS100 in device manager?

3) Do you have the latest drivers setup in CSS?

Best Regards,

Marlyn

HI,

In addition to Marlyn's suggestions, please check the section Invalid data read back of the Debugging JTAG page below. 

http://downloads.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html  

It also contains several suggestions to troubleshoot the hardware. 

Hope this helps,

Rafael

First of all, thank you very much for your reply!

I am using a  custom  board I made myself.It worked fine when it was used before.

I have checked target configuration，as following:

when i run 'Test Connection',it can be observed as following:

[Start: Texas Instruments XDS100v2 USB Debug Probe]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]

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

C:\Users\Edwin\AppData\Local\TEXASI~1\CCS\
ccs910\0\1\BrdDat\testBoard.dat

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

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusb.dll'.
The library build date was 'Jun 3 2019'.
The library build time was '15:24:38'.
The library package version is '8.2.0.00004'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
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]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the FTDI FT2232 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for FTDI FT2232 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[The log-file for the JTAG TCLK output generated from the PLL]----------

There is no hardware for programming the JTAG TCLK frequency.

-----[Measure the source and frequency of the final JTAG TCLKR input]--------

There is no hardware for measuring the JTAG TCLK frequency.

-----[Perform the standard path-length test on the JTAG IR and DR]-----------

This path-length test uses blocks of 64 32-bit words.

The test for the JTAG IR instruction path-length succeeded.
The JTAG IR instruction path-length is 38 bits.

The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 1 bits.

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 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 64 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: Texas Instruments XDS100v2 USB Debug Probe]

2) I am able to detect the XDS100 in device manager

3）i am sorry for not understanding this question.But my ccs is the latest and XDS100's driver too.

!!!!!!Now,

‘’‘The JTAG DR Integrity scan-test has failed.’‘’ this question has been solved.

But I have a new problem：

Error connecting to the target:
(Error -1041 @ 0xFFFFFF66)
The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation.
(Emulation package 8.2.0.00004)

Please help me!!!

I am glad your initial problem was resolved.

user5285694 said:

I am using a  custom  board I made myself. It worked fine when it was used before.

When you say it worked before, do you mean you used to be able to establish the connection between your board and the debug probe? If so, was this with the same debug probe you are trying to use now?

For the error you are seeing now, is explained here: http://software-dl.ti.com/ccs/esd/documents/ccsv7_debugging_jtag_connectivity_issues.html

The issue can be caused by various factors. The following is what is explained in the document:

A problem in the FTDI chip, bad I/O pins on the debug probe, issues on the circuit between the FTDI chip and the JTAG header, or a problem with the target device.

You can try to workaround or solve this issue by swapping the JTAG debug probe and/or target device or board. In rare cases the FTDI device on the XDS100 debug probe may be broken.

Best,

Marlyn

Yes,i used to be able to establish successfully the connection between your board and the debug probe.i used the same debug Probe and same target board!!!

i have studied this http://software-dl.ti.com/ccs/esd/documents/ccsv7_debugging_jtag_connectivity_issues.html,but my question is not solved!!!