Hello,
A team member is designing a PCB for a new product based around the TI RM57L843 but we are having issues connecting to the debug probe. I have connected using the 20-pin (2.54mm pitch, labelled 20eCTI - 20ARM on the silkscreen) ARM probe adaptor and have all signals connected except DBGRQ and DBGACK. When trying to verify the connection in Code Composer I get an error, full output window at bottom of message.
Am I using the incorrect adaptor or is there something else going on? I have tried with and without 4.7K pull ups on TDI/TMS and nReset and a 4.7k pull downs on TCK.
XDS200 end connections were assumed from the ARM-20 Pin column on dev.ti.com/.../node
Any help would be gratefully received.
Thank you,
Craig.
[Start]
Execute the command:
%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity
[Result]
-----[Print the board config pathname(s)]------------------------------------
C:\Users\CRAIG~1.OVE\AppData\Local\TEXASI~1\
CCS\ccs1120\0\0\BrdDat\testBoard.dat
-----[Print the reset-command software log-file]-----------------------------
This utility has selected a 560/2xx-class product.
This utility will load the program 'xds2xxu.out'.
The library build date was 'Mar 17 2022'.
The library build time was '19:20:23'.
The library package version is '9.7.0.00213'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '13' (0x0000000d).
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]-----------------------------
This emulator does not create a reset log-file.
-----[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]
