Build Configurations; Figure 26: Location Of Firmware Image Files - Renesas FreeRTOS DA16200 User Manual

UM-WI-056
DA16200 DA16600 FreeRTOS Getting Started Guide
*----------------------------------------
*Image Generate success
*----------------------------------------
[CM.3.secuboot.bat] END
[.\util\mk_sboot_image.bat] END
*========================================
*Post-Build Clean Start for Windows
*========================================
Start mk_sboot_image_clean.bat
*========================================
*Post-Build End for Windows
*========================================
arm-none-eabi-size --format=berkeley "da16200.elf"
text data bss
1145404 10224 141152 1296780
15:56:21 Build Finished. 0 errors, 0 warnings. (took 4m:10s.749ms)
There are two f irmware images created by the build process and they are stored in the
<sdk_root_directory>/<project_path>/img/ directory. For Example:
DA16200_FBOOT-GEN01-01-c7f4c6cc22_W25Q32JW.img
DA16200_FRTOS-GEN01-01-07b24d20f4-006526.img
The images can be f ound in the directory show in
FBOOT is the bootloader image which is used to initialize the DA16200 and launch the main
f irmware.
●
The bootloader image should be loaded f irst into the f lash of a new device
●
The bootloader image contains SFDP (f lash specif ic) inf ormation. Note that the bootloader must
be loaded into f lash bef ore loading any other images
●
When updating the SDK, always load the bootloader image f irst
FRTOS is the main f irmware image which includes the RTOS and user applications.
5.5.1

Build Configurations

There are several types of build conf iguration f or DA16200 / DA16600 SDK project. Release and
Debug conf igurations are almost the same except that the Release build conf igurations disable the
console (UART0) input and output.
User Manual
CFR0012
dec hex filename
13c98c da16200.elf
Figure

Figure 26: Location of Firmware Image Files

Revision 1.8
42 of 106
26.
© 2023 Renesas Electronics
Aug. 18, 2023