Hi! Now that the reset problem is solved for me, I'm trying to optimize my eclipse setup for my STM32 target.
Basically, I'm using gnuarmeclipse.sf.net for project settings and makefile generation, CodeSourcery Lite as the toolchain, and the "Eclipse C/C++ GDB Hardware Debugging" Plug-In from the current Eclipse Galileo 3.5/CDT 6 release. There also seems to be an Plugin from Zylin (Øyvind?), but http://opensource.zylin.com/embeddedcdt.html is quite outdated. Eclipse 3.3?, CDT 4?! That's > 2 years old!. What's the status on this one? So I just use a GDB Hardware Debugging configuration using the plugin from the official CDT6. My initialization sequence looks like this: mon reset halt load continue Most of the other check boxes (Reset, Halt, Load image) don't seem to work correctly with OpenOCD. Also, I have to start the OpenOCD server seperately in the background. After entering debug, a click on "Restart" leads to this error: Exception(s) occurred attempting to restart. Target request failed: The "remote" target does not support "run". Try "help target" or "continue". Also, I haven't found a nice way to just flash the program, and let it run without debugging. A normal "run" configuration won't do the job, as it tries to start the .elf natively. A "debug" configuration switches to the debug perspective, and won't exit after flashing. So what do you use for development?! Any tips or best practices? _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
