The Bootloader module provides APIs to write bootloader applications for various boot media like QSPI, UART, SOC memory etc.
Features Supported
- QSPI Boot
- UART Boot
- API to parse multicore appimage
- Separate APIs to boot self and non-self cores
SysConfig Features
- Note
- It is strongly recommend to use SysConfig where it is available instead of using direct SW API calls. This will help simplify the SW application and also catch common mistakes early in the development cycle.
- Bootloader instance name
- Boot Media to be used
- Boot Image offset
Features not Supported
R5 Dual Core Support
- With the configuration used in MCU SDK to generate the app images, the RBL brings the R5 Lock Step Mode.
- The SBL runs on R5 core in Lock Step Mode.
- The SBL will switch to Dual core or continue in lock step mode depending on whether App Image loaded by SBL contains the R5 Core 1 image or not.
- If the App Image to be loaded contains the R5 core 1 binary
- The SBL will configure R5 to switch to Dual Core Mode.
- At the end of SBL flow, The Application image of R5 will start running in the dual core mode.
- If the App Image doesnot contain the R5 core 1 binary
- The SBL will not configure R5 to switch to Dual core Mode
- At the end of SBL flow, The Application image of R5 will start running in the lock step mode.
- Refer the IPC example which configures the R5 in Dual Core mode. IPC Notify Echo
Example Usage
Include the below file to access the APIs
Instance Open Example
Booting Cores Example
Instance Close Example
API
APIs for BOOTLOADING CPUs