• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 94 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: 'SC_ERR_PATH_BROKEN'

Praneeth Rao
Prodigy 10 points

Part Number: TMS570LC4357
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

We are using TMS570LC4357 in our custom Boards, and we are flashing through Uniflash with XDS200 USB debug probe, In some of the instances (boards), we are getting the following error in CCS test connection window

[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\pnagesh\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 'Apr 19 2024'.
The library build time was '18:50:34'.
The library package version is '12.7.0.00130'.
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]

and in Uniflash the following error

Once we get this error we are not able to recover this TMS570 at all, it does not allow us to erase, debug or load at all.

Can anyone provide may be the cause and solution to recover?

  • 0
    Prodigy 10 points

    And also we have verified that there are no Hardware or physical damages or faulty connections and all the power rails are proper

  • 0 in reply to Praneeth Rao
    TI__Guru 74696 points

    Hi Praneeth,

    Apologies for the delayed response!

    The error you're experiencing (SC_ERR_PATH_BROKEN with Error -233) indicates that the JTAG scan path is broken and cannot properly communicate with the device. Based on the search results, there are several potential causes and solutions:

    1. Hardware-Related Solutions:
    • Check the JTAG connections, particularly focusing on:
      • TDO (Test Data Out)
      • TMS (Test Mode Select)
      • TCK (Test Clock)
      • TRST (Test Reset)
    • Verify that TRST_N pin is properly connected and pulled up
    • Ensure proper voltage levels on all power rails:
      • Check if all required voltage rails (3.3V, 1.2V) are present and stable
      • Verify there are no voltage irregularities during operation

    1. Recovery Procedure: Try this specific sequence to recover the device:

    2. Open the target configuration window

    3. Launch the selected configuration

    4. Switch to debug window

    5. Press and hold the reset (nRST) button on your PCB board

    6. Click "Connect Target" immediately after releasing the nRST button

    7. You may need to try this sequence multiple times

    8. Additional Troubleshooting Steps:

    • Try lowering the JTAG clock frequency in the connection settings
    • Power cycle the board completely between attempts
    • If possible, check the JTAG signals with an oscilloscope to verify signal integrity
    • Ensure there are no sources of electrical noise that could interfere with JTAG communication
    1. Prevention for Future:
    • Review the PCB layout for potential signal integrity issues
    • Ensure JTAG traces don't cross power or ground plane splits
    • Consider adding additional filtering on JTAG lines if noise is an issue

    --
    Thanks & regards,
    Jagadish.