0

I am working on an ARMv7 based embedded system with an RTOS.
I am also using JLink (v7.00) in Linux to do code debugging.

I use the JLinkGDBServer and GDB together to do the debugging.
Sometimes the GDB failed to single step debug the code, especially the code within the critical section (where interrupt is disabled). It seemed that the JLinkGDBServer failed to capture the target CPU. And the JLinkGDBServer will dump lots of logs to say Read 2 bytes @ address 0xnnnnnnn (Data = 0xnnnnnnnn).

I don't know how to make the single step debugging in this case. I even tried hardware breakpoint at the codes, but got the same result as failing to single debugging the code within the critical section.

I am not sure if I missed something or it is a bug in JLink driver or hardware prober.

Frant
  • 5,382
  • 1
  • 16
  • 22
wangt13
  • 959
  • 7
  • 17

0 Answers0