Hi,
I am tying to setup a PRU to output to in the most basic sense, and I am running into some issues. I have a system project setup and I am using that to configure all the peripherals, and then I have a project on an ARM R Core and a project on RPU1. Everything builds and seems to be configured correctly, but when I try to debug I get:
Error connecting to the target:
(Error -1170 @ 0x0)
Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 9.13.0.00201)v
When I try to connect the JTAG with the ccXML file I generated I get:
[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\GriffiEV\AppData\Local\TEXASI~1\
CCS\ccs1230\0\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 'jioxds110.dll'.
The library build date was 'Sep 6 2023'.
The library build time was '09:57: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 '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: Texas Instruments XDS110 USB Debug Probe_0]
The ccXML looks like this:
I tried lowering the speed and tinkering with the boot mode, but nothing seems to work. I inherited a disjointed project that was working yesterday so I don't think its hardware related.
I also googled around and found talk of gel scripts and other things, but those don't appear to have resoled the issue, but that does not mean they are not the issue, more likely my newness to CCS is part of the problem.
What should I check?
