ARM-CM3 STM32 Olimexino-STM32 TrueStudio

Supported firmware update interfaces

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

Development Environment

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 ST-LINK/V2 debugger 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 ST-LINK/V2 to the 10-pin SWD connector on the board, the ARM-JTAG-20-10 adapter was used.

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.

Workspace creation in TrueStudio

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_STM32F1_Olimexino_STM32_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_STM32F1_Olimexino_STM32_TrueStudio\. Eclipse will automatically find the Boot and Prog projects and select them:

Click the Finish button to complete the project import operation.

Building and programming the Bootloader

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

Set the project as the active project in Eclipse. This is achieved by clicking the Boot project in the Project Explorer to select it. Next, select Project → Rebuild Project from the menu to compile all the bootloader sources and link them together into the final executable.

The bootloader program is now ready to be programmed into the internal flash memory of the STM32F103RB microcontroller. Make sure the Olimexino-STM32 board is connected to your PC via a ST-LINK/V2 debugger interface. Next, select Run → Debug from the menu to flash the bootloader program. This will launch the Debug perspective in Eclipse. Once done, you can start the bootloader program by selecting Run → Resume from the menu.

Alternatively, you can use your favorite programmer to flash the bootloader using one of the following files, depending on what file type your programmer supports:

  • \Target\Demo\ARMCM3_STM32F1_Olimexino_STM32_TrueStudio\Boot\Debug\openblt_olimexino_stm32.elf
  • \Target\Demo\ARMCM3_STM32F1_Olimexino_STM32_TrueStudio\Boot\Debug\openblt_olimexino_stm32.srec

Building the Demo Program

Set the project as the active project in Eclipse. This is achieved by clicking the Prog project in the Project Explorer to select it. Next, select Project → Rebuild Project from the menu to compile all the user program sources and link them together into the final executable.

The output file is

  • \Target\Demo\ARMCM3_STM32F1_Olimexino_STM32_TrueStudio\Prog\Debug\demoprog_olimexino_stm32.srec

Firmware update procedure

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

Known limitations

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.

manual/demos/olimexino_stm32_truestudio.txt · Last modified: 2018/06/07 12:17 by voorburg
 
Powered by PHP Driven by DokuWiki