• State
  • Locked Locked
  • Replies 9 replies
  • Subscribers 53 subscribers
  • Views 6173 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:

CCS/TMDSEMU110-U: XDS110 not working, but my XDS100v2 works fine.

CCS/TMS320F28027: Error -233 - 'SC_ERR_PATH_BROKEN'.

SKR
Prodigy 130 points
Part Number: TMS320F28027

Tool/software: Code Composer Studio

Degugger used: XDS100v3 USB Debug probe

Error message: 

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

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusbv3.dll'.
The library build date was 'May 7 2020'.
The library build time was '21:10:18'.
The library package version is '9.2.0.00002'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
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 FTDI FT2232 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for FTDI FT2232 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 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 '-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]

what is the reason i am getting this.i have tried power cycling, checked for a short connection, please assist. 

  • 0
    TI__Guru**** 465891 points

    Hello,

    shruthi Ramasubramaniam said:

    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.

    This is a low level JTAG connectivity error, usually caused by some hardware issue. Please see the below link for more details and for suggestions on how to resolve it:

    https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html#invalid-data-read-back

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 130 points

    Hi all this didnt solve my issue. 

    I want to also know if i am using a xds100v3 debugger and my target configuration file is xds100v2.ccxml is it fine? i never had a xds100v2 debugger but my target file configurations have worked fine for me in the past. Should i install a xds100v3.ccxml for this to work? if so, where can i get the installation package?

    Thanks

    S

  • 0 in reply to SKR
    TI__Guru**** 465891 points

    If your probe is an xds100v3, then you should be using a ccxml for xds100v3. CCS comes with XDS100v3 support:

    You can see if this helps with your error. But I am doubtful. The error you are getting is a low level connectivity error where bits could be be successfully circulated on the JTAG scan chain. You need to confirm that your HW connections are all good.

  • 0 in reply to Ki
    Prodigy 130 points

    Nothing that i tried worked. Should the target configuration folder be inside a specific file path? i went ahead and changed the connectors with new ones and still the same error. not sure what i am doing wrong.

  • 0 in reply to SKR
    TI__Guru**** 465891 points

    SKR said:
    Should the target configuration folder be inside a specific file path?

    No, that should not matter.

    Again, the error is a low level connectivity issue, usually caused by some HW connection error.

    Can you provide your ccxml file? I just want to quickly verify that it looks good.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 130 points

    <?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/tixds100v2c28x.xml" id="drivers" xml="tixds100v2c28x.xml" xmlpath="drivers"/>
    <platform XML_version="1.2" id="platform_0">
    <instance XML_version="1.2" desc="TMS320F28027_0" href="devices/f28027.xml" id="TMS320F28027_0" xml="f28027.xml" xmlpath="devices"/>
    <device HW_revision="1" XML_version="1.2" description="" id="TMS320F28027_0" partnum="TMS320F28027" simulation="no">
    <cpu HW_revision="1.0" XML_version="1.2" desc="C28xx" description="CPU" deviceSim="false" id="C2800" isa="TMS320C28XX">
    <property Type="filepathfield" Value="..\..\..\..\solutions\instaspin_foc\boards\boostxldrv8305_revA\f28x\f2802xF\projects\ccs\f28027.gel" id="GEL File"/>
    </cpu>
    </device>
    </platform>
    </connection>
    </configuration>
    </configurations>

    Not sure whether this is the one that my program uses. I have multiple 28027_xds100v2.ccxml files in my computer. The debugger board i use is xds100v3.

  • 0 in reply to SKR
    TI__Guru**** 465891 points

    The ccxml file you are using seems ok. I don't see any issue there. Are you using a custom f28027 target board?

  • 0 in reply to Ki
    Prodigy 130 points

    Nope. i am using the emulator olimex TMS320-XDS100-V3. I have checked for loose cables, disonnected and connected the wires again, bought new cables. Deleted and reinstalled CCS. 

  • 0 in reply to SKR
    TI__Guru**** 465891 points

    You may need to put a scope and monitor the pins to check the signals. There is some issue with the HW JTAG scan chain.