Using J-Trace Cortex, TMS570LS12x chip, CCS IDE v10.3.
If debugger injects a Sw bkpkt, then it is no longer possible to resume/step the code, either C statement or ASM. This is in CCS.
Once this happens, the CCS
Looking at asm, for e.g:
So the CPU is stuck at line 1, and ASM step doens't work. Further, debugger/ide fails to read bunch of registers from that point, SP, CP, SPSR.
Moving PC manually, i.e. setnextline , or move to line, by setting to line 2 in asm above, resumes the code.
So, is J-Link/J-Trace 's settings somehow clash with software break points here? I don't get seems this stuck behaviour on same code with an XDS debug probe.
If debugger injects a Sw bkpkt, then it is no longer possible to resume/step the code, either C statement or ASM. This is in CCS.
Once this happens, the CCS
Looking at asm, for e.g:
So the CPU is stuck at line 1, and ASM step doens't work. Further, debugger/ide fails to read bunch of registers from that point, SP, CP, SPSR.
Source Code
- ortexR4: Trouble Reading Register PC: Failed to measure CPU clock frequency
- CortexR4: Trouble Reading Register CPSR: Failed to measure CPU clock frequency: second loop count is less than first one! (0<=0)
- CortexR4: Trouble Reading Register CPSR: Failed to measure CPU clock frequency
- CortexR4: Trouble Reading Register SP: Failed to measure CPU clock frequency: second loop count is less than first one! (0<=0)
- CortexR4: Trouble Reading Register SP: Failed to measure CPU clock frequency
So, is J-Link/J-Trace 's settings somehow clash with software break points here? I don't get seems this stuck behaviour on same code with an XDS debug probe.