• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 73 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.

CCSTUDIO: CCS20.2 fails to connect to the XDS110

tony tan
Prodigy 10 points
Part Number: CCSTUDIO

Tool/software:

Hi，

    CCS20.2 is unable to connect to the XDS110，Please provide support, thank you!

     1) Print information after press "Test Connection(s)"

    

-----[Print the board config pathname(s)]------------------------------------ C:\Users\tonytan\AppData\Local\TEXASI~1\ CCS\ccs2020\0\0\BrdDat\testBoard.dat -----[Print the reset-command software log-file]----------------------------- This utility has selected a 100/110/510 class product. This utility will load the adapter 'jioxds110.dll'. The library build date was 'May 23 2025'. The library build time was '13:46:29'. The library package version is '20.2.0.3536'. 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.
    2) Check XDS110's information:
C:\ti\ccs2020\ccs\ccs_base\common\uscif\xds110>xdsdfu -e

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...


<<<< Device 0 >>>>

VID: 0x0451 PID: 0xbef3
Device Name: XDS110 Embed with CMSIS-DAP
Version: 3.0.0.38
Manufacturer: Texas Instruments
Serial Num: L3101821
Mode: Runtime
Configuration: Standard

Found 1 device.
  • +1
    TI__Guru**** 466841 points

    Hello,

    Are you using a standalone XDS110 debug probe with a custom board?

    tony tan said:
    <<<< Device 0 >>>>

    VID: 0x0451 PID: 0xbef3
    Device Name: XDS110 Embed with CMSIS-DAP
    Version: 3.0.0.38
    Manufacturer: Texas Instruments
    Serial Num: L3101821
    Mode: Runtime
    Configuration: Standard

    Found 1 device.

    This means that the the CCS connection to the XDS110 is fine.

    tony tan said:
    he 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 means that the XDS110 was unable to successfully establish communication with with the device due to some low level (usually hardware) JTAG connection issue. 

    Please see the section called "Invalid data read back" in the below document:

    https://dev.ti.com/tirex/explore/node?node=A__ANoamrIZPWD2-6T-NDDWGg__ccs_devtools__FUz-xrs__LATEST

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 10 points

    Hi ki,

    The issue has been resolved; it was due to a power supply problem with the target board. Thank you