Hello,
is ist possible to configure a setup for:
a) Segger GDB Server connection via JLink to target (Cortex-M7)
b) GNU ARM arm-none-eabi-gdb client connected to it
b1) where program execution is not interrupted (in any way even for the shortest amount of time)
b2) getting gdb client to perform "print my_data_structure" while target is running
?
So far I only managed to get the following:
- Connection to target via JLink
- GDB connection out of Eclipse via "GDB SEGGER J-Link Debugging"; I could also connect the gdb client purely from command line (without any difference)
- get it connected to the target
- but I always do see an interruption / halt
- (followed by a continue)
- when connected to the target and it is running, I am not able to enter a command to the gdb client, since it seems to be "locked by the gdb server"
- only if I halt the target, I can write commands via the gdb client
Did I overlook some config options?
If I want to read from / write to target memory without any sort of interruption / halt I have to connect to the running target with J-Link Commander (then use commands like mem32, w4) ... and therefore I lose the advantage of having GDB in combination with the ELF file (for "automatic symbol to address conversion" ... e.g. "(gdb) print my_data_structure")
is ist possible to configure a setup for:
a) Segger GDB Server connection via JLink to target (Cortex-M7)
b) GNU ARM arm-none-eabi-gdb client connected to it
b1) where program execution is not interrupted (in any way even for the shortest amount of time)
b2) getting gdb client to perform "print my_data_structure" while target is running
?
So far I only managed to get the following:
- Connection to target via JLink
- GDB connection out of Eclipse via "GDB SEGGER J-Link Debugging"; I could also connect the gdb client purely from command line (without any difference)
- get it connected to the target
- but I always do see an interruption / halt
- (followed by a continue)
- when connected to the target and it is running, I am not able to enter a command to the gdb client, since it seems to be "locked by the gdb server"
- only if I halt the target, I can write commands via the gdb client
Did I overlook some config options?
If I want to read from / write to target memory without any sort of interruption / halt I have to connect to the running target with J-Link Commander (then use commands like mem32, w4) ... and therefore I lose the advantage of having GDB in combination with the ELF file (for "automatic symbol to address conversion" ... e.g. "(gdb) print my_data_structure")