This demo is targeted towards the Olimexino-STM32 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 Segger J-Link JTAG interface was used. However, this is not required if you have another means of programming the internal flash. To connect the 20-pin cable of the Segger J-Link to the 10-pin SWD connector in the board, the ARM-JTAG-20-10 adapter was used.

To compile the demo programs you can use the IAR Embedded Workbench for ARM development environment.

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.

When using IAR EWARM, simply open the workspace from within the Embedded Workbench. The workspace file (stm32f103.eww) is located at: \Target\Demo\ARMCM3_STM32F1_Olimexino_STM32_IAR\Boot\ide\. Once opened, select Project→Rebuild All from the menu to compile all the bootloader sources and link the together into the final executable.

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_STM32F1_Olimexino_STM32_IAR\Boot\bin\openblt_olimexino_stm32.out
• \Target\Demo\ARMCM3_STM32F1_Olimexino_STM32_IAR\Boot\bin\openblt_olimexino_stm32.srec

When using IAR EWARM, simply open the workspace from within the Embedded Workbench. The workspace file (stm32f103.eww) is located at: \Target\Demo\ARMCM3_STM32F1_Olimexino_STM32_IAR\Prog\ide\. Once opened, select Project→Rebuild All from the menu to compile all the demo program sources and link the together into the final executable.

The output file is

• \Target\Demo\ARMCM3_STM32F1_Olimexino_STM32_IAR\Prog\bin\demoprog_olimexino_stm32.srec

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

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

Even though the demo bootloader can perform firmare updates via both CAN and USB, only one of these communication interfaces can be enabled at a time. This is due to a hardware limitation of the STM32F103 microcontroller where the CAN and USB peripherals cannot be used at the same time. These CAN and USB communication interfaces can be enabled/disabled with configuration macros in blt_conf.h: BOOT_COM_CAN_ENABLE and BOOT_COM_USB_ENABLE, respectively.