#55 Target halted after termination of debug session

Version 1.x
debug stm32 (2)
Ulf S

When debugging my STM32F2xx project using a J-Link Ultra+ everything works fine until I terminate the debug session. The target doesn't continue execution but seems to be halted, and I need to either manually reset it or restart the debug session.

I would like it if it worked as when I'm using IAR EWARM. Then, when I terminate a debug session the target continues execution.


  • Liviu Ionescu (ilg)

    Do you mean that exactly the same application, the same J-Link GDB server and the same J-Link Ultra+ probe, when used with IAR EWARM, continues to run after terminating the debug session, while with GNU ARM Eclipse J-Link plug-in it is restarted?

    As far as I know, the plug-in does not perform any reset at the end, so the application should continue to run.

    What happens if after terminating the debug session you unplug the jtag ribbon cable and reset the board? Does the application run properly?

  • Liviu Ionescu (ilg)

    • status: open --> accepted
    • assigned_to: Liviu Ionescu (ilg)
  • Ulf S

    Ulf S - 2014-05-12

    With IAR EWARM the debugger is C-Spy instead of GDB.

    It would seem that GDB + J-Link hogs the CPU after the debug session is terminated.

    I can restart the target by resetting it whether I disconnect the J-Link first or not.

  • Liviu Ionescu (ilg)

    I don't have any F2 board at hand, can you try with a STM32F4DISCOVERY board, so I can later reproduce the case?

  • Liviu Ionescu (ilg)

    Ulf, do you have any news related to this issue?

  • Ulf S

    Ulf S - 2014-06-24

    I'm sorry but I have no more input on this at the moment.

  • Liviu Ionescu (ilg)

    • status: accepted --> closed

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks