Differences

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

--- manual:demos:olimex_stm32h103_gcc [2016/10/24 13:14]
voorburg
+++ 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 =====
-^ UART           ^ CAN             ^ USB          ^ TCP/IP       ^ SD-card      ^
+^ RS232         ^ CAN            ^ USB         ^ TCP/IP      ^ SD-card      ^ Modbus RTU   ^
+| No            | No             | Yes         | No          | No           | No           |
-| 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 build the demo programs you can use the [[https://developer.arm.com/open-source/gnu-toolchain/gnu-rm|GNU ARM Embedded]] toolchain.
+===== Toolchain configuration =====
-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.
+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&|}}
-The demo programs are pre-configured for building with the {{:manual:arm-2013.11-24-arm-none-eabi.zip?linkonly|Codesourcery G++ Lite}} (Target OS EABI) toolchain. Alternatively, you can use the [[manual:demos:gcc_arm_embedded|GCC ARM Embedded]] toolchain.
+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 =====
@@ Line 38: / Line 30: @@
 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.
+To build the bootloader, open a command prompt in directory **\Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_GCC\Boot\** and run the command:
+<code>
-Batch files are added to aid in building the software program. First clean the bootloader program by double-clicking the file "\Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_GCC\**Boot**\cmd\**clean.bat**". Next, build the bootloader program by double-clicking the file "\Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_GCC\**Boot**\cmd\**build.bat**". The output should look like:
+make clean all
+</code>
+The expected output is:
 <code>
 +++ Compiling [hooks.o]
 +++ Compiling [main.o]
 +++ Compiling [boot.o]
 ...
++++ Linking [openblt_olimex_stm32h103.elf]
-+++ Linking [openbtl_olimex_stm32h103.elf]
 ...
++++ Build complete [openblt_olimex_stm32h103.srec]
-+++ Build complete [openbtl_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_STM32F1_Olimex_STM32H103_GCC\**Boot**\bin\**openblt_olimex_stm32h103.elf**
+  * \Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_GCC\**Boot**\bin\**openblt_olimex_stm32h103.srec**
-  * \Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_GCC\**Boot**\bin\**openbtl_olimex_stm32h103.elf**
-  * \Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_GCC\**Boot**\bin\**openbtl_olimex_stm32h103.srec**
 ===== Building 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_STM32F1_Olimex_STM32H103_GCC\**Prog**\cmd\**clean.bat**". Next, build the demo program by double-clicking the file "\Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_GCC\**Prog**\cmd\**build.bat**". The output should look like:
+To build the user program, open a command prompt in directory **\Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_GCC\Prog\** and run the command:
 <code>
+make clean all
+</code>
+The expected output is:
+<code>
 +++ Compiling [boot.c]
 +++ Compiling [main.c]
 ...
 +++ Linking [demoprog_olimex_stm32h103.elf]
 ...
 +++ Build complete [demoprog_olimex_stm32h103.srec]
 </code>
 The output file is
   * \Target\Demo\ARMCM3_STM32F1_Olimex_STM32H103_GCC\**Prog**\bin\**demoprog_olimex_stm32h103.srec**
 ===== Firmware update procedure =====
 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