User Tools

Site Tools


manual:demos:stm32f3_discovery_gcc

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
manual:demos:stm32f3_discovery_gcc [2018/06/11 15:34]
voorburg [Building and programming the Bootloader]
manual:demos:stm32f3_discovery_gcc [2018/06/11 15:44]
voorburg [Firmware update procedure]
Line 40: Line 40:
 +++ Cleaning build environment +++ Cleaning build environment
 +++ Clean complete +++ Clean complete
-+++ Assembling [startup_stm32f30x.S]++++ Assembling [startup_stm32f303xc.s]
 +++ Compiling [main.c] +++ Compiling [main.c]
 +++ Compiling [hooks.c] +++ Compiling [hooks.c]
Line 51: Line 51:
 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: 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_Nucleo_F303K8_GCC\**Boot**\bin\**openblt_stm32f303.elf** +  * \Target\Demo\ARMCM4_STM32F3_Discovery_F303VC_GCC\**Boot**\bin\**openblt_stm32f303.elf** 
-  * \Target\Demo\ARMCM4_STM32F3_Nucleo_F303K8_GCC\**Boot**\bin\**openblt_stm32f303.srec**+  * \Target\Demo\ARMCM4_STM32F3_Discovery_F303VC_GCC\**Boot**\bin\**openblt_stm32f303.srec**
  
 ===== Building the Demo Program ===== ===== Building the Demo Program =====
  
-Set the project as the active project ​in Eclipse. This is achieved by clicking the **Prog** ​project in the //Project Explorer// to select itNext, select ​//Project -Rebuild Project// from the menu to compile all the user program sources and link them together into the final executable.+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 The output file is
  
-  * \Target\Demo\ARMCM4_STM32F3_Discovery_F303VC_TrueStudio\**Prog**\Debug\**demoprog_stm32f303.srec**+  * \Target\Demo\ARMCM4_STM32F3_Discovery_F303VC_GCC\**Prog**\bin\**demoprog_stm32f303.srec** 
  
 ===== Firmware update procedure ===== ===== Firmware update procedure =====
  
-To download the demo program \Target\Demo\ARMCM4_STM32F3_Discovery_F303VC_TrueStudio\**Prog**\Debug\**demoprog_stm32f303.srec** using the bootloader, follow the instructions in the following links, depending on the communication interface you intend to use:+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]]   * [[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. 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.
manual/demos/stm32f3_discovery_gcc.txt · Last modified: 2023/12/04 22:25 by voorburg