Differences

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

--- manual:demos:nucleo_f303k8_gcc [2016/11/14 17:32]
voorburg [Development Environment]
+++ manual:demos:nucleo_f303k8_gcc [2017/07/11 10:33]
voorburg [Development Environment]
@@ Line 14: / Line 14: @@
 To compile the demo programs you can use the [[http://www.emblocks.org/|EmBitz]] development environment from Em::Blocks. The version that was used to create these demo programs was {{:manual:embitz_1_00.zip?linkonly|EmBitz version 1.00}}.
-To program the bootloader into the internal flash on 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.
 ===== Building and programming the Bootloader =====
-Before the bootloader can be used, it needs to be built and programmed into the STM32F207'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 STM32F303'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\ARMCM3_STM32F2_Olimex_STM32P207_GCC\**Boot**\ide\**stm32f207.ebp** from the Windows Explorer. To build the bootloader, select //Build -> Rebuild all target files// from the program menu.
+When using EmBitz, simply open the project file by double-clicking the file: \Target\Demo\ARMCM4_STM32F3_Nucleo_F303K8_GCC\**Boot**\ide\**stm32f303.ebp** from the Windows Explorer. To build the bootloader, select //Build -> Rebuild all target files// from the program menu.
-The bootloader program is now ready to be programmed into the internal flash memory of the STM32F207. Make sure the Segger J-Link debugger interface it connected to the JTAG connector on the Olimex STM32-P207 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.
+The bootloader program is now ready to be programmed into the internal flash memory of the STM32F303. 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.
 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:
-  * \Target\Demo\ARMCM3_STM32F2_Olimex_STM32P207_GCC\**Boot**\bin\**openblt_stm32f207.elf**
+  * \Target\Demo\ARMCM4_STM32F3_Nucleo_F303K8_GCC\**Boot**\bin\**openblt_stm32f303.elf**
-  * \Target\Demo\ARMCM3_STM32F2_Olimex_STM32P207_GCC\**Boot**\bin\**openblt_stm32f207.srec**
+  * \Target\Demo\ARMCM4_STM32F3_Nucleo_F303K8_GCC\**Boot**\bin\**openblt_stm32f303.srec**
 ===== Building the Demo Program =====
-When using EmBitz, simply open the project file by double-clicking the file: \Target\Demo\ARMCM3_STM32F2_Olimex_STM32P207_GCC\**Prog**\ide\**stm32f207.ebp** from the Windows Explorer. To build the demo program, select //Build -> Rebuild all target files// from the program's menu.
+When using EmBitz, simply open the project file by double-clicking the file: \Target\Demo\ARMCM4_STM32F3_Nucleo_F303K8_GCC\**Prog**\ide\**stm32f303.ebp** from the Windows Explorer. To build the demo program, select //Build -> Rebuild all target files// from the program's menu.
 The output file is
-  * \Target\Demo\ARMCM3_STM32F2_Olimex_STM32P207_GCC\**Prog**\bin\**demoprog_stm32f207.srec**
+  * \Target\Demo\ARMCM4_STM32F3_Nucleo_F303K8_GCC\**Prog**\bin\**demoprog_stm32f303.srec**
 ===== Firmware update procedure =====
-To download the demo program \Target\Demo\ARMCM3_STM32F2_Olimex_STM32P207_GCC\**Prog**\bin\**demoprog_stm32f207.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_Nucleo_F303K8_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:uart_demo|Firmware updates using the UART communication interface]]
   * [[manual:can_demo|Firmware updates using the CAN communication interface]]
-  * [[manual:sdcard_demo|Firmware updates from SD-card]]

OpenBLT Bootloader

User Tools

Site Tools

Differences

Page Tools