Skip to main content



      Home
Home » Language IDEs » C / C++ IDE (CDT) » Debuging of STM32 does not work since update
Debuging of STM32 does not work since update [message #1709904] Thu, 01 October 2015 16:09 Go to next message
Eclipse UserFriend
Hello,

I use eclipse for programming with STM32 controllers. I have installed cdt and the arm plugin. All worked fine since I made a update. Now I cannot debug anymore.
I get this message when I want to program and debug the controller:

Error in final launch sequence
Failed to execute MI command:
-exec-run
Error message from debugger back end:
Don't know how to run. Try "help target".
Don't know how to run. Try "help target".

What is the problem?
When I use the terminal with openocd and gdb it works fine.

Here a foto of my configurations:
dropbox.com/s/ios1724xuet0vme/pic1.png?dl=0
Re: Debuging of STM32 does not work since update [message #1709905 is a reply to message #1709904] Thu, 01 October 2015 16:12 Go to previous messageGo to next message
Eclipse UserFriend
To use OpenOCD on the same computer, GDB needs a command:

target remote :3333

to use OpenOCD. You may miss it. Look at the 'Debug Configurations'.
Re: Debuging of STM32 does not work since update [message #1709928 is a reply to message #1709905] Fri, 02 October 2015 00:58 Go to previous messageGo to next message
Eclipse UserFriend
Tauno Voipio wrote on Thu, 01 October 2015 20:12
To use OpenOCD on the same computer, GDB needs a command:

target remote :3333

to use OpenOCD. You may miss it. Look at the 'Debug Configurations'.


Where I have to input this command?
Re: Debuging of STM32 does not work since update [message #1709939 is a reply to message #1709928] Fri, 02 October 2015 03:28 Go to previous messageGo to next message
Eclipse UserFriend
Not sure if this would be helpful but there is a plugin specifically for debugging OpenOCD at http://gnuarmeclipse.github.io/debug/openocd/
You may want to look into it.


Re: Debuging of STM32 does not work since update [message #1709998 is a reply to message #1709928] Fri, 02 October 2015 10:26 Go to previous messageGo to next message
Eclipse UserFriend
Open Eclipse, Help, Help Content, C/C++ Development User Guide, Getting Started, Debugging Projects.

There is more in the Reference part of the guide.
Re: Debuging of STM32 does not work since update [message #1710017 is a reply to message #1709998] Fri, 02 October 2015 12:46 Go to previous messageGo to next message
Eclipse UserFriend
I use this plugin. I had some start commands for the gdb but I don't remember me.
Re: Debuging of STM32 does not work since update [message #1710019 is a reply to message #1710017] Fri, 02 October 2015 13:14 Go to previous messageGo to next message
Eclipse UserFriend
I did that in the terminal:

1. Terminal: openocd -f /usr/share/openocd/scripts/board/st_nucleo_f4.cfg
2. Terminal: arm-none-eabi-gdb workspace/STM32I2C/Debug/STM32I2C.elf
tar ext :3333
monitor reset halt
load
monitor reset init
thbreak main
continue
It works fine. I can make breakpoint, stepping .... how I can do that in eclipse?
Re: Debuging of STM32 does not work since update [message #1710033 is a reply to message #1710019] Fri, 02 October 2015 14:46 Go to previous message
Eclipse UserFriend
You have to make a debug configuration from the 'Run' 'Debug Configurations'.
There are pages for setting the GDB commands.

Please read the manual part on creating the debug configuration. There is little sense that I'd copy the help pages here.

If I were you, I'd create an openocd.cfg file in the working directory, either by making a symlink to the configuration or by greating a configuration file which sources your configuration file from the crooked path.
Previous Topic:Fortran static libraries
Next Topic:Make eclipse indent preprocessor macros.
Goto Forum:
  


Current Time: Mon Jul 14 09:06:37 EDT 2025

Powered by FUDForum. Page generated in 0.27681 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top