• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 4659 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS: XDS110 not working but XDS100v3 works

Greg James
Prodigy 160 points
Other Parts Discussed in Thread: CC3200

Tool/software: Code Composer Studio

Hi

I have been using the XDS100V3 on the SmartRF06 to debug my CC3200 hardware and it has been working fine.

But when I try to use the XDS110 that I have just purchased it fails with SC_ERR_PATH_BROKEN , I have tried it with all the different JTAG/ SWD /cJTAG modes and droped the TCLK to 100Khz

Any ideas ?


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

/home/greg/.ti/ti/7/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 'libjioxds110.so'.
The library build date was 'May 2 2017'.
The library build time was '12:38:03'.
The library package version is '6.0.628.1'.
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]

  • 0
    TI__Guru**** 169894 points
    Hi,

    Can you send the XDS100v3 and the XDS110 .ccxml files so I can take a look at them?

    Regards,
    Rafael
  • 0
    Prodigy 160 points
    Hi Rafeal
    Thank you for your response

    The XDS100V3 ccxml

    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <configurations XML_version="1.2" id="configurations_0">
    <configuration XML_version="1.2" id="Texas Instruments XDS100v3 USB Debug Probe_0">
    <instance XML_version="1.2" desc="Texas Instruments XDS100v3 USB Debug Probe_0" href="connections/TIXDS100v3_Dot7_Connection.xml" id="Texas Instruments XDS100v3 USB Debug Probe_0" xml="TIXDS100v3_Dot7_Connection.xml" xmlpath="connections"/>
    <connection XML_version="1.2" desc="Texas Instruments XDS100v3 USB Debug Probe_0" id="Texas Instruments XDS100v3 USB Debug Probe_0">
    <instance XML_version="1.2" href="drivers/tixds100v2icepick_c.xml" id="drivers" xml="tixds100v2icepick_c.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds100v2cs_dap.xml" id="drivers" xml="tixds100v2cs_dap.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds100v2cortexM.xml" id="drivers" xml="tixds100v2cortexM.xml" xmlpath="drivers"/>
    <property Type="choicelist" Value="0" id="The Converter Usage">
    <choice Name="Its bypassed, use 1149.1, mimic XDS100v2" value="nothing">
    <property Type="choicelist" Value="0" id="The Emulator 1149.1 Frequency"/>
    </choice>
    </property>
    <platform XML_version="1.2" id="platform_0">
    <instance XML_version="1.2" desc="CC3200_0" href="devices/CC3200.xml" id="CC3200_0" xml="CC3200.xml" xmlpath="devices"/>
    </platform>
    </connection>
    </configuration>
    </configurations>

    And the XDS110

    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <configurations XML_version="1.2" id="configurations_0">
    <configuration XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
    <instance XML_version="1.2" desc="Texas Instruments XDS110 USB Debug Probe_0" href="connections/TIXDS110_Connection.xml" id="Texas Instruments XDS110 USB Debug Probe_0" xml="TIXDS110_Connection.xml" xmlpath="connections"/>
    <connection XML_version="1.2" desc="Texas Instruments XDS110 USB Debug Probe_0" id="Texas Instruments XDS110 USB Debug Probe_0">
    <instance XML_version="1.2" href="drivers/tixds510icepick_c.xml" id="drivers" xml="tixds510icepick_c.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds510cs_dap.xml" id="drivers" xml="tixds510cs_dap.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds510cortexM.xml" id="drivers" xml="tixds510cortexM.xml" xmlpath="drivers"/>
    <property Type="choicelist" Value="0" id="SWD Mode Settings"/>
    <platform XML_version="1.2" id="platform_0">
    <instance XML_version="1.2" desc="CC3200_0" href="devices/CC3200.xml" id="CC3200_0" xml="CC3200.xml" xmlpath="devices"/>
    </platform>
    </connection>
    </configuration>
    </configurations>
  • 0 in reply to Greg James
    TI__Guru**** 169894 points

    Hi,

    Thank you for sending the contents of the two files.

    I copied the contents of each to .ccxml files and opened them with CCS - their configuration is identical.

    I then used a different launchpad that has a XDS110 and, by means of a "frankenstein" connection, I was able to connect to my CC3200 Launchpad just fine. 

    In my case I have the SOP jumpers all pulled to set the debug mode to 4WD but nothing else was required. 

    In light of this I suspect that somehow the XDS110 connections to the board are incorrect or too noisy (despite the 100kHz on the TCLK).

    If you have a launchpad, would it be possible to test the XDS110 on this hardware in an attempt to isolate all variables? 

    Regards,

    Rafael

     

  • 0 in reply to desouza
    Expert 2395 points
    Hi Rafael,

    We are having a similar issue. Can you please take a look at it?
    e2e.ti.com/.../614015
  • 0 in reply to desouza
    Intellectual 380 points

    Hello Rafael,

    sorry for reopening the same thread but I am having the exact same issue. I am working with a beaglebone Black and am able to debug using a XDS100v3 but not with an XDS110 (on a MSP432 Launchpad). The output I get is as below. I am connecting the 4 pins from the Launchpad to the JTAG connector of the BBB exactly as you have done it. Additionally I am connecting the GND signal from the XDS header to the JTAG GND pins on the JTAG header.

    [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\User\AppData\Local\TEXASI~1\CCS\
        ccs730\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]

    Are there any other settings on the newer version of the Launchpad that I am overseeing / missing?? DO I need a firmware upgrade? I am ussing CCS 7.3.

    Best regards,

    Shailesh

  • 0 in reply to Shailesh Joshi
    TI__Guru**** 169894 points
    Hi everyone,

    Please apologize for missing this thread.

    Please check the thread below; the user is experiencing a very similar issue and is using a pull down TRST resistor that is too strong. Perhaps you can try to use a different resistor and see if it works well?
    e2e.ti.com/.../2333828

    Hope this helps,
    Rafael