Simultaneous access to target via J-Link GDB Server and J-Link Commander.

Eugene · August 20, 2008 at 4:59 PM

Hello

I'm working with my target by using GDB server and sometime I need to monitor some target resources (such as EmbeddedICE registers or something other) by using J-Link Commander. Is this operation correct? Commander's output is not conforming with real system state. Of course, in monitoring target is halted.

BR, Eugene.

SEGGER - Rolf · August 26, 2008 at 2:44 PM

Eugene,

it does not work this way. The first process will modify the ICE registers, so they are temporary registers
that are not consisten between processes.
You can still read write ICE registers from a second process, but you should be aware that the first process can modify them at any time as well.
After all, it is only one CPU ...

Eugene · August 29, 2008 at 5:33 PM

Rolf,

Your reply has almost satisfied me, but I want more explanations.

For example, lets consider next situation:
1) Target is halted;
2) GDB is showing, for example, what ARM’s core register r0 is equal to 0xDEADBEAF;
3) J-link’s “regs” command is printing r0 value as 0x0BADC0DE.

Should I treat “0x0BADC0DE” in r0 as “garbage” having been temporary stayed there by debugger’s interface pluck (i.e while target halted, its resources used by debugger’s interface internals) and that original context (0xDEADBEAF) will be restored before continue of program being debugged?

Participate now!