This demo is targeted towards the Olimex STM32P103 board, with 128 kB internal Flash EEPROM and 20 kB internal RAM.

To program the bootloader into the internal flash on the STM32F103 microcontroller, the Olimex ARM-USB-TINY-H JTAG interface was used in combination with OpenOCD 0.4.0. However, this is not required if you have another means of programming the internal flash.

To compile the demo programs with Codesourcery G++ Lite (Target OS EABI), you can invoke the make utility from the command line.

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

Batch files are added to aid in building the software program. First clean the bootloader program by double-clicking the file “\Target\Demo\ARMCM3_STM32_Olimex_STM32P103_GCC\Boot\cmd\clean.bat”. Next, build the bootloader program by double-clicking the file “\Target\Demo\ARMCM3_STM32_Olimex_STM32P103_GCC\Boot\cmd\build.bat”. The output should look like:

+++ Compiling [hooks.o]
+++ Compiling [main.o]
+++ Compiling [boot.o]
...
+++ Linking [openbtl_olimex_stm32p103.elf]
...
+++ Build complete [openbtl_olimex_stm32p103.srec]

The bootloader program is now ready to be programmed into the internal flash memory of the STM32F103. Using your favorite programmer, flash the bootloader using one of the following files, depending on what file type your programmer supports:

• \Target\Demo\ARMCM3_STM32_Olimex_STM32P103_GCC\Boot\bin\openbtl_olimex_stm32p103.elf
• \Target\Demo\ARMCM3_STM32_Olimex_STM32P103_GCC\Boot\bin\openbtl_olimex_stm32p103.srec

The Microboot utility needs to be configured to connect to the correct COM-port and to communication at the correct baudrate:

• Start Microboot by double-clicking “\Host\MicroBoot.exe”.
• Click the “Settings”-button and select “OpenBLT using UART” from the dropdown box.
• Click the “Options”-button to configure the communication parameters.
  • Select the PC's COM-port that the board is connected to.
  • Set the baudrate to 57600 bits/sec.

Once you saved the settings by clicking the “OK”-button twice, you can close Microboot by clicking the “Cancel”-button on the main screen. Microboot is now ready for action!

Batch files are added to aid in building the demo program. First clean the demo program by double-clicking the file “\Target\Demo\ARMCM3_STM32_Olimex_STM32P103_GCC\Prog\cmd\clean.bat”. Next, build the demo program by double-clicking the file “\Target\Demo\ARMCM3_STM32_Olimex_STM32P103_GCC\Prog\cmd\build.bat”. The output should look like:

+++ Compiling [boot.c]
+++ Compiling [main.c]
...
+++ Linking [demoprog_olimex_stm32p103.elf]
...
+++ Build complete [demoprog_olimex_stm32p103.srec]

The output file is

• \Target\Demo\ARMCM3_STM32_Olimex_STM32P103_GCC\Prog\bin\demoprog_olimex_stm32p103.srec

To download this demoprog_olimex_stm32p103.srec file to the remaining flash memory using the bootloader, start the Microboot program and click the “Browse”-button. Browse to the “\Target\Demo\ARMCM3_STM32_Olimex_STM32P103_GCC\Prog\bin\” directory and select the demoprog_olimex_stm32p103.srec file to start the download.

Once the download completed, the newly programmed software will be started by the bootloader. You can verify this by checking that the status LED blinks. Congratulations! That's all there is to using the bootloader.

In addition to the previously described update procedure with Microboot, the bootloader demo is configured for making firmware updates from an SD-card. The procedure is:

1. Insert the SD-card into your PC and store the firmware file demoprog_olimex_stm32p103.srec on it.
2. Insert the SD-card into the card holder on the microcontroller board.
3. Reset the microcontroller to start the firmware update. Once done, the newly programmed firmware is automatically started.

The bootloader demo is configured to output log messages to a serial terminal. This enables you to view the progress of the firmware update with a terminal program such as Putty. The communication settings are the same as those described above in section Configuring Microboot. Additionally, the log messages are written to a file called bootlog.txt on the SD-card, which can optionally be checked for verification purposes.