This demo is targeted towards the Olimex STM32-P207 board, with 512 kB internal Flash EEPROM and 128 kB internal RAM.

To program the bootloader into the internal flash on the STM32F207 microcontroller, the ST-LINK/V2 debugger interface was used. However, this is not required if you have another means of programming the internal flash.

To compile the demo programs you can use the Atollic TrueStudio development environment. Note the Atollic TrueStudio is cross-platform. The information outlined on this page applies to both Microsoft Windows and Linux users.

Firmware updates via the serial communication port are preconfigured to use USART3 on connector RS232_2 on the board.

Two demo projects are included in the OpenBLT bootloader package. One for the bootloader itself and one for the demo user program. This user program is configured such that it can be programmed, into the internal flash memory of the microcontroller, during a firmware update with the bootloader.

The first step in getting the the bootloader up-and-running, is the creation of the Eclipse workspace in TrueStudio. After starting TrueStudio, you are prompted to open a workspace. It is easiest to create a new one in the following directory: .\Target\Demo\ARMCM3_STM32F2_Olimex_STM32P207_TrueStudio\

To import the demo programs into the workspace, select File → Import from the program menu. Then select General → Existing Projects into Workspace. On the next screen you select the following directory as the root directory: .\Target\Demo\ARMCM3_STM32F2_Olimex_STM32P207_TrueStudio\. Eclipse will automatically find the Boot and Prog projects and select them:

Click the Finish button to complete the project import operation.

Before the bootloader can be used, it needs to be built and programmed into the STM32F207'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\ARMCM3_STM32F2_Olimex_STM32P207_GCC\Boot\ and run the command:

make clean all

The expected output is:

+++ Cleaning build environment
+++ Clean complete
+++ Assembling [startup_stm32f2xx.S]
+++ Compiling [main.c]
+++ Compiling [hooks.c]
...
+++ Linking [openblt_stm32f207.elf]
..
+++ Build complete [openblt_stm32f207.srec]

The bootloader program is now ready to be programmed into the internal flash memory of the STM32F207. 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\ARMCM3_STM32F2_Olimex_STM32P207_GCC\Boot\bin\openblt_stm32f207.elf
• \Target\Demo\ARMCM3_STM32F2_Olimex_STM32P207_GCC\Boot\bin\openblt_stm32f207.srec

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

make clean all

The expected output is:

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

The output file is

• \Target\Demo\ARMCM3_STM32F2_Olimex_STM32P207_GCC\Prog\bin\demoprog_stm32f207.srec

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

• Firmware updates using the UART communication interface
• Firmware updates using the CAN communication interface
• Firmware updates from SD-card