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 [2015/07/26 12:46]
voorburg
manual:demos:olimex_stm32e407_gcc [2020/02/06 16:32]
voorburg
Line 1: Line 1:
 ====== ARM-CM4 STM32 Olimex STM32E407 GCC ====== ====== ARM-CM4 STM32 Olimex STM32E407 GCC ======
- 
- 
  
 ===== Supported firmware update interfaces ===== ===== Supported firmware update interfaces =====
  
-UART           ^ CAN             ^ USB          ^ TCP/​IP ​      ^ SD-card ​     ^ +RS232          ​^ CAN             ^ USB          ^ TCP/​IP ​      ^ SD-card ​     ^ 
- +| Yes            | Yes             ​| ​No           No           | Yes          |
-| Yes            | Yes             ​| ​Yes          ​Yes          ​| Yes          | +
- +
  
 ===== Development Environment ===== ===== Development Environment =====
- 
- 
  
 {{:​manual:​demos:​olimex_stm32e407.jpg?​200 |}} {{:​manual:​demos:​olimex_stm32e407.jpg?​200 |}}
- 
- 
  
 This demo is targeted towards the [[https://​www.olimex.com/​Products/​ARM/​ST/​STM32-E407/​|Olimex STM32E407]] board, with 1 MB internal Flash EEPROM and 196 kB internal RAM. This demo is targeted towards the [[https://​www.olimex.com/​Products/​ARM/​ST/​STM32-E407/​|Olimex STM32E407]] board, with 1 MB internal Flash EEPROM and 196 kB internal RAM.
- 
- 
  
 To program the bootloader into the internal flash on the STM32F407 microcontroller,​ the [[http://​www.segger.com/​development-tools.html|Segger J-Link]] JTAG interface was used. However, this is not required if you have another means of programming the internal flash. To program the bootloader into the internal flash on the STM32F407 microcontroller,​ the [[http://​www.segger.com/​development-tools.html|Segger J-Link]] JTAG interface was used. However, this is not required if you have another means of programming the internal flash.
- 
- 
  
 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 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 compile the demo programs with {{:​manual:​arm-2013.11-24-arm-none-eabi.zip?​linkonly|Codesourcery G++ Lite}} (Target OS EABI), you can invoke ​the make utility from the command line.+The demo programs ​are configured for building ​with a MakefileBefore 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 =====
Line 40: Line 31:
 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.
  
 +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>​
  
-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:+The expected ​output ​is:
  
 <​code>​ <​code>​
- 
 +++ Compiling [hooks.o] +++ Compiling [hooks.o]
- 
 +++ Compiling [main.o] +++ Compiling [main.o]
- 
 +++ Compiling [boot.o] +++ Compiling [boot.o]
- 
 ... ...
- ++++ Linking [openblt_olimex_stm32e407.elf]
-+++ Linking [openbtl_olimex_stm32e407.elf] +
 ... ...
- ++++ Build complete [openblt_olimex_stm32e407.srec]
-+++ Build complete [openbtl_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_STM32F4_Olimex_STM32E407_GCC\**Boot**\bin\**openblt_olimex_stm32e407.elf** 
- +  * \Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_GCC\**Boot**\bin\**openblt_olimex_stm32e407.srec**
-  ​* \Target\Demo\ARMCM4_STM32_Olimex_STM32E407_GCC\**Boot**\bin\**openbtl_olimex_stm32e407.elf** +
- +
-  * \Target\Demo\ARMCM4_STM32_Olimex_STM32E407_GCC\**Boot**\bin\**openbtl_olimex_stm32e407.srec** +
- +
- +
- +
  
 ===== Building the Demo Program ===== ===== 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\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:+To build the user program, open a command prompt in directory ​**\Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_GCC\Prog\** ​and run the command:
  
 <​code>​ <​code>​
 +make clean all
 +</​code>​
 + 
 +The expected output is:
  
 +<​code>​
 +++ Compiling [boot.c] +++ Compiling [boot.c]
- 
 +++ Compiling [main.c] +++ Compiling [main.c]
- 
 ... ...
- 
 +++ Linking [demoprog_olimex_stm32e407.elf] +++ Linking [demoprog_olimex_stm32e407.elf]
- 
 ... ...
- 
 +++ Build complete [demoprog_olimex_stm32e407.srec] +++ Build complete [demoprog_olimex_stm32e407.srec]
- 
 </​code>​ </​code>​
- 
- 
  
 The output file is The output file is
  
-  * \Target\Demo\ARMCM4_STM32_Olimex_STM32E407_GCC\**Prog**\bin\**demoprog_olimex_stm32e407.srec** +  * \Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_GCC\**Prog**\bin\**demoprog_olimex_stm32e407.srec**
- +
  
 ===== Firmware update procedure ===== ===== Firmware update procedure =====
  
-To download the demo program \Target\Demo\ARMCM4_STM32_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: +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:
- +
- +
- +
-  * [[manual:​uart_demo|Firmware updates using the UART communication interface]]+
  
 +  * [[manual:​rs232_demo|Firmware updates using the RS232 communication interface]]
   * [[manual:​can_demo|Firmware updates using the CAN communication interface]]   * [[manual:​can_demo|Firmware updates using the CAN communication interface]]
- 
-  * [[manual:​net_demo|Firmware updates using the TCP/IP communication interface]] 
- 
-  * [[manual:​usb_demo|Firmware updates using the USB communication interface]] 
- 
   * [[manual:​sdcard_demo|Firmware updates from SD-card]]   * [[manual:​sdcard_demo|Firmware updates from SD-card]]
  
  
manual/demos/olimex_stm32e407_gcc.txt · Last modified: 2020/02/06 16:32 by voorburg