Posted by geraldfryjr on 2015-11-09 10:12

I didn’t write exactly how because it was the very First time I had done it.

However I am perparing a step by step description of how I created my first blinky project on this platform.

I know how you feel as I have been though almost every tuorial out there and got no where with them due to version changes or lack of details.
I am hoping that this well help more to people to get started with this great little board.

I will already assume that you have Eclipse installed, I am using the Luna version as I had problems with using Mars version locking up in some menus on me in linux, and, these are known issues that they are working on.

Also I will assume to that you have the “System Workbench for STM32-Bare Metal Edition” installed in Eclipse as well, the directions are in these pages and it is very simple to do,

http://www.openstm32.org/Installing+System+Workbench+for+STM32?structure=Documentation

This is the page for installing it in Eclipse,

http://www.openstm32.org/Installing+System+Workbench+for+STM32+from+Eclipse

I am using “qstlink2” to program my board, it works great but sometimes it hangs a little and you have to hit the reset button on the Discovery Board and then click on Run MCU in the Qstlink2 GUI and your progarm will start running, Othertimes the board will automatically reset and start running, I am sure there is a reason for this but I don’t know what it is at this time.

Qstlink 2 can be found here,

https://github.com/fpoussin/qstlink2

This page is great help for getting everything setup as well,

http://vedder.se/2012/07/get-started-with-stm32f4-on-ubuntu-linux/

After doing it so many times I found that by just adding the PPA found on this page for your distro is the easiest methed.

https://launchpad.net/~fpoussin/+archive/ubuntu/ppa

And then just use “apt-get install qstlink2” and it will install it and create the icon for you as well to add to your panels for launching.

Then all you have to do is copy the dev rules with

sudo tar -xf stlink_udev_rule.tar.bz2 -C /etc/udev/rules.d

I have attched the devrules file and you put it in a folder called “stlink” in your Home directory to use the above command.

The dev rules for the “stlink and the “qstlink2” methods are the same I beleive.

I like “qstlink2” because it has a GUI where as “stlink” methed doesn’t and is run from the terminal.

I have not yet learned how to setup the debuging system but that is next on my list.

Then you connect your board and launch qstlink2 either by the icon or in a Terminal and you are good to go to program the board.

Unlike stlink, qstlink2 will only except a .bin file, but if your program compiles fine then the .bin file will be produced.

More to come!!

jer

P.S. The file that I added got added twice by mistake and I couldn’t figure out how to delete one copy.
Your added files don’t show up when you edit the post.