User Tools

Site Tools


manual:demos:olimex_stm32e407_gcc

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:demos:olimex_stm32e407_gcc [2013/05/29 16:38]
voorburg [Development Environment]
manual:demos:olimex_stm32e407_gcc [2020/02/06 16:32] (current)
voorburg
Line 1: Line 1:
 ====== ARM-CM4 STM32 Olimex STM32E407 GCC ====== ====== ARM-CM4 STM32 Olimex STM32E407 GCC ======
 +
 +===== Supported firmware update interfaces =====
 +
 +^ RS232          ^ CAN             ^ USB          ^ TCP/​IP ​      ^ SD-card ​     ^
 +| Yes            | Yes             | No           | No           | Yes          |
  
 ===== Development Environment ===== ===== Development Environment =====
Line 11: Line 16:
 A [[https://​www.olimex.com/​Products/​Modules/​Interface/​MOD-USB-RS232/​|MOD-USB-RS232]] was connected to the EXT connector of the board to establish a serial communication connection between the board and the PC.  A [[https://​www.olimex.com/​Products/​Modules/​Interface/​MOD-USB-RS232/​|MOD-USB-RS232]] was connected to the EXT connector of the board to establish a serial communication connection between the board and the PC. 
  
-To compile ​the demo programs ​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.+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 =====
 +
 +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 ===== ===== Building and programming the Bootloader =====
 +
 Before the bootloader can be used, it needs to be built and programmed into the STM32F407'​s internal flash memory. The steps in this section only need to be done once. Before the bootloader can be used, it needs to be built and programmed into the STM32F407'​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\ARMCM4_STM32_Olimex_STM32E407_GCC\**Boot**\cmd\**clean.bat**"​. Next, build the bootloader program by double-clicking the file "\Target\Demo\ARMCM4_STM32_Olimex_STM32E407_GCC\**Boot**\cmd\**build.bat**"​. ​The output ​should look like:+To build the bootloader, open a command prompt in directory ​**\Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_GCC\Boot\** ​and run the command: 
 + 
 +<​code>​ 
 +make clean all 
 +</​code>​ 
 + 
 +The expected ​output ​is: 
 <​code>​ <​code>​
 +++ Compiling [hooks.o] +++ Compiling [hooks.o]
Line 23: Line 44:
 +++ Compiling [boot.o] +++ Compiling [boot.o]
 ... ...
-+++ Linking [openbtl_olimex_stm32e407.elf]++++ Linking [openblt_olimex_stm32e407.elf]
 ... ...
-+++ Build complete [openbtl_olimex_stm32e407.srec]++++ Build complete [openblt_olimex_stm32e407.srec]
 </​code>​ </​code>​
  
 The bootloader program is now ready to be programmed into the internal flash memory of the STM32F407. Using your favorite programmer, flash the bootloader using one of the following files, depending on what file type your programmer supports: The bootloader program is now ready to be programmed into the internal flash memory of the STM32F407. Using your favorite programmer, flash the bootloader using one of the following files, depending on what file type your programmer supports:
  
-  * \Target\Demo\ARMCM4_STM32_Olimex_STM32E407_GCC\**Boot**\bin\**openbtl_olimex_stm32e407.elf** +  * \Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_GCC\**Boot**\bin\**openblt_olimex_stm32e407.elf** 
-  * \Target\Demo\ARMCM4_STM32_Olimex_STM32E407_GCC\**Boot**\bin\**openbtl_olimex_stm32e407.srec**+  * \Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_GCC\**Boot**\bin\**openblt_olimex_stm32e407.srec**
  
 +===== Building the Demo Program =====
  
-===== Configuring Microboot ===== +To build the user program, open a command prompt in directory **\Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_GCC\Prog\** ​and run the command:
-The Microboot utility needs to be configured to connect to the correct COM-port ​and to communication at the correct baudrate:+
  
-  * Start Microboot by double-clicking "​\Host\**MicroBoot.exe**"​. +<​code>​ 
-  * Click the "​**Settings**"​-button and select "​**OpenBLT using UART**"​ from the dropdown box. +make clean all 
-  * Click the "​**Options**"​-button to configure the communication parameters. +</code> 
-    * Select the PC's **COM-port** that the board is connected to. +  
-    * Set the baudrate to **57600** bits/sec. +The expected output ​is:
- +
-Once you saved the settings by clicking the "​**OK**"​-button twice, 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\ARMCM4_STM32_Olimex_STM32E407_GCC\**Prog**\cmd\**clean.bat**"​. Next, build the demo program by double-clicking the file "​\Target\Demo\ARMCM4_STM32_Olimex_STM32E407_GCC\**Prog**\cmd\**build.bat**"​. The output should look like: 
 <​code>​ <​code>​
 +++ Compiling [boot.c] +++ Compiling [boot.c]
Line 57: Line 74:
  
 The output file is The output file is
-  * \Target\Demo\ARMCM4_STM32_Olimex_STM32E407_GCC\**Prog**\bin\**demoprog_olimex_stm32e407.srec** 
- 
- 
-To download this **demoprog_olimex_stm32e407.srec** file to the remaining flash memory using the bootloader, start the **Microboot** program and click the "​**Browse**"​-button. Browse to the "​\Target\Demo\ARMCM4_STM32_Olimex_STM32E407_GCC\**Prog**\bin\"​ directory and select the **demoprog_olimex_stm32e407.srec** file to start the download. ​ 
  
-{{:​manual:​demos:​olimex_stm32e407_download.gif?|}}+  * \Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_GCC\**Prog**\bin\**demoprog_olimex_stm32e407.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.+===== Firmware update procedure =====
  
-===== Firmware updates from SD-card ===== +To download ​the demo program \Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_GCC\**Prog**\bin\**demoprog_olimex_stm32e407.srec** using the bootloader, follow the instructions in the following links, depending on the communication interface you intend to use:
-In addition to the previously described update procedure with Microboot, the bootloader ​demo is configured for making firmware updates from an SD-cardThe procedure is:+
  
-  ​- Insert ​the SD-card into your PC and store the firmware file **demoprog_olimex_stm32e407.srec** on it. +  ​* [[manual:​rs232_demo|Firmware updates using the RS232 communication interface]] 
-  ​- Insert the SD-card ​into the card holder on the microcontroller board. +  * [[manual:​can_demo|Firmware updates using the CAN communication interface]] 
-  - Reset the microcontroller to start the firmware update. Once done, the newly programmed firmware is automatically started.+  ​* [[manual:​sdcard_demo|Firmware updates from SD-card]]
  
-The bootloader demo is configured to output log messages to a serial terminal. This enables you to view the progress of the firmware update with a terminal program such as Putty. The communication settings are the same as those described above in section //​Configuring Microboot//​. Additionally,​ the log messages are written to a file called **bootlog.txt** on the SD-card, which can optionally be checked for verification purposes. ​ 
  
-{{:​manual:​demos:​sdcard_firmware_update_logging.gif?​|}} 
manual/demos/olimex_stm32e407_gcc.1369838322.txt.gz · Last modified: 2019/09/24 22:13 (external edit)