User Tools

Site Tools


manual:demos:olimex_stm32p405_gcc

ARM-CM4 STM32 Olimex STM32-P405 GCC

Supported firmware update interfaces

RS232 CAN USB TCP/IP SD-card
Yes Yes Yes No Yes

Development Environment

This demo is targeted towards the Olimex STM32-P405 board, with 1024 kB internal Flash EEPROM and 192 kB internal RAM.

To program the bootloader into the internal flash on the STM32F405 microcontroller, the Segger J-Link JTAG interface was used. However, this is not required if you have another means of programming the internal flash.

To build the demo programs you can use the GNU ARM Embedded toolchain.

Toolchain configuration

The demo programs are configured for building with a Makefile. Before attempting to perform a build, update the location of the toolchain binaries (i.e. arm-none-eabi-gcc) in the Makefile. It is set in variable TOOL_PATH. If the toolchain binaries are available on the path, then the TOOL_PATH variable can be left empty.

It is assumed that tools such as GNU make and rm are installed and available on the path. For (Ubuntu) Linux users this can be achieved by running command: sudo apt-get install build-essential. Windows users can install the GNU MCU Eclipse Windows Build Tools.

Building and programming the Bootloader

Before the bootloader can be used, it needs to be built and programmed into the STM32F405's internal flash memory. The steps in this section only need to be done once.

To build the bootloader, open a command prompt in directory \Target\Demo\ARMCM4_STM32F4_Olimex_STM32P405_GCC\Boot\ and run the command:

make clean all

The expected output is:

+++ Cleaning build environment
+++ Clean complete
+++ Assembling [startup_stm32f4xx.S]
+++ Compiling [usbd_usr.c]
+++ Compiling [usb_bsp.c]
...
+++ Linking [openblt_olimex_stm32p405.elf]
...
+++ Build complete [openblt_olimex_stm32p405.srec]

The bootloader program is now ready to be programmed into the internal flash memory of the STM32F405. Using your favorite programmer (i.e. OpenOCD, Segger J-Flash Lite or STM32 ST-Link utility), flash the bootloader using one of the following files, depending on what file type your programmer supports:

  • \Target\Demo\ARMCM4_STM32F4_Olimex_STM32P405_GCC\Boot\bin\openblt_olimex_stm32p405.elf
  • \Target\Demo\ARMCM4_STM32F4_Olimex_STM32P405_GCC\Boot\bin\openblt_olimex_stm32p405.srec

Building the Demo Program

To build the user program, open a command prompt in directory \Target\Demo\ARMCM4_STM32F4_Olimex_STM32P405_GCC\Prog\ and run the command:

make clean all

The expected output is:

+++ Cleaning build environment
+++ Clean complete
+++ Assembling [startup_stm32f4xx.S]
+++ Compiling [boot.c]
+++ Compiling [main.c]
...
+++ Linking [demoprog_olimex_stm32p405.elf]
...
+++ Build complete [demoprog_olimex_stm32p405.srec]

The output file is

  • \Target\Demo\ARMCM4_STM32F4_Olimex_STM32P405_GCC\Prog\bin\demoprog_olimex_stm32p405.srec

Firmware update procedure

To download the demo program \Target\Demo\ARMCM4_STM32F4_Olimex_STM32P405_GCC\Prog\bin\demoprog_olimex_stm32p405.srec using the bootloader, follow the instructions in the following links, depending on the communication interface you intend to use:

manual/demos/olimex_stm32p405_gcc.txt · Last modified: 2020/02/06 16:30 by voorburg