User Tools

Site Tools


manual:demos:olimex_em32g880f128stk_gcc

Differences

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

Link to this comparison view

Next revision
Previous revision
manual:demos:olimex_em32g880f128stk_gcc [2012/03/04 22:00]
voorburg created
manual:demos:olimex_em32g880f128stk_gcc [2023/12/04 22:43] (current)
voorburg [Supported firmware update interfaces]
Line 1: Line 1:
 ====== ARM-CM3 EFM32 Olimex EM-32G880F128-STK GCC ====== ====== ARM-CM3 EFM32 Olimex EM-32G880F128-STK GCC ======
 +
 +===== Supported firmware update interfaces =====
 +
 +^ RS232         ^ CAN            ^ USB         ^ TCP/​IP ​     ^ SD-card ​     ^ Modbus RTU   ^
 +| Yes           | No             | No          | No          | No           | No           |
  
 ===== Development Environment ===== ===== Development Environment =====
Line 9: Line 14:
 To program the bootloader into the internal flash on the EFM32G880 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 EFM32G880 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 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 EFM32G880'​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 EFM32G880'​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_EFM32_Olimex_EM32G880F128STK_GCC\**Boot**\cmd\**clean.bat**"​. Next, build the bootloader program by double-clicking the file "\Target\Demo\ARMCM3_EFM32_Olimex_EM32G880F128STK_GCC\**Boot**\cmd\**build.bat**"​. ​The output ​should look like:+To build the bootloader, open a command prompt in directory ​**\Target\Demo\ARMCM3_EFM32_Olimex_EM32G880F128STK_GCC\Boot\** ​and run the command: 
 + 
 +<​code>​ 
 +make clean all 
 +</​code>​ 
 + 
 +The expected ​output ​is: 
 <​code>​ <​code>​
 +++ Compiling [hooks.o] +++ Compiling [hooks.o]
Line 21: Line 42:
 +++ Compiling [boot.o] +++ Compiling [boot.o]
 ... ...
-+++ Linking [openbtl_olimex_efm32g880.elf]++++ Linking [openblt_olimex_efm32g880.elf]
 ... ...
-+++ Build complete [openbtl_olimex_efm32g880.bin]++++ Build complete [openblt_olimex_efm32g880.bin]
 </​code>​ </​code>​
  
 The bootloader program is now ready to be programmed into the internal flash memory of the EFM32G880. 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 EFM32G880. Using your favorite programmer, flash the bootloader using one of the following files, depending on what file type your programmer supports:
  
-  * \Target\Demo\ARMCM3_EFM32_Olimex_EM32G880F128STK_GCC\**Boot**\bin\**openbtl_olimex_efm32g880.elf** +  * \Target\Demo\ARMCM3_EFM32_Olimex_EM32G880F128STK_GCC\**Boot**\bin\**openblt_olimex_efm32g880.elf** 
-  * \Target\Demo\ARMCM3_EFM32_Olimex_EM32G880F128STK_GCC\**Boot**\bin\**openbtl_olimex_efm32g880.bin**+  * \Target\Demo\ARMCM3_EFM32_Olimex_EM32G880F128STK_GCC\**Boot**\bin\**openblt_olimex_efm32g880.bin**
  
-===== Configuring Microboot ​===== +===== Building the Demo Program ​=====
-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**"​. +To build the user program, open a command prompt in directory **\Target\Demo\ARMCM3_EFM32_Olimex_EM32G880F128STK_GCC\Prog\** and run the command:
-  * Click the "​**Settings**"​-button ​and select "​**OpenBLT using UART**"​ from the dropdown box. +
-  * Click the "​**Options**"​-button to configure the communication parameters. +
-    * Select the PC's **COM-port** that the board is connected to. +
-    * Set the baudrate to **9600** bits/sec.+
  
-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!+<​code>​ 
 +make clean all 
 +</​code>​ 
 +  
 +The expected output ​is:
  
-===== 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_EFM32_Olimex_EM32G880F128STK_GCC\**Prog**\cmd\**clean.bat**"​. Next, build the demo program by double-clicking the file "​\Target\Demo\ARMCM3_EFM32_Olimex_EM32G880F128STK_GCC\**Prog**\cmd\**build.bat**"​. The output should look like: 
 <​code>​ <​code>​
 +++ Compiling [boot.c] +++ Compiling [boot.c]
Line 54: Line 72:
  
 The output file is The output file is
 +
   * \Target\Demo\ARMCM3_EFM32_Olimex_EM32G880F128STK_GCC\**Prog**\bin\**demoprog_olimex_efm32g880.srec**   * \Target\Demo\ARMCM3_EFM32_Olimex_EM32G880F128STK_GCC\**Prog**\bin\**demoprog_olimex_efm32g880.srec**
  
 +===== Firmware update procedure =====
  
-To download ​this **demoprog_olimex_efm32g880.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_EFM32_Olimex_EM32G880F128STK_GCC\**Prog**\bin\" directory and select the **demoprog_olimex_efm32g880.srec** ​file to start the download. ​+To download the demo program \Target\Demo\ARMCM3_EFM32_Olimex_EM32G880F128STK_GCC\**Prog**\bin\**demoprog_olimex_efm32g880.srec** ​using the bootloader, follow the instructions in the following links, depending on the communication interface you intend to use:
  
-{{:manual:demos:​olimex_em32g880f128stk_download.gif?​|}}+  * [[manual:rs232_demo|Firmware updates using the RS232 communication interface]]
  
-Once the download completed, the newly programmed software will be started by the bootloader. You can verify this by checking that the test "​Olimex"​ blinks on the LCD. Congratulations! That's all there is to using the bootloader. 
manual/demos/olimex_em32g880f128stk_gcc.1330894815.txt.gz · Last modified: 2019/09/24 22:13 (external edit)