Update: If I create a NEW debug configuration from Segger (not STM), I see the "connect to target" option.
However, even though I explicitly filled in the path C:\Program Files (x86)\SEGGER\JLink\JLinkGDBServerCL.exe,
I get an error "Error while launching command: gdb --version" when I try to debug.
The project and ELF settings all look correct, and match the working non-Segger STM debug configuration.
Any ideas???
Original post: I'm using J-Link base to debug an STM32F413CG over SWD, in the STM STCubeIDE Eclipse package.
Debugging generally works great, thanks, but...
Configuring the debug profile, I can't find a "Connect to running target" option as explained here:
mcuoneclipse.com/2015/03/20/at…r-j-link-gdb-and-eclipse/
How do I connect to a running target?
Thanks!
Best Regards, Dave
PS: I'm using JLink_Windows_V652e
Also, no change after I updated to the latest GNU ARM C/C++ J-Link Debugging 4.1.4.201704251808 ilg.gnuarmeclipse.debug.gdbjtag.jlink.feature.group Liviu Ionescu
However, even though I explicitly filled in the path C:\Program Files (x86)\SEGGER\JLink\JLinkGDBServerCL.exe,
I get an error "Error while launching command: gdb --version" when I try to debug.
The project and ELF settings all look correct, and match the working non-Segger STM debug configuration.
Any ideas???
Original post: I'm using J-Link base to debug an STM32F413CG over SWD, in the STM STCubeIDE Eclipse package.
Debugging generally works great, thanks, but...
Configuring the debug profile, I can't find a "Connect to running target" option as explained here:
mcuoneclipse.com/2015/03/20/at…r-j-link-gdb-and-eclipse/
How do I connect to a running target?
Thanks!
Best Regards, Dave
PS: I'm using JLink_Windows_V652e
Also, no change after I updated to the latest GNU ARM C/C++ J-Link Debugging 4.1.4.201704251808 ilg.gnuarmeclipse.debug.gdbjtag.jlink.feature.group Liviu Ionescu
The post was edited 1 time, last by DaveN ().