Differences

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

--- manual:demos:olimex_stm32e407_truestudio [2018/06/07 23:14]
voorburg created
+++ manual:demos:olimex_stm32e407_truestudio [2020/02/06 16:32] (current)
voorburg
@@ Line 3: / Line 3: @@
 ===== Supported firmware update interfaces =====
-^ UART           ^ CAN             ^ USB          ^ TCP/IP       ^ SD-card      ^
+^ RS232          ^ CAN             ^ USB          ^ TCP/IP       ^ SD-card      ^
-| Yes            | Yes             | Yes          | Yes          | Yes          |
+| Yes            | Yes             | No           | No           | Yes          |
 ===== Development Environment =====
@@ Line 12: / Line 12: @@
 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.st.com/en/development-tools/st-link-v2.html|ST-LINK/V2]] debugger interface was used. However, this is not required if you have another means of programming the internal flash.
+To compile the demo programs you can use the [[https://atollic.com/truestudio/|Atollic TrueStudio]] development environment. Note the Atollic TrueStudio is cross-platform. The information outlined on this page applies to both Microsoft Windows and Linux users.
 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.
+===== Workspace creation in TrueStudio =====
-===== Toolchain configuration =====
+Two demo projects are included in the OpenBLT bootloader package. One for the bootloader itself and one for the demo user program. This user program is configured such that it can be programmed, into the internal flash memory of the microcontroller, during a firmware update with the bootloader.
-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.
+The first step in getting the the bootloader up-and-running, is the creation of the Eclipse workspace in TrueStudio. After starting TrueStudio, you are prompted to open a workspace. It is easiest to create a new one in the following directory: .\Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_TrueStudio\
-{{:manual:demos:makefile_toolpath.png?nolink&|}}
+{{:manual:demos:olimex_stm32e407_truestudio_workspace_creation.png?600|}}
+To import the demo programs into the workspace, select //File -> Import// from the program menu. Then select //General -> Existing Projects into Workspace//. On the next screen you select the following directory as the root directory: .\Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_TrueStudio\. Eclipse will automatically find the **Boot** and **Prog** projects and select them:
-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]].
+{{:manual:demos:olimex_stm32e407_truestudio_project_import.png?600|}}
+Click the //Finish// button to complete the project import operation.
 ===== 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 STM32F407ZG'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:
+Set the project as the active project in Eclipse. This is achieved by clicking the **Boot** project in the //Project Explorer// to select it. Next, select //Project -> Rebuild Project// from the menu to compile all the bootloader sources and link them together into the final executable.
-<code>
+The bootloader program is now ready to be programmed into the internal flash memory of the STM32F407ZG microcontroller. Make sure the Olimex STM32-E407 board is connected to your PC via a ST-LINK/V2 debugger interface. Next, select //Run -> Debug// from the menu to flash the bootloader program. This will launch the Debug perspective in Eclipse. Once done, you can start the bootloader program by selecting //Run -> Resume// from the menu.
-make clean all
-</code>
-The expected output is:
+Alternatively, you can use your favorite programmer to flash the bootloader using one of the following files, depending on what file type your programmer supports:
-<code>
+  * \Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_TrueStudio\**Boot**\Debug\**openblt_olimex_stm32e407.elf**
-+++ Compiling [hooks.o]
+  * \Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_TrueStudio\**Boot**\Debug\**openblt_olimex_stm32e407.srec**
-+++ Compiling [main.o]
-+++ Compiling [boot.o]
-...
-+++ Linking [openblt_olimex_stm32e407.elf]
-...
-+++ Build complete [openblt_olimex_stm32e407.srec]
-</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:
-  * \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**
 ===== Building the Demo Program =====
-To build the user program, open a command prompt in directory **\Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_GCC\Prog\** and run the command:
+Set the project as the active project in Eclipse. This is achieved by clicking the **Prog** project in the //Project Explorer// to select it. Next, select //Project -> Rebuild Project// from the menu to compile all the user program sources and link them together into the final executable.
-<code>
-make clean all
-</code>
-The expected output is:
-<code>
-+++ Compiling [boot.c]
-+++ Compiling [main.c]
-...
-+++ Linking [demoprog_olimex_stm32e407.elf]
-...
-+++ Build complete [demoprog_olimex_stm32e407.srec]
-</code>
 The output file is
-  * \Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_GCC\**Prog**\bin\**demoprog_olimex_stm32e407.srec**
+  * \Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_TrueStudio\**Prog**\Debug\**demoprog_olimex_stm32e407.srec**
 ===== Firmware update procedure =====
-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:
+To download the demo program \Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_TrueStudio\**Prog**\Debug\**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: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]]

OpenBLT Bootloader

User Tools

Site Tools

Differences

Page Tools