Posted on September 24, 2012 at 22:06 The packages I attached earlier are GNU/GCC Yagarto based, so yes the STM32F2 firmware library works just fine. You could build the library portion independently of the application. The CMSIS based firmwares seem to mash everything together, the older 2.x version for the F1 basically pulled in a .a/.lib file.
I've built F2 projects under Eclipse using the Code Sourcery chain, and when it starting squawking about licencing, I just pointed it at the Yagarto chain, which I've used for some time, along with WinARM, to build GNU/GCC related code trees.
My FreeRTOS projects are under Keil, but having them run with Yagarto or GNU/GCC is a simple port.
Here's the Keil one I did for the STM32F4-Discovery
https://my.st.com/public/STe2ecommunities/mcu/Lists/STM32Discovery/Flat.aspx?RootFolder=https://my.st.com/public/STe2ecommunities/mcu/Lists/STM32Discovery/FreeRTOS to STM32F4DISCOVERY - Crossstudio&FolderCTID=0x01200200770978C69A1141439FE559EB459D75800084C20D8867EAD444A5987D47BE638E0F¤tviews=134
IAR is quite similar to Keil, has a couple of nuances that annoy me, I'd work/port things to it if someone bought me a licence.
Debugging is a challenge with Open Source tool solutions, worked on by a lot of well meaning folk, but ultimately driven by their preferences/commitment. I honestly don't use debuggers much, if I have to single step my code to understand code flow I've already failed. Much prefer to stream telemetry via the serial port to understand real-time dynamics, not freeze the machine in a non-functional state. So classically when I need a debugger it's AXD/RealView/Keil. I'd imagine GDB would be similar, just not sufficiently familiar with it for it to be immediately usable for me.
