• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 81 subscribers
  • Views 451 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.

TMS320F28388D: Can't connect with XDS200 emulator

Davide Plavan
Prodigy 135 points
Part Number: TMS320F28388D


I was using the XDS200 emulator when suddenly it stopped working.

I tried everything and I followed the troubleshooting that TI sent to me.

The same board works fine with another emulator.

The same emulator doesn't work with another board.

The log from CCS12 from 'Test Connection' says that there is "a line stuck to 0 or to 1".

  • 0
    TI__Guru 55700 points

    David,

    Can you send us the Test Connection results for both XDS200 emulator and other emulator you are working?

    Did you check whether XDS200 emulator works correctly on another board? Are you sure the problem is not with the emulator?

    Regards,

    Manoj

  • 0 in reply to Manoj Santha Mohan
    Prodigy 135 points

    Manoj, as I wrote, the emulator doesn't work with another board (we have four of them). So I'm sure that the problem is with the emulator.

    This is the log from the Test Connection:

    [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\Plavan\AppData\Local\TEXASI~1\CCS\
    ccs1230\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 10 2023'.
    The library build time was '22:17:39'.
    The library package version is '9.11.0.00128'.
    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 '-234' (0xffffff16).
    The title is 'SC_ERR_PATH_IR_BROKEN'.

    The explanation is:
    The instruction scan-path cannot circulate bits, it may be broken.
    An attempt to scan the JTAG instruction registers has failed.
    The target's JTAG instruction path appears to be broken
    with a stuck-at-ones or stuck-at-zero fault.

    [End: Texas Instruments XDS2xx USB Debug Probe_0]

  • 0 in reply to Davide Plavan
    TI__Guru 55700 points

    Okay. It looks like your emulator has a hardware issue.

    Are you asking how to revive you emulator? You cannot update firmware and expect to get this resolved as the issue is with emulator HW. You can try probing for JTAG signals and see whether any of the JTAG pins are shorted to GND (or) power-supply. Then you have to find why it is shorted to GND (or) power supply replace that part. This is like debugging any other HW. Unfortunately no shortcuts.

  • 0 in reply to Manoj Santha Mohan
    Prodigy 135 points

    Manoj, I was sure the problem is in the emulator, but TI Customer Service asked me to write here before proceding with a replacement. So, thank you for your confirmation.

    For completeness of the analisys I include the Test Connection log of the same board with another emulator

    [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\MUDRIT~1\AppData\Local\TEXASI~1\

        CCS\TI-CCS~1\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 'Jun 25 2021'.

    The library build time was '16:23:59'.

    The library package version is '9.4.0.00129'.

    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.

     

    -----[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 XDS2xx USB Debug Probe_0]

  • 0 in reply to Davide Plavan
    TI__Guru 55700 points

    Okay. Thanks for letting me know.

    I'm closing this thread.

    Regards,

    Manoj