System Workbench for STM32

Hello,

Could you try to install the eclipse plugin yourself and see if it works?

I would be surprised if it doesn't, but then again, I don't have much experience with this STM32 line.

Thanks,
Dustin

Thanks Dustin, I am already using these eclipse plugins on another project and am highly impressed. The J-Link plug-in should work great with System Workbench. This will be advantageous for System Workbench as Segger has working J-Link drivers for all major operating systems.

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.

Found a fix to my problem above here:
https://community.freescale.com/thread/324320

Basically, at the Debug Config... Debug tag, for "GDB client setup", browsed to
"C:\Program Files (x86)\eclipse\plugins\fr.ac6.mcu.externaltools.arm-none.win32_1.1.0.201503101257\tools\compiler\bin\arm-none-eabi-gdb.exe"

Is there a better way?

Hi,

The right value to use in this case would be "${openstm32_compiler_path}\arm-none-eabi-gdb.exe" (the .exe is in fact optional); going this way allows you to not depend on th einstallation directory and use the last version of the debugger when you update System Workbench (by "Help >> Check for Updates...")

Bernard

There is some method to use J-link with AC6 and view the I/O registers? Now, when I debug with J-link, the "I/O registers", show "No CMSIS-SVD schema for this target". Can AC6 integrate J-link officially?

Hi,
I have just successfuly started J-Link under AC6. It works significantly faster than ST-Link e.g. in step mode. It has unlimited breakpoits. It is good news.
How long I can't see / debug all register, the AC6 is only free of charge toy.
Dear developers! There is a piece of market to take! I hate the IAR user interface (eclipse is 100x better), but functionaly IAR is percect.

Regards, Maciej