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.

RM44L920: debug tool xds110,xds200,xds560 selection

Part Number: RM44L920

when we connected xds110 with our board rm44l920, there were error occured as below, we are not sure if it is a hardware or software related problem, do you have any suggestions, thanks.

[Start]

 

Execute the command:

 

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

 

[Result]

 

 

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

 

C:\Users\212712~1\AppData\Local\TEXASI~1\

    CCS\ccs820\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 'May 30 2018'.

The library build time was '23:03:35'.

The library package version is '8.0.27.9'.

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]