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.

TMS570LS3137: Error -1170, Inability to connect...

Part Number: TMS570LS3137
Other Parts Discussed in Thread: UNIFLASH

My software writer has created code which now prevents JTAG access to 4 TMSs in a chain. I would try a procedure suggested at https://e2e.ti.com/support/microcontrollers/hercules/f/312/p/542615/2020352 but this thread is no longer on your website.  The fifth TMS..3137 in the chain has different code and re-programs OK.

If I pull nRST low, then instead of the -1170 error, I see -241 error on the particular part (see attached txt file).

It's believed our code runs for about 30ms then shuts down all the TMS clock domains.

I've made a Reset-release latch such that upon receipt of the first TCLK rising edge, Power-On-Reset is released high. So when I start the Uniflash Erase script, I get 43ms of slow clock (40kHz) until the TMS570 outputs TDO, whereupon TCLK is set to full speed, with TMS and TDI pulses. However, the Debug output is the same as in the txt file. Ah, even with Reset released at power-up, I still see 43ms of slow clock so this must be part of the 100V2 boot process. Is there any way of speeding that section up?

I'm currently using Windows to run both pods, but could find Unix to run Uniflash as I gather it might run with less delays between process phases.

Any ideas welcome, Thanks.

C:\ti\ccs831\ccsv8\ccs_base\DebugServer\bin\DSLite.exe flash --config=TMS.ccxml -n 1 -a Erase
fatal: Dap_2: Error connecting to the target: (Error -241 @ 0x0) A router subpath could not be accessed. A security error has probably occurred. Make sure your device is unlocked. (Emulation package 8.1.0.00012)
Failed: Operation was aborted

C:\ti\ccs831\ccsv8\ccs_base\DebugServer\bin\DSLite.exe flash --config=TMS.ccxml -n 2 -a Erase
fatal: CortexR4_3: 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 8.1.0.00012)
Failed: Operation was aborted

C:\ti\ccs831\ccsv8\ccs_base\DebugServer\bin\DSLite.exe flash --config=TMS.ccxml -n 3 -a Erase
fatal: CortexR4_0: 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 8.1.0.00012)
Failed: Operation was aborted

C:\ti\ccs831\ccsv8\ccs_base\DebugServer\bin\DSLite.exe flash --config=TMS.ccxml -n 4 -a Erase
fatal: CortexR4: 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 8.1.0.00012)
Failed: Operation was aborted