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.

TMS570LC4357: The JTAG DR Integrity scan-test has failed on HDK board

Part Number: TMS570LC4357
Other Parts Discussed in Thread: HALCOGEN

Dear all,

Today I have encountered a hardware issue.

While plug in my HDK with power and mini USB, the on board LED DS2,3,4,5 start to blink in random sequence for about 15 seconds, and the D1 error is also blinking at the same time.

After that, DS2,3,4,5 is on as normal, but D1 is in a dim red.

then I could not connect and debug anymore, and the connection verification note is given at the end.

Could someone advise for such a situation?

---------

[Start]

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\yef06104\AppData\Local\TEXASI~1\
CCS\ccs910\0\0\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 failed.
The JTAG IR instruction scan-path is stuck-at-zero.

The test for the JTAG DR bypass path-length failed.
The JTAG DR bypass scan-path is stuck-at-zero.

-----[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.
Test 1 Word 0: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 1: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 2: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 3: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 4: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 5: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 6: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 7: scanned out 0xFFFFFFFF and scanned in 0x00000000.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 1, skipped: 0, failed: 1
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 83.3 percent.

The JTAG IR Integrity scan-test has failed.

-----[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.
Test 1 Word 0: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 1: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 2: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 3: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 4: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 5: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 6: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 7: scanned out 0xFFFFFFFF and scanned in 0x00000000.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 1, skipped: 0, failed: 1
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 83.3 percent.

The JTAG DR Integrity scan-test has failed.

[End]

 

  • some updates:

    I have tried the JTAG debug given by online manual http://software-dl.ti.com/ccs/esd/documents/ccsv7_debugging_jtag_connectivity_issues.html

    After using different cables, laptops and TCLK MHz, it is still the same error 2131.

    Also if I connect my HDK , without any program or task, the CPU becomes hot after about 5 min.

    The rest, from on-board button & CCS do not work anymore.

  • also some updates, recently, everytime I connect the power and mini USB, there is no response at all, and the LEDs show like in the photos

  • Hello,

    Can you please measure the voltage level of core power supply and IO power supply? and measure the current at R140, R142?

  • Hi Wang,

    I have measured the following values from my board A:

    TP14 – 15       -                 0.001V

    TP16 – 17           -             0.008V

    TP18 – 19           -             0.001V

    TP20 – 21           -             0.000V

    TP22 – 23           -             0.000V

    With ground

    TP14      -             1.204V

    TP16      -             3.29V

    TP18      -             1.203V

    TP20      -             3.291V

    TP22      -             5.040V

    Current

    R140 – 0.64 mA

    R142 – 0.37mA

    Then I measured a good working HDK say board B, the only difference is the current:

    R140 – 3.32 mA

    R142 – 2.04 mA

    Is there any hardware issue for board A?

    Regards 

    Lu

  • Hello Lu,

    The core (1.2V) and I/O (3.3V) power supplies are good. It does not make sure to me that the chip becomes hot but the current for core is very small. Can you measure the current at R141 (3.3V), R143 (flash), R144(ADC module)?

  • current mA voltage V
    R141, 3V3 IO, 20M 4.41 0.008 
    R143, 3V3 VCP 20M 0.01 0 (GND to both sides of R143, is 3.291V)
    R144, VADC, 20M 0 0 (GND to both sides of R144, is 5.046V)

    Hi Wang

    please check the measurement above.

    Kind regards.

    Lu

  • Hello Lu,

    You said the chip became hot 5 minutes after powered up. But from the volume of current you measured, I don't see any short circuit on your board. All the power supplies are good.

    Is there any code in the flash? Is there another external emulator plugged onto the 20-pin JTAG header?

  • Hi Wang,

    The last successful load was when  trying to duplicate the HALCoGen example of HET interupt PWM, there was no modification of the sample codes, then the next day, JTAG error occured and nothing can be communicated anymore.

    There is no external emulator, the only connection are the mini-USB and power supply.

    Does a broken D1 LED have impact on the performance ?

    Regards. 

    Lu

  • Hello Lu,

    Please try this procedure to let CPU enter a debug state:

    1. Open the target configuration window, and launch the selected the configuration
    2. Switch to debug window
    3. Press the reset (nRST) button and hold it
    4. Click “Connect Target” immediately after you release the nRST button
    5. The board should be connected after couple tries

  • Hi Wang,

    I have followed your instructions, still the connection failed.

    And it seems the reset button S3 is not working at all. After releasing the button, it fails to connect, with the "IcePick: Error connecting to the target -2131".

    Is there another way to reset the CPU ?

    For details of config, I have a screenshot attached of the debug view.

  • Hello Lu,

    Have you solved the problem?

  • HI Wang,

    I tried as your instruciton, there seems no response at all, even the reset button. Neither did any of the LED's gave response.

    I am currently contacting the local vendor for more details, meanwhile, could you recommend other measures to trouble-shooting this issue?

    thanks a lot

    Lu

  • Hello Lu,

    You said the device got hot 5 minute after it was powered up. Did you feel hurt when you touched the device? I'd like to know how hot it became. 

    Your test message shows that no TCLK, and IR length were detected. I think the JTAG port may be damaged. 

  • Hi Wang

    If for a longer than 5 min, the CPU becomes hurting-level.

    Could the damage of JTAG port lead to phenomena like voltage ref LED blinks in random sequence while connecting ? that was the first thing I saw before it is not connect-able at all.

    And today I tried again, there is no response from any maneuvering .

    Kind regard.

    Lu

  • Hi Lu,

    It depends on how the JTAG signal is damaged. The damage may cause the internal 3.3V short to GND, or cause the pin short to GND or 3.3V. 

  • Hi Wang

    I am no expert in electronics, but according to your opinion, how likely is it to be HW-diagnosed and fixed?

    if not, i will contact my vendor for warranty support, which might be my only option here.

    thanks a lot

    Lu

  • Hello Lu,

    If one of the JTAG pins is internally shorted to GND or 3.3V, it is not fixable. You can monitor the JTAG signals with oscillator if they can toggle when the emulator sends message to MCU.