====== ARM-CM4 STM32 STMicroelectronics STM32F3-Discovery GCC ======

===== Supported firmware update interfaces =====

^ RS232         ^ CAN            ^ USB         ^ TCP/IP      ^ SD-card      ^ Modbus RTU   ^
| No            | No             | Yes         | No          | No           | No           |

===== Development Environment =====

{{:manual:demos:stm32_discoveryf3.png? |}}

This demo is targeted towards the [[http://www.st.com/en/evaluation-tools/stm32f3discovery.html|STM32F3-Discovery]] board, with 256 Kb internal Flash EEPROM and 48 Kb internal RAM.

To program the bootloader into the internal flash, the on-board ST-Link debugger interface was used (USB ST-LINK connector). Firmware updates via USB use the USB USER connector on the board. This means that no additional hardware is needed, besides a standard micro-USB cable.

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 =====

Before the bootloader can be used, it needs to be built and programmed into the STM32F303'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\ARMCM4_STM32F3_Discovery_F303VC_GCC\Boot\** and run the command:

<code>
make clean all
</code>
 
The expected output is:

<code>
+++ Cleaning build environment
+++ Clean complete
+++ Assembling [startup_stm32f303xc.s]
+++ Compiling [main.c]
+++ Compiling [hooks.c]
...
+++ Linking [openblt_stm32f303.elf]
...
+++ Build complete [openblt_stm32f303.srec]
</code>

The bootloader program is now ready to be programmed into the internal flash memory of the STM32F303. 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\ARMCM4_STM32F3_Discovery_F303VC_GCC\**Boot**\bin\**openblt_stm32f303.elf**
  * \Target\Demo\ARMCM4_STM32F3_Discovery_F303VC_GCC\**Boot**\bin\**openblt_stm32f303.srec**

===== Building the Demo Program =====

To build the user program, open a command prompt in directory **\Target\Demo\ARMCM4_STM32F3_Discovery_F303VC_GCC\Prog\** and run the command:

<code>
make clean all
</code>
 
The expected output is:

<code>
+++ Cleaning build environment
+++ Clean complete
+++ Assembling [startup_stm32f303xc.s]
+++ Compiling [timer.c]
+++ Compiling [main.c]
...
+++ Linking [demoprog_stm32f303.elf]
...
+++ Build complete [demoprog_stm32f303.srec]
</code>

The output file is

  * \Target\Demo\ARMCM4_STM32F3_Discovery_F303VC_GCC\**Prog**\bin\**demoprog_stm32f303.srec**


===== Firmware update procedure =====

To download the demo program \Target\Demo\ARMCM4_STM32F3_Discovery_F303VC_GCC\**Prog**\bin\**demoprog_stm32f303.srec** using the bootloader, follow the instructions in the following links, depending on the communication interface you intend to use:

  * [[manual:usb_demo|Firmware updates using the USB communication interface]]

For firmware updates via USB, keep in mind that the USB cable should be connected to the USB USER connector on the board and not the USB ST-LINK connector.