Navigation
External Links
Donate
Show your appreciation for OpenBLT
and support future development by
donating.
External Links
Donate
Show your appreciation for OpenBLT
and support future development by
donating.
RS232 | CAN | USB | TCP/IP | SD-card |
---|---|---|---|---|
No | No | Yes | No | No |
This demo is targeted towards the Olimex STM32H103 board, with 128 kB internal Flash EEPROM and 20 kB internal RAM.
This header board is a small version of the Olimex STM32P103, however it does not have a UART or CAN connector, but a USB connector. Therefore, the OpenBLT demo for this board features bootloading over USB. Note that this demo is compatible with the STM32P103 board as well.
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 you can use the Rowley Crossworks 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 Rowley CrossWorks, simply open the project from within CrossWorks and rebuild the project there. The project file is located at: \Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_Crossworks\Boot\ide\
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:
When using Rowley CrossWorks, simply open the project from within CrossWorks and rebuild the project there. The project file is located at: \Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_Crossworks\Prog\ide\
The output file is
To download the demo program \Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_Crossworks\Prog\bin\demoprog_olimex_stm32h103.srec using the bootloader, follow the instructions in the following links, depending on the communication interface you intend to use: