Differences

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

--- manual:demos:olimex_stm32p405_gcc [2017/07/18 11:10]
voorburg [Development Environment]
+++ manual:demos:olimex_stm32p405_gcc [2023/12/04 22:28] (current)
voorburg [Supported firmware update interfaces]
@@ Line 3: / Line 3: @@
 ===== Supported firmware update interfaces =====
-^ UART           ^ CAN             ^ USB          ^ TCP/IP       ^ SD-card      ^
+^ RS232         ^ CAN            ^ USB         ^ TCP/IP      ^ SD-card      ^ Modbus RTU   ^
-| Yes            | Yes             | Yes          | No           | Yes          |
+| Yes           | Yes            | Yes         | No          | Yes          | No           |
 ===== Development Environment =====
@@ Line 15: / Line 15: @@
 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 =====
@@ Line 20: / Line 29: @@
 Before the bootloader can be used, it needs to be built and programmed into the STM32F405'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\ARMCM4_STM32F4_Olimex_STM32P405_GCC\**Boot**\ide\**STM32P405.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\ARMCM4_STM32F4_Olimex_STM32P405_GCC\Boot\** and run the command:
-The bootloader program is now ready to be programmed into the internal flash memory of the STM32F405. Make sure the Segger J-Link debugger interface it connected to the JTAG connector on the Olimex STM32-P405 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_stm32f4xx.S]
++++ Compiling [usbd_usr.c]
++++ Compiling [usb_bsp.c]
+...
++++ Linking [openblt_olimex_stm32p405.elf]
+...
++++ Build complete [openblt_olimex_stm32p405.srec]
+</code>
+The bootloader program is now ready to be programmed into the internal flash memory of the STM32F405. 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\ARMCM4_STM32F4_Olimex_STM32P405_GCC\**Boot**\bin\**openblt_olimex_stm32p405.elf**
   * \Target\Demo\ARMCM4_STM32F4_Olimex_STM32P405_GCC\**Boot**\bin\**openblt_olimex_stm32p405.srec**
 ===== Building the Demo Program =====
-When using EmBitz, simply open the project file by double-clicking the file: \Target\Demo\ARMCM4_STM32F4_Olimex_STM32P405_GCC\**Prog**\ide\**STM32P405.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\ARMCM4_STM32F4_Olimex_STM32P405_GCC\Prog\** and run the command:
+<code>
+make clean all
+</code>
+The expected output is:
+<code>
++++ Cleaning build environment
++++ Clean complete
++++ Assembling [startup_stm32f4xx.S]
++++ Compiling [boot.c]
++++ Compiling [main.c]
+...
++++ Linking [demoprog_olimex_stm32p405.elf]
+...
++++ Build complete [demoprog_olimex_stm32p405.srec]
+</code>
 The output file is
   * \Target\Demo\ARMCM4_STM32F4_Olimex_STM32P405_GCC\**Prog**\bin\**demoprog_olimex_stm32p405.srec**
 ===== Firmware update procedure =====
@@ Line 43: / Line 84: @@
 To download the demo program \Target\Demo\ARMCM4_STM32F4_Olimex_STM32P405_GCC\**Prog**\bin\**demoprog_olimex_stm32p405.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:usb_demo|Firmware updates using the USB communication interface]]

OpenBLT Bootloader

User Tools

Site Tools

Differences

Page Tools