I’m using WinXP Pro, an Olimex ARM-USB-TINY ( http://www.sparkfun.com/commerce/produc … ts_id=8278 ), and an STM32 prototype board ( http://www.sparkfun.com/commerce/produc … ts_id=8560 ).
I know the board works, I can flash and debug it using IAR tools. I tried using the instructions and software here http://www.st.com/mcu/forums-cat-6445-23.html to program/flash/debug with gcc, using the toolchain from codesourcery (their latest eval version of ‘professional’). I’ve tried the OpenOCD that came with codesourcery’s installer, as well as the one from the Yagarto website, and building OpenOCD from subversion top-of-trunk.
I can build, flash and execute my program using OpenOCD and the olimex programmer (as evidenced by blinking LEDs), but I am not able to debug. I can telnet into openocd (localhost:4444) and start/stop, but when I connect with GDB (“target remote localhost:3333”), I am not able to ‘continue’. gdb responds with ‘Continuing.\n’, but I do not get a “(gdb)” prompt after that, and it becomes unresponsive to commands. All I can do at that point is ctrl-c to quit gdb.
What I haven’t tried yet is a different toolchain, but because it’s an STM32 (Cortex-M3), I think I am stuck with using one from codesourcery until they merge the cortex changes back to mainline gcc. I may try using the ‘light’ (free) version instead of the trial Pro version I am using now. I may also try debugging with Eclipse instead of using GDB directly, I’ve no idea how/why that would work, but I don’t know what else to do.
Anyone have any advice? Should I switch to a regular ARM7 instead of Cortex-M3? There’s a lot of things like yagarto and gnuarm that claim to offer turn-key ARM7 programming/debugging/IDE, but they don’t yet support Cortex-M3.
Thanks,
Miles