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/BEAGLEBOARD-X15: CCS 7.4 XDS100v2 connection: The controller has detected a cable break far-from itself.

Part Number: BEAGLEBOARD-X15


Tool/software: Code Composer Studio

Dear all,

I try to connect to the beagle board using my XDS100v2 debug probe and get the output below. What can I do to fix the problem? Is it possible at all to connect to the beagleboard x15 using the XDS100v2 ?

Thanks for your help!

[Start: Texas Instruments XDS100v2 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]


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

C:\Users\MDORIG~1\AppData\Local\TEXASI~1\
CCS\ti\1\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 'jioserdesusb.dll'.
The library build date was 'Nov 6 2017'.
The library build time was '10:36:36'.
The library package version is '7.0.100.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 '-183' (0xffffff49).
The title is 'SC_ERR_CTL_CBL_BREAK_FAR'.

The explanation is:
The controller has detected a cable break far-from itself.
The user must connect the cable/pod to the target.

[End: Texas Instruments XDS100v2 USB Debug Probe_0]

  • Hi,

    XDS100v2 is fully supported by the device of the AM572x device of the BEAGLEBOARD-X15. Looking at its System Reference Manual, I can see the JTAG connector is populated and should be operational. However, I strongly suspect this board has the same behaviour as our GPEVM - namely an 8s shutdown time of the PMIC described in the post below:
    e2e.ti.com/.../2519999

    In this case, try the method described above and see if you can successfully connect to your board.

    If you are already doing this, then you should check the reference below (search for the error code)
    dev.ti.com/.../

    Hope this helps,
    Rafael
  • Thanks for the hint. I could not solve the issue so I moved on and use an XDS560v2, that one work right away.

    Thanks for your effort,

    Martin
  • Martin,

    Thanks for reporting back your findings; I still think the problem may be related to the fast PMIC reset - the XDS560v2, being a much faster Debug Probe, will most probably prevent the reset to occur.

    At any rate, good development!

    Regards,
    Rafael