If simply conventional debug and the evaluation of a separate function of RX72N are needed, refer to Generate new project (bare metal).
Understand the memory map and the operation of the firmware of RX72N Envision Kit
Understand the memory map and the operation of the firmware of RX72N Envision Kit by referring to the following Design memo
Memory map definition with the initial firmware of RX72N Envision Kit
Operation difference between initial firmware and after updating.
Combine firmwares and create updater
How to debug is effective when debugging, but is not effective when mass producing.
This is because the following two challenges exist.
When mass producing, downloading takes time and effort.
When operating after the mass production, data amount during updater distribution increases.(Communication fee increases)
Create tools with following functions as countermeasures for each challenge.
Create 1 sheet of MOT file for mass production by combining Bootloader, user application (for execute area) and user application(for temporary area).
Create RSU file (original) for the time of mass production and operation by converting any user application binary.
MOT file is a hexadecimally expressed text. RSU file is a binary one. As the file size containing 2MB data for 1 side of RX72N bank, MOT file is 4MB and RSU file is 2MB.
When assuming especially automatic firmware distribution via the internet, the usage fee of data distribution server such as AWS(Amazon Web Services) is a pay-as-you-go billing system, distributed data needs to be compressed as much as possible.
Customize firmware
All you have to do is to change a source code and execute compile and build.
For example, you can try by changing the version data included in aws_demos.