This demo is targeted towards the Nucleo-F103RB board, with 128 kB internal Flash EEPROM and 20 kB internal RAM.

To program the bootloader into the internal flash, the on-board ST-Link debugger interface was used. Firmware updates via the serial communication port are preconfigured to use the virtual COM-port offered by the ST-Link. This means that no additional hardware is needed, besides a standard micro-USB cable.

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_Nucleo_F103RB_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_Nucleo_F103RB_IAR\Boot\bin\openblt_stm32f103.out
• \Target\Demo\ARMCM3_STM32F1_Nucleo_F103RB_IAR\Boot\bin\openblt_stm32f103.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_Nucleo_F103RB_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_Nucleo_F103RB_IAR\Prog\bin\demoprog_stm32f103.srec

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

• Firmware updates using the RS232 communication interface
• Firmware updates using the CAN communication interface