The name of your board should be printed on the board itself. The “DISC1” is the newer version that uses “ST-Link/V2-1”. You will find two STM32F429I discovery boards. Select “Ac6 STM32 MCU Project” under “Executable”.Ĭlick “Next” until you are prompted to select a board. To do that, click on “File -> New -> C Project”. While that’s downloading, we will create a new C-Project in Eclipse called “blink_example”. It is a collection of software examples for the STM32F4 line of microcontrollers. For this, you must first download the STM32CubeF4 Software Package. Everything you need to get started, is in there.įor your first code project to flash onto the STM32F4, I recommend the “hello world” of electronics – to blink an LED. What I cherish most about the System Workbench is the extensive wiki on the homepage that really helps you out. I solved the issue by installing the newest Java SE Development Kit, which is different from the standard Java installation.įrom there the installation worked like a breeze and without complications.
To install the package, you simply download an installer and run it.Īt first it gave me an error saying my Java RE (Runtime Environment) was out of date, even though the System Preferences showed me a version higher than the one required. It is based on free software, such as the Eclipse programming environment. Having a Macbook running OSX El Capitan (10.11), I really only had one option – the OpenSTM32 System workbench.
Atollic Truestudio - So far only for Windows, site says “Linux and Mac OS X support is scheduled for later this year”.
I wrote down all the free ones that seemed promising: Knowing my previous IDE would fail me, I looked around for alternatives.Īfter a bit of searching I found a page on ST’s site that lists many software IDEs that support their chips. So I put the board aside and focused on other projects.Ībout a year later, earlier this month, I dug out my discovery board again. I just couldn’t get those tasty ST code examples to compile. The problem wasn’t the code itself, but the programming IDE I was using. But each error fixed would uncover 10 more compile errors. Upon compiling, I would only encounter a few errors. It was enough to blink an LED on the board, but as soon as I wanted to play around with the code examples given by ST, I hit a brick wall. Like all images on this page, click to see in full size.Īt the time I had built myself a programming environment by piecing together free software and command line tools, following this recipe.