On Wed, Nov 11, 2009 at 1:30 PM, Thomas Kindler <mail+...@t-kindler.de> wrote: > 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?
I use it every day w/Eclipse 3.5, linux & windows. It supports projectless development + treats Cygwin as a first class citizen. > So I just use a GDB Hardware Debugging configuration using the plugin > from the official CDT6. My initialization sequence looks like this: > add to connect to OpenOCD: target remote xxxx:3333 > mon reset halt Should be: monitor reset init > load > continue Don't use continue. => use "stepi" here. This will *not* stepi, but rather sync up GDB to the target state. See message printed to that effect in the GDB console. -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
