FW Update through IAP
The bootloader with IAP function can be downloaded into MCU, STM32F429VE using ST-LINK or JLINK through SWD Interface.
The application can be downloaded via bootloader with GUI.
| FW | Download Tool | |
| Bootloader | ST-LINK or JLINK | |
| Application | EVBKS5 GUI via Bootloader |
1. Program Memory Map
The MCU, STM32F429VET6 has 512KB of program memory, and the memory map for FW is as follows.
| Start Address | End Address | Size | Function | |
| 0x0800 0000 | 0x0800 BFFF | 48K Bytes | Bootloader program | |
| 0x0800 C000 | 0x0800 FFFF | 16K Bytes | Application partition and update information etc. | |
| 0x0801 0000 | 0x0801 FFFF | 64K Bytes | Application’s configuration | |
| 0x0802 0000 | 0x0803 FFFF | 128K Bytes | Application 0 | |
| 0x0804 0000 | 0x0805 FFFF | 128K Bytes | Application 1 | |
| 0x0806 0000 | 0x0807 FFFF | 128K Bytes | Application’s configuration |
2. Example FW
Extract the zip file after downloading
| Example | Partition | FW | |
| Bootloader | § EVBKS5_IAP_Bootloader | ||
| Motion/Moving-Target Detection | APP0 | § EVBKS5_MotionDetect_APP0 | |
| APP1 | |||
| Body/Human-Presence Sensing | APP0 | § EVBKS5_BodySensing_APP0 | |
| APP1 | |||
| USBHS_datatransfer | APP0 | ||
| APP1 |
3. Note for Application FW
Any one of the APP firmware, after compiling, will generate two image files that are defined to run at different flash address.
Take EVBKS5_BodySensing as an example.
When opening its project directory in the embedded compiling tool, users can find two projects that called APP0 and APP1.
These two projects are identical, the only difference between them is that they are supposed to run at different flash address.
When building the project, users MUST CHOOSE “Rebuild all target files “so that both APP projects can be compiled
and their bin files can be found under firmware’s Objects directory, as shown in Figure 6-1.
These two bin files are two image files that are used for updating EVBKS5 board.
WiFi IoT Module
Bluetooth Module
5G/LTE/CAT-M1/NB-IoT
