Posted by rstanley on 2015-04-07 20:31

Have been struggling to get J-Link debugging to work.
I am a HW engineer, so, not used to SW tool configuration.
Have installed eclipse with openstm32 and STM32CubeMX add-ons in a W7 PC.
Could compile and debug with ST-Link on a STM32F429 discovery board.
When I try to use j-link as debugger, I consistently get an error
“Error while launching command: gdb - - version”

I have launched the “JLinkGDBServerCL.exe” in a DOS window, it seems to find my Device and ends with “waiting for GDB”.

At the bottom of the following page:
http://gnuarmeclipse.livius.net/blog/jlink-debugging/#J-Link_plug-in_use

I think the second paragraph refers to my problem, but I have no idea how to apply the information!

Can anyone give me a pointer?

Thanks

Error while launching command: gdb –version

If you kept the GDB client executable defined as ${cross_prefix}gdb${cross_suffix}, the above error means that the macros could not be substituted with the correct prefix/suffix. There can be several reasons for this. One might be that you did not associate the debug launcher to a project. Check the Main tab and be sure the field Project: refer to the correct project. Next time when you create the debug configuration, be sure you follow the above suggestions (select .elf, Debug Configurations, double click on GDB SEGGER J-Link Debugging. Another reason is presented below.

Using a different build plug-in or not supported compiler

Another reason for not being able to start the debug session is that your project was not build with the GNU ARM Eclipse managed build plug-in. If you are using another build plug-in, or an exotic/obsolete toolchain, you need to replace ${cross_prefix}gdb${cross_suffix} with the actual name of the gdb client available in your toolchain, since the ${cross_*} macros are available only in projects managed by the GNU ARM Eclipse build plug-in.