manual:demos:nucleo_f091rc_gcc
Differences
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:nucleo_f091rc_gcc [2017/07/19 15:09] voorburg [Development Environment] |
manual:demos:nucleo_f091rc_gcc [2017/07/19 15:14] voorburg [Building and programming the Bootloader] |
||
|---|---|---|---|
| Line 16: | Line 16: | ||
| To program the bootloader into the internal flash, the on-board ST-Link debugger interface was used. Firmware updates via the serial communication port are preconfigured to use the virtual COM-port offered by the ST-Link. This means that no additional hardware is needed, besides a standard micro-USB cable. | To program the bootloader into the internal flash, the on-board ST-Link debugger interface was used. Firmware updates via the serial communication port are preconfigured to use the virtual COM-port offered by the ST-Link. This means that no additional hardware is needed, besides a standard micro-USB cable. | ||
| + | ===== 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 21: | Line 28: | ||
| Before the bootloader can be used, it needs to be built and programmed into the STM32F091'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 STM32F091'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\ARMCM0_STM32F0_Nucleo_F091RC_GCC\**Boot**\ide\**stm32f091.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\ARMCM0_STM32F0_Nucleo_F091RC_GCC\Boot\** and run the command: |
| + | |||
| + | <code> | ||
| + | make clean all | ||
| + | </code> | ||
| + | |||
| + | The expected output is: | ||
| - | The bootloader program is now ready to be programmed into the internal flash memory of the STM32F091. Make sure the board is connected to your PC via a micro-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> |
| + | +++ Cleaning build environment | ||
| + | +++ Clean complete | ||
| + | +++ Assembling [startup_stm32f0xx.S] | ||
| + | +++ Compiling [main.c] | ||
| + | +++ Compiling [hooks.c] | ||
| + | ... | ||
| + | +++ Linking [openblt_stm32f091.elf] | ||
| + | ... | ||
| + | +++ Build complete [openblt_stm32f091.srec] | ||
| - | 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\ARMCM0_STM32F0_Nucleo_F091RC_GCC\**Boot**\bin\**openblt_stm32f303.elf** | + | The bootloader program is now ready to be programmed into the internal flash memory of the STM32F091. Using your favorite programmer (i.e. OpenOCD or STM32 ST-Link utility), flash the bootloader using one of the following files, depending on what file type your programmer supports: |
| - | * \Target\Demo\ARMCM0_STM32F0_Nucleo_F091RC_GCC\**Boot**\bin\**openblt_stm32f303.srec** | + | |
| + | * \Target\Demo\ARMCM0_STM32F0_Nucleo_F091RC_GCC\**Boot**\bin\**openblt_stm32f091.elf** | ||
| + | * \Target\Demo\ARMCM0_STM32F0_Nucleo_F091RC_GCC\**Boot**\bin\**openblt_stm32f091.srec** | ||
| ===== Building the Demo Program ===== | ===== Building the Demo Program ===== | ||
manual/demos/nucleo_f091rc_gcc.txt · Last modified: 2023/12/04 22:17 by voorburg
Page Tools
