How to attach to running target w/o reset from Linux JLinkGDBServer

最新推荐文章于 2024-07-26 20:47:03 发布

yazhouren

最新推荐文章于 2024-07-26 20:47:03 发布

阅读量697

点赞数

分类专栏： iot_robot

iot_robot 专栏收录该内容

205 篇文章 9 订阅

订阅专栏

origin: http://forum.segger.com/index.php?page=Thread&threadID=1347

Hello,

I am trying to work through the process of gdb + JLinkGDBServer attaching to a running device without invoking a reset on the device.
Some environmental info:
Ubuntu 11.04 Linux,
arm-none-eabi-gdb V7.4.40,
JLinkGDBServer V4.58 (JTAG, not SWD)
target system is STM32L151 Cortex-M3

I have tried starting JLinkGDBServer with the -noreset option but it appears not to work, at least on ubuntu linux.
The target get a reset regardless of the -noreset option.

Note: I have tried this with OpenOCD built for JLink support and it works (e.g. no reset).
The significant difference is that OpenOCD, by default, does not do any resets at connect time, where as JLinkGDBServer (per docs) does a reset unless the -noreset option is specified.
Most of developers in our shop use JLinkGDBServer, so I would prefer staying with JLinkGDBServer rather that trying to get them switched to OpenOCD.

Can someone give detailed directions as to how (in particular from Linux) to attach to a running Cortex-M3 system?
It would be much appreciated.

Thanks

Hi,

I just checked it again:
The current GDBServer does not perform a reset of the target at startup by default.
The doc is a bit outdated there because old/very old versions of the GDBServer always performed a reset of the target at startup.

The only cases under which a reset of the target is performed:
1) "monitor reset" is executed
2) GDB sends a 'k', 'r' or 'R' packet which are packets that are used for (k)ill, (r)eset or (R)estart. These packets are used by some GDB based IDEs to provide a reset button etc. in the IDE.
3) If attaching to the target is not possible which can happen for example if the target is in a low-power mode which disables the debug interface etc.
If J-Link knows the device (if the device has been selected in GDBServer at startup via command line) and so can perform a special connect in such cases, it is possible that a reset is performed.

Best regards
Alex