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/CC2642R: XDS110 Debug Probe Can't Detect CC2642R1 On Custom Board

Part Number: CC2642R

Tool/software: Code Composer Studio

Hello,

I have a custom board designed based on CC2642R1. However, I have been having issues flashing the chip with an XDS110 on CC2652R1 launchpad. I've been getting the following error.

When I tried testing the connection to the chip in CCS Studio, I got the following error messages

[Start: Texas Instruments XDS110 USB Debug Probe_0]
 
Execute the command:
 
%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity
 
[Result]
 
 
-----[Print the board config pathname(s)]------------------------------------
 
C:\Users\zhang\AppData\Local\TEXASI~1\CCS\
    ti\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 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 '-242' (0xffffff0e).
The title is 'SC_ERR_ROUTER_ACCESS_SUBPATH'.
 
The explanation is:
A router subpath could not be accessed.
The board configuration file is probably incorrect.
 
[End: Texas Instruments XDS110 USB Debug Probe_0]
I followed the launchpad schematic very closely and I am not sure if it's a design issue. Do you have any ideas what the issue might be? Thank you very much!