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.

LAUNCHXL-F280025C: XDS 100 V3 : SC_ERR_TEST_MEASURE / SC_ERR_CTL_CBL_BREAK_FAR error

Part Number: LAUNCHXL-F280025C

Hi,

I would like to prepare custom board with 2 wires JTAG, so I bought XDS100V3 emulator and connect to my LaunchXL-F280025C as below : 

it's directly connected TCK and TMS to emulator, and LaunchXL board powered by USB, both 3.3v and GND connected to emulator.

but it's returned either SC_ERR_TEST_MEASURE or SC_ERR_CTL_CBL_BREAK_FAR errors 

Target connection 

SC_ERR_CTL_CBL_BREAK_FAR

[Start: Texas Instruments XDS100v3 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)]------------------------------------

/Users/dannychan/.ti/ccs1250/2/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 'libjioserdesusbv3.dylib'.
The library build date was 'Sep 6 2023'.
The library build time was '09:01:39'.
The library package version is '9.13.0.00201'.
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 XDS100v3 USB Debug Probe_0]

SC_ERR_TEST_MEASURE

[Start: Texas Instruments XDS100v3 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)]------------------------------------

/Users/dannychan/.ti/ccs1250/2/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 'libjioserdesusbv3.dylib'.
The library build date was 'Sep 6 2023'.
The library build time was '09:01:39'.
The library package version is '9.13.0.00201'.
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 '-501' (0xfffffe0b).
The title is 'SC_ERR_TEST_MEASURE'.

The explanation is:
The built-in scan-path length measurement failed.
The built-in scan-path reliability tests cannot be
performed without knowledge of the scan-path length.
Try specifying the scan-path lengths in the command-line
options or board configuration file of this utility or debugger.

[End: Texas Instruments XDS100v3 USB Debug Probe_0]