Eclipse on Carmine Noviello

How to quickly import a STM32CubeMX project inside an Eclipse project

Mon, 02 Nov 2015 14:08:08 +0000

I’ve implemented a faster way to automatically import CubeMX project into an Eclipse tool-chain based on the GNU ARM Plugin, as described either on this blog and in my book.

I’ve implemented a bare-bone python script that simply “translates” a CubeMX project for the SW4STM32 (aka AC6) tool-chain in a project generated with the GNU ARM plugin. The script can be downloaded from my github account. Let’s see how this works.

First of all, we have to generate a new Eclipse project using the GNU ARM Plugin. Go to File->New->C Project and select “Hello World ARM Cortex-M C/C++ project. You can choose the project name you want. Click on “Next“. Here we assume “test1” as Eclipse project name.

Getting started with STM32F746G-DISCO

Mon, 13 Jul 2015 05:06:56 +0000

ST Microelectronics recently expanded its portfolio of STM32 microcontrollers with the new STM32F7 family. These are the new best-in-class MCUs from ST, with a Cortex-M7 core able to run up to 216Mhz (future releases will run up to 400Mhz with 2000 CoreMark index), with an internal flash up to 1Mb and 360Kb of RAM. STM32F7 is also able to run from external flash memory without performance penalty, thanks to a L1 cache (this is probably the most interesting aspect of these MCUs). STM32F7 are targeted for High-end embedded applications, especially to multimedia ones, and I think that it’s far from low-budget applications and hobbyist uses. At the time of writing, these MCUs are quite pricy, ranging from 12€ to 20€/pcs for low-volume orders. This is definitely a really high price, especially if you consider that you can find around Cortex-A7 MCUs for less than 10€. But I think that the price will be dramatically reduced in the future.

Running FreeRTOS on a STM32Nucleo using a free GCC/Eclipse toolchain

Mon, 22 Jun 2015 05:50:14 +0000

Using a micro like the STM32F4, able to run up to 160Mhz, with 512Kb of flash and about 100k of RAM, without using an operating system is a nonsense. Although it’s perfectly possible to use some forms of cooperative scheduling to execute firmware activities, basically this not convenient especially when dealing with low level events related to hardware (eg. interrupt handling) and aspects related to synchronization. As long as your firmware starts to grow, you’ll need constructs to synchronize firmware activities, like queues or semaphores. Moreover, especially when dealing with low-power devices, a busy spin (while(some condition);) it’s not the best solution if you have to fight with mAh.

Build STM32 applications with Eclipse, GCC and STM32Cube

Thu, 04 Jun 2015 14:13:18 +0000

If you landed to this page, you probably already know that I’ve covered this topic in the past. I showed in a series made of three posts how to successfully setup a complete Eclipse/GCC ARM tool-chain to develop applications for the STM32Nucleo-F4 developing board. Since then, many people have reported me positive feedback on that tutorial. But, some of them had serious troubles in getting those instructions working for other STM32 families (F0, F1 and so on). This was mainly caused by the GNU ARM Eclipse plug-in, or rather by the included templates in the plug-in. When a new project is created using the plug-in wizard, a template is used depending on processor family. Unfortunately, the plug-in author has updated just the template for STM32-F4 family to the more recently STM32Cube-F4 HAL framework from ST (which still supports only commercial IDE…..), leaving the other templates still based on the old Standard Peripheral Library, which is no longer supported by ST and STM32CubeMX tool used in my tutorial. *This causes my instructions to be wrong for processor families different from STM32-F4. *

Setting up a GCC/Eclipse toolchain for STM32Nucleo – Part III

Fri, 16 Jan 2015 07:12:39 +0000

Let’s recap what we’ve done in the two previous parts of this series. In the first part we’ve configured Eclipse and GCC to build applications for the ARM-Cortex platform. We’ve used the GNU ARM Eclipse plug-ins to generate a minimal yet working example (a simple blinking LED app) for our STM32 Nucleo board. Next, we’ve used the CubeMX tool from ST to generate the right initialization code for our Nucleo. Lastly, we used ST-Link Utility to upload generated binary code on the target MCU. In the second part we’ve taken a deeper look in the debug topic. We’ve configured OpenOCD and GDB to allow step-by-step execution of our application on the Nucleo target MCU.

Setting up a GCC/Eclipse toolchain for STM32Nucleo – Part II

Wed, 07 Jan 2015 14:13:50 +0000

In the first part of this series we’ve successfully setup a minimal yet working tool-chain to develop applications for the STM32 family (we’ve especially focused on STM32Nucleo developing board). We’ve based the tool-chain over the Eclipse IDE and the GCC cross-compiler for ARM Cortex platform. We’ve also created a test project (a simple blinking LED) and uploaded it on our Nucleo using the ST-Link Utility.

Setting up a GCC/Eclipse toolchain for STM32Nucleo - Part I

Sun, 28 Dec 2014 17:09:33 +0000

I recently got in my hands a new development board from STMicroelectronics: STM32Nucleo. It’s a development board based on the STM32 MCU and it is compatible with the Arduino UNO pinout. This means that it’s possible to use the hundreds of shields available for the Arduino. However this is true in theory, since the most important aspect of Arduino’s world is the software (based on libraries, examples, and so on) made for this popular platform.