Posted on April 18, 2012 at 16:28I am using all opensource tools with an STM32VLDISCOVERY (using the on-board ST-link) by roughly following the instructions here:
http://www.stf12.org/developers/ODeV.html I'm using CodeSourcery Lite, Eclipse with the ARM plugin, and OpenOCD, from PCLinuxOS 2011. There are a lot of points to get hung up following those instructions though:
-OpenOCD must be pulled from the GIT repository, as you need a very new version, and must be compiled using ./configure --enable-maintainer-mode --enable-stlink. You can then run it with openocd -f board/stm32vldiscovery.cfg
-Trying to get everything working at once through Eclipse is a pain. In fact, there's no reason you even *need* Eclipse -- your firmware projects will actually cross-build just fine by typing ''make'', assuming you have a proper makefile. Instead, get OpenOCD sending commands to the ST-link first. Test it through its telnet interface, (you should at least be able to start and stop the eval board from running), then get arm-none-eabi-gdb connected to it (easy).
-Instead of using the example projects at the website mentioned above, I started with a much simpler one that I found... somewhere. Try googling for a template project. Like before, trying to start with a complicated project that uses RTOS just gives you more chances to have problems that you will spend time trying to explain.
I am only a couple of days into using this toolchain, so I will know more about it in the future, but so far it appears to be pretty solid. If not, there are other (opensource) options for each one of the components.
