Differences

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

--- manual:demos:olimex_stm32h103_gcc [2011/12/17 11:42]
voorburg [Backdoor entry]
+++ manual:demos:olimex_stm32h103_gcc [2023/12/04 22:19] (current)
voorburg [Supported firmware update interfaces]
@@ Line 1: / Line 1: @@
 ====== ARM-CM3 STM32 Olimex STM32H103 GCC ======
+===== Supported firmware update interfaces =====
+^ RS232         ^ CAN            ^ USB         ^ TCP/IP      ^ SD-card      ^ Modbus RTU   ^
+| No            | No             | Yes         | No          | No           | No           |
 ===== Development Environment =====
@@ Line 10: / Line 15: @@
 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 build the demo programs you can use the [[https://developer.arm.com/open-source/gnu-toolchain/gnu-rm|GNU ARM Embedded]] toolchain.
-To compile the demo program with [[http://www.mentor.com/embedded-software/sourcery-tools/sourcery-codebench/lite-edition|Codesourcery G++ Lite]] (Target OS EABI), you can invoke the make utility from the command line.
+===== Toolchain configuration =====
+The demo programs are configured for building with a Makefile. Before attempting to perform a build, update the location of the toolchain binaries (i.e. //arm-none-eabi-gcc//) in the Makefile. It is set in variable **TOOL_PATH**. If the toolchain binaries are available on the path, then the **TOOL_PATH** variable can be left empty.
+{{:manual:demos:makefile_toolpath.png?nolink&|}}
+It is assumed that tools such as GNU //make// and //rm// are installed and available on the path. For (Ubuntu) Linux users this can be achieved by running command: //sudo apt-get install build-essential//. Windows users can install the [[https://gnu-mcu-eclipse.github.io/windows-build-tools/|GNU MCU Eclipse Windows Build Tools]].
 ===== 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.
-Batch files are added to aid in building the software program. First clean the bootloader program by double-clicking the file "\Target\Demo\ARMCM3_STM32_Olimex_STM32H103_GCC\**Boot**\cmd\**clean.bat**". Next, build the bootloader program by double-clicking the file "\Target\Demo\ARMCM3_STM32_Olimex_STM32H103_GCC\**Boot**\cmd\**build.bat**". The output should look like:
+To build the bootloader, open a command prompt in directory **\Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_GCC\Boot\** and run the command:
+<code>
+make clean all
+</code>
+The expected output is:
 <code>
 +++ Compiling [hooks.o]
@@ Line 22: / Line 43: @@
 +++ Compiling [boot.o]
 ...
-+++ Linking [openbtl_olimex_stm32h103.elf]
++++ Linking [openblt_olimex_stm32h103.elf]
 ...
-+++ Build complete [openbtl_olimex_stm32h103.srec]
++++ Build complete [openblt_olimex_stm32h103.srec]
 </code>
 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_GCC\**Boot**\bin\**openbtl_olimex_stm32h103.elf**
+  * \Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_GCC\**Boot**\bin\**openblt_olimex_stm32h103.elf**
-  * \Target\Demo\ARMCM3_STM32_Olimex_STM32H103_GCC\**Boot**\bin\**openbtl_olimex_stm32h103.srec**
+  * \Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_GCC\**Boot**\bin\**openblt_olimex_stm32h103.srec**
-===== USB driver installation =====
+===== Building the Demo Program =====
-..TODO driver installation....link to seperate page with screenshots..
+To build the user program, open a command prompt in directory **\Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_GCC\Prog\** and run the command:
-===== Configuring Microboot =====
+<code>
-The Microboot utility needs to be configured to use USB as the communication interface:
+make clean all
+</code>
-  * Start Microboot by double-clicking "\Host\**MicroBoot.exe**".
-  * Click the "**Settings**"-button and select "**OpenBLT using USB**" from the dropdown box.
+The expected output is:
-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 =====
-Batch files are added to aid in building the demo program. First clean the demo program by double-clicking the file "\Target\Demo\ARMCM3_STM32_Olimex_STM32H103_GCC\**Prog**\cmd\**clean.bat**". Next, build the demo program by double-clicking the file "\Target\Demo\ARMCM3_STM32_Olimex_STM32H103_GCC\**Prog**\cmd\**build.bat**". The output should look like:
 <code>
 +++ Compiling [boot.c]
@@ Line 56: / Line 73: @@
 The output file is
-  * \Target\Demo\ARMCM3_STM32_Olimex_STM32H103_GCC\**Prog**\bin\**demoprog_olimex_stm32h103.srec**
+  * \Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_GCC\**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_GCC\**Prog**\bin\" directory and select the **demoprog_olimex_stm32h103.srec** file to start the download.
+===== Firmware update procedure =====
-{{:manual:demos:olimex_stm32h103_download.gif?|}}
-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 =====
-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 and was enabled by setting the following configuration macro in "config.h":
-<code>
-#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|}}
+To download the demo program \Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_GCC\**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:
+  * [[manual:usb_demo|Firmware updates using the USB communication interface]]

OpenBLT Bootloader

User Tools

Site Tools

Differences

Page Tools