This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
manual:demos:olimex_stm32p207_gcc [2016/07/23 18:31] voorburg [Supported firmware update interfaces] |
manual:demos:olimex_stm32p207_gcc [2017/08/21 15:43] voorburg |
||
---|---|---|---|
Line 14: | Line 14: | ||
To program the bootloader into the internal flash on the STM32F207 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 STM32F207 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 you can use the [[http://www.emblocks.org/|EmBitz]] development environment from Em::Blocks. The version that was used to create these demo programs was {{:manual:embitz_0_42.zip?linkonly|EmBitz version 0.42}}. | + | To build the demo programs you can use the [[https://developer.arm.com/open-source/gnu-toolchain/gnu-rm|GNU ARM Embedded]] toolchain. |
- | Firmware update via the serial communication port are preconfigured to use USART3 on connector RS232_2 on the board. | + | Firmware updates via the serial communication port are preconfigured to use USART3 on connector RS232_2 on the board. |
+ | ===== 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 ===== | ||
Line 23: | Line 31: | ||
Before the bootloader can be used, it needs to be built and programmed into the STM32F207'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 STM32F207's internal flash memory. The steps in this section only need to be done once. | ||
- | When using EmBitz, simply open the project file by double-clicking the file: \Target\Demo\ARMCM3_STM32F2_Olimex_STM32P207_GCC\**Boot**\ide\**stm32f207.ebp** from the Windows Explorer. To build the bootloader, select //Build -> Rebuild all target files// from the program menu. | + | To build the bootloader, open a command prompt in directory **\Target\Demo\ARMCM3_STM32F2_Olimex_STM32P207_GCC\Boot\** and run the command: |
- | The bootloader program is now ready to be programmed into the internal flash memory of the STM32F207. Make sure the Segger J-Link debugger interface it connected to the JTAG connector on the Olimex STM32-P207 board and the other side to your PC via a USB cable. Next, select //Debug -> Start Debug Session (F8)// from EmBitz's program menu to flash the bootloader program. Once done, you can start the bootloader program by selecting //Debug -> Run (F5)// from the program's menu. | + | <code> |
+ | 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> |
+ | +++ Cleaning build environment | ||
+ | +++ Clean complete | ||
+ | +++ Assembling [startup_stm32f2xx.S] | ||
+ | +++ Compiling [main.c] | ||
+ | +++ Compiling [hooks.c] | ||
+ | ... | ||
+ | +++ Linking [openblt_stm32f207.elf] | ||
+ | .. | ||
+ | +++ Build complete [openblt_stm32f207.srec] | ||
+ | </code> | ||
+ | |||
+ | The bootloader program is now ready to be programmed into the internal flash memory of the STM32F207. Using your favorite programmer (i.e. OpenOCD, Segger J-Flash Lite or STM32 ST-Link utility), flash the bootloader using one of the following files, depending on what file type your programmer supports: | ||
* \Target\Demo\ARMCM3_STM32F2_Olimex_STM32P207_GCC\**Boot**\bin\**openblt_stm32f207.elf** | * \Target\Demo\ARMCM3_STM32F2_Olimex_STM32P207_GCC\**Boot**\bin\**openblt_stm32f207.elf** | ||
Line 35: | Line 59: | ||
===== Building the Demo Program ===== | ===== Building the Demo Program ===== | ||
- | When using EmBitz, simply open the project file by double-clicking the file: \Target\Demo\ARMCM3_STM32F2_Olimex_STM32P207_GCC\**Prog**\ide\**stm32f207.ebp** from the Windows Explorer. To build the demo program, select //Build -> Rebuild all target files// from the program's menu. | + | To build the user program, open a command prompt in directory **\Target\Demo\ARMCM3_STM32F2_Olimex_STM32P207_GCC\Prog\** and run the command: |
+ | |||
+ | <code> | ||
+ | make clean all | ||
+ | </code> | ||
+ | |||
+ | The expected output is: | ||
+ | |||
+ | <code> | ||
+ | +++ Cleaning build environment | ||
+ | +++ Clean complete | ||
+ | +++ Assembling [startup_stm32f2xx.S] | ||
+ | +++ Compiling [boot.c] | ||
+ | +++ Compiling [main.c] | ||
+ | ... | ||
+ | +++ Linking [demoprog_stm32f207.elf] | ||
+ | ... | ||
+ | +++ Build complete [demoprog_stm32f207.srec]</code> | ||
The output file is | The output file is | ||
Line 47: | Line 88: | ||
* [[manual:uart_demo|Firmware updates using the UART communication interface]] | * [[manual:uart_demo|Firmware updates using the UART 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]] | ||