TMS320F280037: error 1135 @ x0

Part Number: TMS320F280037

image.png

 

I started getting this error out of the blue.  Several weeks into trouble shooting.  I have tried 2 XDS110 and 2 PCB assemblies know to have been working previously, all with the same error.  I rebooted my laptop and tried again with the same results.  

Test connection reports no errors. (see below). 

 

What else do I need to look at?

Thanks

 

[Start: Texas Instruments XDS110 USB Debug Probe]

Execute the command:

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

[Result]


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

C:\Users\truexd\AppData\Local\TEXASI~1\CCS\
    ccs1281\0\0\BrdDat\testBoard.dat

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

This utility has selected a 100/110/510 class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Sep 26 2024'.
The library build time was '10:09:41'.
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 '5' (0x00000005).
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 XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 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).

-----[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 XDS110 USB Debug Probe]

  • Hi, 

    Please take a look at our JTAG Connection debug document. Specifically table 4-1 which states some steps you can take to help debug the issue. 

    Kind regards,
    AJ Favela 

  • These are the debug steps for this error:

    This error message is usually caused by hardware related issues. Verify that VDDIO/VDD are properly supplied. Confirm that XRSn is asserting high, indicating that the device is properly coming out of reset. Long JTAG cables, improper termination, or excessive capacitance can also degrade the JTAG signal integrity as well.

    All of these things are OK. VDD is in spec, XRSn is high and the cable is about 6 inches long.  i've been using this style cable for years without problems.

    Would the test connection pass if these were not ok?

  • Hi,

    Have you made any changes to your .ccxml file between the connection working and failing?

    Additionally, can you place your device into waitboot mode if it isn't already? This can be done by following the table below.

    Kind regards,
    AJ Favela