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.
Dear Sirs.
We are testing functions from the Safety Library and end up in a situation where the debugger is no longer able to connect to the target.
Under this situation, our board is unusable because it has bad code and I'm not able to reprogram it.
I've tryind forcing to ground both PRORST and RST pins, but the debugger does not connect.
I have tried recovery both from Code Composer and Uniflash.
The error codes, depending if I'm resetting or not are:
CortexR5: Error connecting to the target: (Error -2062 @ 0x0) Unable to halt device. 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.4.0.00006)
Dap: Error: (Error -242 @ 0x0) A router subpath could not be accessed. The board configuration file is probably incorrect. (Emulation package 8.4.0.00006)
CortexR5: Error connecting to the target: (Error -6305) PRSC module failed to write to a router register. (Emulation package 8.4.0.00006)
Is there any way to put the processor in a state that allows connection to the debugger without running whatever code it has inside that disables the JTAG?
Thank you
HI Txema,
I am sorry to hear this.
Did you try this way below?
Hi Wang.
After one hour cycling power and jumping nRST and nPORRST to ground while launching UniFlash I was able to download a working copy to the target.
I cannot tell how I did it exactly, but it worked.
Thank you.