manual:demos:olimex_stm32e407_gcc
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
manual:demos:olimex_stm32e407_gcc [2017/08/15 18:24] voorburg [Development Environment] |
manual:demos:olimex_stm32e407_gcc [2019/09/24 22:12] 127.0.0.1 external edit |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| ^ UART ^ CAN ^ USB ^ TCP/IP ^ SD-card ^ | ^ UART ^ CAN ^ USB ^ TCP/IP ^ SD-card ^ | ||
| - | | Yes | Yes | Yes | Yes | Yes | | + | | Yes | Yes | No | No | Yes | |
| ===== Development Environment ===== | ===== Development Environment ===== | ||
| Line 17: | Line 17: | ||
| To build the demo programs you can use the [[https://developer.arm.com/open-source/gnu-toolchain/gnu-rm|GNU ARM Embedded]] toolchain. | 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 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 STM32F407'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\ARMCM4_STM32F4_Olimex_STM32E407_GCC\**Boot**\cmd\**clean.bat**". Next, build the bootloader program by double-clicking the file "\Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_GCC\**Boot**\cmd\**build.bat**". The output should look like: | + | To build the bootloader, open a command prompt in directory **\Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_GCC\Boot\** and run the command: |
| + | |||
| + | <code> | ||
| + | make clean all | ||
| + | </code> | ||
| + | |||
| + | The expected output is: | ||
| <code> | <code> | ||
| Line 40: | Line 56: | ||
| ===== Building the Demo Program ===== | ===== Building 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\ARMCM4_STM32F4_Olimex_STM32E407_GCC\**Prog**\cmd\**clean.bat**". Next, build the demo program by double-clicking the file "\Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_GCC\**Prog**\cmd\**build.bat**". The output should look like: | + | To build the user program, open a command prompt in directory **\Target\Demo\ARMCM4_STM32F4_Olimex_STM32E407_GCC\Prog\** and run the command: |
| + | |||
| + | <code> | ||
| + | make clean all | ||
| + | </code> | ||
| + | |||
| + | The expected output is: | ||
| <code> | <code> | ||
manual/demos/olimex_stm32e407_gcc.txt · Last modified: 2020/02/06 16:32 by voorburg
Page Tools
