Differences

This shows you the differences between two versions of the page.

--- manual:demos:olimex_stm32h103_crossworks [2011/12/17 13:21]
voorburg created
+++ manual:demos:olimex_stm32h103_crossworks [2020/02/06 16:23] (current)
voorburg
@@ Line 1: / Line 1: @@
 ====== ARM-CM3 STM32 Olimex STM32H103 Crossworks ======
+===== Supported firmware update interfaces =====
+^ RS232          ^ CAN             ^ USB          ^ TCP/IP       ^ SD-card      ^
+| No             | No              | Yes          | No           | No           |
 ===== Development Environment =====
 {{:manual:demos:olimex_stm32h103.png?200 |}}
 This demo is targeted towards the [[http://olimex.com/dev/stm32-h103.html|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 [[http://www.olimex.com/dev/arm-usb-tiny-h.html|Olimex ARM-USB-TINY-H]] JTAG interface was used in combination with [[http://openocd.sourceforge.net/|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 [[http://www.rowley.co.uk/|Rowley Crossworks for ARM]] development environment.
 ===== Building and programming the Bootloader =====
 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_STM32_Olimex_STM32H103_Crossworks\**Boot**\ide\
+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:
-  * \Target\Demo\ARMCM3_STM32_Olimex_STM32H103_Crossworks\**Boot**\bin\**openbtl_olimex_stm32h103.elf**
-  * \Target\Demo\ARMCM3_STM32_Olimex_STM32H103_Crossworks\**Boot**\bin\**openbtl_olimex_stm32h103.srec**
-===== USB driver installation =====
-With the bootloader programmed and running on the board, you will be prompted to install the USB driver, after connecting the board to your PC's USB port. The driver installation is described on a seperate page: [[manual:demos:usb_driver_install|OpenBLT USB driver installation instructions]].
+  * \Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_Crossworks\**Boot**\bin\**openblt_olimex_stm32h103.elf**
-===== Configuring Microboot =====
+  * \Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_Crossworks\**Boot**\bin\**openblt_olimex_stm32h103.srec**
-The Microboot utility needs to be configured to use USB as the communication interface:
-  * Start Microboot by double-clicking "\Host\**MicroBoot.exe**".
-  * Click the "**Settings**"-button and select "**OpenBLT using USB**" from the dropdown box.
-After selecting the USB communication interface, you can close Microboot by clicking the "**Cancel**"-button on the main screen. Microboot is now ready for action!
-===== Building and downloading the Demo Program =====
+===== Building the Demo Program =====
-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_STM32_Olimex_STM32H103_Crossworks\**Prog**\ide\
-The output file is
+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\
-  * \Target\Demo\ARMCM3_STM32_Olimex_STM32H103_Crossworks\**Prog**\bin\**demoprog_olimex_stm32h103.srec**
-To download this **demoprog_olimex_stm32h103.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_STM32H103_Crossworks\**Prog**\bin\" directory and select the **demoprog_olimex_stm32h103.srec** file to start the download.
-{{:manual:demos:olimex_stm32h103_download.gif?|}}
+The output file is
+  * \Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_Crossworks\**Prog**\bin\**demoprog_olimex_stm32h103.srec**
-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.
-===== Backdoor entry =====
+===== Firmware update procedure =====
-With USB as the communication interface, it is not practical to automatically support re-entry into the bootloader from a running user program. This is because the USB device in the user program is most likely different from the USB device in the OpenBLT bootloader. Therefore an alternative backdoor entry is pre-configured in the demo which was enabled by setting the following configuration macro in "config.h":
-<code>
+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:
-#define BOOT_BACKDOOR_HOOKS_ENABLE      (1)
-</code>
-Its implementation as such that to reactivate the bootloader you can keep button BUT on the board pressed during reset. Assuming the board is connected to your PC's USB port, you can check that the bootloader is active, by looking in the Window's Device Manager. It should show "WinUSB Bulk Device". Once active, you can reprogram your program with Microboot as described above.
-{{:manual:demos:check_bootloader_activation.gif|}}
+  * [[manual:usb_demo|Firmware updates using the USB communication interface]]

OpenBLT Bootloader

User Tools

Site Tools

Differences

Page Tools