I thought this was just a simple timeout problem so i set it to "set remotetimeout 40" and instead it started to give me a different error that said: Error in final launch sequence Text from the error is below: Error in final launch sequence The "set remotetimeout" was originally 20 but I got this error when i tried to launch the debug configuration from Eclipse (with "set remotetimeout 20"). Here is my Debug configuration for Eclipse Then i needed to set up a debug configuration so i could use GDB and Eclipse for graphical debugging. I am fairly certain that the external tool is not the problem, but i am including details on it for completeness sake. I tested this tool by running it from eclipse and the ST-Link LED flashes red and green to indicate that it was successfully connected to by OpenOCD from within eclipse.
Here are screenshots of the external tool configuration for OpenOCD Now i am trying to set up an eclipse debug configuration using OpenOCD as an external Tool.
I have tested this by connecting to my ST-Link from OpenOCD using terminal (it flashes red and green on an LED when its connected to). I have OpenOCD installed and set up correctly. I am following the instructions of a book called Mastering STM32 by Carmine Noviello. I am trying to get OpenOCD to work with my Nucleo-F446RE.
0 kommentar(er)
