• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 3 answers
  • Subscribers 97 subscribers
  • Views 1033 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.

Original question:

TMS320C6748: Error connecting to the target through the XDS110

TMS320C6748: Debug error: -2131 in TMS320C6748 (non-recoverable)

user5238872
Prodigy 220 points

Part Number: TMS320C6748

Hi,

we have developing a project in a TMS320C6748 for one year and a half and we are using the XDS110 for debugging. During this time we had had the same problem in three TMS320C6748. 

While we are working, without changing the target plugs, SW, .gel, only restarting the debugging the next error is displayed and we can not debug again in the TMS320 board.

Error connecting to the target:
(Error -2131 @ 0x0)
Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 7.0.48.0)

After that, it is impossible to debug again that TMS320C6748. However, although the debug is not possible to load in NAND memory works and our project runs correctly.

The error after a Test Connection is the following:

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

This time, again, we have repeated the steps and the behaviour is the same that in the two previous cases:

- Follow the instructions (http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems#Device_register)

- Reinstall the JTAG 

- Check JTAG pin (http://processors.wiki.ti.com/index.php/XDS_Connector_Design_Checklist)

- We have several projects and we can not debug any of them

- If the binary is load in the NAND the project run and works correctly. So it is an error in the TMS320 board and XDS110 connection

- The CCS version is v7.3

We need your help to try solve this error in our targets and also to know how to avoid repeat this error (we have still one working DSP).

Thank you,

Lucía

  • 0
    TI__Guru**** 161600 points
    Hi,

    Could you post the JTAG part of your schematics?

    Best Regards,
    Yordan
  • 0 in reply to Yordan Kovachev
    Prodigy 220 points
    Hi,
    We connect the JTAG to the Texas LCDK for C6748.
    Best regards,

    Lucía
  • 0 in reply to user5238872
    TI__Guru**** 161600 points
    Hi,

    Check the recommendations here:
    software-dl.ti.com/.../ccs_debugging_jtag_connectivity_issues.html

    Basically see if the power supply to your board is ok. Try with a different JTAG cable (it is possible that it is broken). Depending on the readback you can check your JTAG emulator for short to VCC or to GND.

    Best Regards,
    Yordan
  • 0 in reply to Yordan Kovachev
    Prodigy 220 points

    Hi Yordan,

    Thank you for your answer. 

    While I was raisen the Test Connection for both debugger the debugging starts working. We have not done any extra activity or chang. Now, it is possible to debug with both debuggers. Previously the same teset was done with both debugger,

    It is very strange that sometimes the debug dies and we can not debug and one week later the error is recuperable and we can debug.

    We want to avoid that this situation will be repeated in the future. Do you know what is happening?

    Other thing to remark is when I raised the Test Connection each JTAG anserwered with different errors (despite of the same package versión are installed: 7.0.48).

    I attach the two different logs.

    Best regards,

    Lucía


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

    C:\Users\ilvc\AppData\Local\TEXASI~1\CCS\
        ti\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 'jioxds110.dll'.
    The library build date was 'Jul 21 2017'.
    The library build time was '19:36:41'.
    The library package version is '7.0.48.0'.
    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).

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

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    [Start: Texas Instruments XDS110 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\ilvc\AppData\Local\TEXASI~1\CCS\
        ti\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 'jioxds110.dll'.
    The library build date was 'Jul 21 2017'.
    The library build time was '19:36:41'.
    The library package version is '7.0.48.0'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.

    An error occurred while hard opening the controller.

    -----[An error has occurred and this utility has aborted]--------------------

    This error is generated by TI's USCIF driver or utilities.

    The value is '-267' (0xfffffef5).
    The title is 'SC_ERR_XDS110_TARGET_SUPPLY'.

    The explanation is:
    The controller could not detect valid target supply. Check target
    JTAG connection and/or connection setting specifying voltage level.

    [End: Texas Instruments XDS110 USB Debug Probe_0]

  • 0 in reply to user5238872
    TI__Guru**** 161600 points
    Hi,

    Are you sure your emulators power supply/XDS connector is OK? It seems that's the problem with both of your debuggers. Maybe loose connections or similar issue. Have you tested these debuggers with another baord?


    Best Regards,
    Yordan
  • 0 in reply to Yordan Kovachev
    Prodigy 220 points

    Hi,

    yes, I have tested both debuggers in another board and they are working well.

    Best regards,

    Lucía

  • 0 in reply to user5238872
    TI__Guru**** 161600 points

    Then have you inspected the JTAG header connections on the problematic boards? You need to comply with the recommendations provided here:
      Section 5.2.8 JTAG and EMU from this document:

    Chapter 4 JTAG from the Hardware Design Guide:

    Also the following two documents:
     

    Best Regards,

    Yordan