User Tools

Site Tools


manual:demos:olimex_stm32p103_truestudio

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_stm32p103_truestudio [2018/06/06 22:10]
voorburg [Development Environment]
manual:demos:olimex_stm32p103_truestudio [2020/02/06 16:24] (current)
voorburg
Line 3: Line 3:
 ===== 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             | No           | No           | Yes          |
  
Line 16: Line 16:
 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. 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.
  
-===== Toolchain configuration ​=====+===== Workspace creation in TrueStudio ​=====
  
-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 paththen the **TOOL_PATH** variable can be left empty.+Two demo projects ​are included in the OpenBLT bootloader package. One for the bootloader itself and one for the demo user programThis user program ​is configured such that it can be programmed, into the internal flash memory of the microcontrollerduring a firmware update with the bootloader.
  
-{{:​manual:​demos:makefile_toolpath.png?​nolink&​|}}+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\ARMCM3_STM32F1_Olimex_STM32P103_TrueStudio\
  
 +{{:​manual:​demos:​olimex_stm32p103_truestudio_workspace_creation.png?​600|}}
  
-It is assumed that tools such as GNU //make// and //rm// are installed and available on the pathFor (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]].+To import the demo programs into the workspace, select ​//File -> Import// from the program menuThen select ​//General ​-> Existing Projects into Workspace//. On the next screen you select the following directory as the root directory: .\Target\Demo\ARMCM3_STM32F1_Olimex_STM32P103_TrueStudio\Eclipse will automatically find the **Boot** and **Prog** projects and select them: 
 + 
 +{{:​manual:​demos:​olimex_stm32p103_truestudio_project_import.png?​600|}} 
 + 
 +Click the //Finish// button to complete the project import operation.
  
 ===== 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 STM32F103'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 STM32F103RB'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_STM32P103_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 STM32F103RB microcontroller. Make sure the Olimex STM32-P103 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:+
  
-<​code>​ +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:
-+++ Compiling [hooks.o] +
-+++ Compiling [main.o] +
-+++ Compiling [boot.o] +
-... +
-+++ Linking [openblt_olimex_stm32p103.elf] +
-... +
-+++ Build complete [openblt_olimex_stm32p103.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_STM32P103_TrueStudio\**Boot**\Debug\**openblt_olimex_stm32p103.elf** 
- +  * \Target\Demo\ARMCM3_STM32F1_Olimex_STM32P103_TrueStudio\**Boot**\Debug\**openblt_olimex_stm32p103.srec**
-  ​* \Target\Demo\ARMCM3_STM32F1_Olimex_STM32P103_GCC\**Boot**\bin\**openblt_olimex_stm32p103.elf** +
-  * \Target\Demo\ARMCM3_STM32F1_Olimex_STM32P103_GCC\**Boot**\bin\**openblt_olimex_stm32p103.srec**+
  
 ===== Building the Demo Program ===== ===== Building the Demo Program =====
  
-To build the user program, open a command prompt ​in directory ​**\Target\Demo\ARMCM3_STM32F1_Olimex_STM32P103_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 itNext, 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_stm32p103.elf] +
-... +
-+++ Build complete [demoprog_olimex_stm32p103.srec] +
-</code>+
  
 The output file is The output file is
  
-  * \Target\Demo\ARMCM3_STM32F1_Olimex_STM32P103_GCC\**Prog**\bin\**demoprog_olimex_stm32p103.srec**+  * \Target\Demo\ARMCM3_STM32F1_Olimex_STM32P103_TrueStudio\**Prog**\Debug\**demoprog_olimex_stm32p103.srec**
  
 ===== Firmware update procedure ===== ===== Firmware update procedure =====
  
-To download the demo program \Target\Demo\ARMCM3_STM32F1_Olimex_STM32P103_GCC\**Prog**\bin\**demoprog_olimex_stm32p103.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\ARMCM3_STM32F1_Olimex_STM32P103_TrueStudio\**Prog**\Debug\**demoprog_olimex_stm32p103.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:​sdcard_demo|Firmware updates from SD-card]]   * [[manual:​sdcard_demo|Firmware updates from SD-card]]
  
  
manual/demos/olimex_stm32p103_truestudio.1528315805.txt.gz · Last modified: 2019/09/24 22:13 (external edit)