We are testing using J-Link PLUS with the J-Link GDB server on Windows 7. We are using Eclipse CDT and arm-none-eabi-gdb.exe to connect to the server.


Debugging works OK, however when we exit (or close) a debug session our processor locks up. On the J-Link GDB server the log indicates "Reset target CPU..". I think the reset is killing our processor due to our specialized HW.


Is there any way to disable the reset of the target CPU from the J-Link GDB server? Our HW setup does not allow for a reset through the JTAG connection.

The problem is fixed when we upgraded eclipse. We are using GDB through eclipse CDT, and the old version had CDT 7.0.1.2010... and we switched to CDT 8.3.0.2014... After the switch we never see a reset on the JLINK GDB server.

My best guess is that the older CDT was sending a signal (through arm-none-eabi-gdb) to the JLINK GDB server which was causing the reset, and the new version does not send any signal.

The problem occurred (with the older CDT) when we we pressed the terminate button on the CDT debugger window.
This was the message on the J-Link GDB Server "Reset target CPU..."
and on the J-Link control panel the log had this message "JLINK_Reset() -- Type 0"