Introduction

This is a bootloader example, which shows an example of booting RTOS/NORTOS applications on DM R5, MCU R5 C75 and A53 cores.

The booting is done in 2 stages(2 bootloader applications).

The stage1 of the bootloader runs from the HSM RAM. It boots MCU R5 with RTOS/NORTOS application and initializes the DDR. Then it loads the stage2 of the bootloader to DDR and stats running it.
The stage2 of the bootloader boots RTOS/NORTOS on A53 and then self loads DM firmware on the DM R5.

The SBL uses 7 appimages

tiboot3.bin with SBL stage1, TIFS, BoardConfig
Appimage for SBL stage2
Appimage for MCU R5
Appimage for HSM M4
Appimage for C75
DM firmware appimage for DM R5
Appimage for A53

Supported Combinations

Parameter	Value
CPU + OS	r5fss0-0 nortos
Toolchain	ti-arm-clang
Board	am62ax-sk
Example folder	examples/drivers/boot/sbl_ospi_nand_multistage

Steps to Run the Example

Build the example

Since this is a bootloader, the example will be run every time you boot an application using this example. It is run from a OSPI boot media unlike other examples which are usually loaded with CCS. Nevertheless, you can build this example like you do for the others using makefile or build it via CCS by importing as a project.

When using CCS projects to build, import the CCS project for the required combination and build it using the CCS project menu (see Using SDK with CCS Projects).
When using makefiles to build, note the required combination and build using make command (see Using SDK with Makefiles)
Refer to the page Basic steps to flash files to flash this bootloader along with the application to boot.

Create HSM Appimage

Create a HSM Appimage
This can be done by running the makefile at {SDK_INSTALL_PATH}/tools/boot/HSMAppimageGen
Refer HSM Appimage Generator Tool for more details

Run the example

This example is the SBL which needs to be flashed on the EVM flash, along with sample application images for R5, M4 CPUs and A53 Appimage.

Note: For HS-SE device, use default_sbl_ospi_nand_hs.cfg as the cfg file.; For HS-FS device, use default_sbl_ospi_nand_hs_fs.cfg as the cfg file.

There is a default flash config file as shown below which flashes this SBL and the IPC RPMsg echo applications
```
  ${SDK_INSTALL_PATH}/tools/boot/sbl_prebuilt/@VAR_SK_LP_BOARD_NAME_LOWER/default_sbl_ospi_nand.cfg
```
Make sure IPC rpms echo application is built before running the flash script. (see IPC RP Message Echo)
To flash to the EVM, refer to Flash a Hello World example . Only when giving the flash config file, point to the default_sbl_ospi_nand.cfg shown above.

Example, assuming SDK is installed at C:/ti/mcu_plus_sdk and this example and IPC application is built using makefiles, and RTOS Appimage is already created, in Windows,

  cd C:/ti/mcu_plus_sdk/tools/boot
  python uart_uniflash.py -p COM13 --cfg=C:/ti/mcu_plus_sdk/tools/boot/sbl_prebuilt/@VAR_SK_LP_BOARD_NAME_LOWER/default_sbl_ospi_nand.cfg

If Linux PC is used, assuming SDK is installed at ~/ti/mcu_plus_sdk

  cd ~/ti/mcu_plus_sdk/tools/boot
  python uart_uniflash.py -p /dev/ttyUSB0 --cfg=~/ti/mcu_plus_sdk/tools/boot/sbl_prebuilt/@VAR_SK_LP_BOARD_NAME_LOWER/default_sbl_ospi_nand.cfg

This example is the SBL which needs to be flashed on the EVM flash, along with sample application images for DM R5, MCU R5, C75, HSM M4 CPUs and A53 Appimage.
Note
For HS-SE device, use default_sbl_ospi_nand_hs.cfg as the cfg file.

For HS-FS device, use default_sbl_ospi_nand_hs_fs.cfg as the cfg file.
There is a default flash config file as shown below which flashes this SBL and the IPC RPMsg echo applications
```
  ${SDK_INSTALL_PATH}/tools/boot/sbl_prebuilt/am62ax-sk/default_sbl_ospi_nand_hs_fs.cfg
```
Make sure IPC rpmsg echo application is built before running the flash script. (see IPC RP Message Echo)

Note: For IPC rpmsg echo, the resource table entity must be placed at the beginning of remoteproc memory section.

To flash to the EVM, refer to Flash a Hello World example . Only when giving the flash config file, point to the default_sbl_ospi_nand_hs_fs.cfg shown above.
Example, assuming SDK is installed at C:/ti/mcu_plus_sdk and this example and IPC application is built using makefiles, and RTOS Appimage is already created, in Windows,
```
  cd C:/ti/mcu_plus_sdk/tools/boot
  python uart_uniflash.py -p COM13 --cfg=C:/ti/mcu_plus_sdk/tools/boot/sbl_prebuilt/am62ax-sk/default_sbl_ospi_nand_hs_fs.cfg
```

If Linux PC is used, assuming SDK is installed at ~/ti/mcu_plus_sdk

  cd ~/ti/mcu_plus_sdk/tools/boot
  python uart_uniflash.py -p /dev/ttyUSB0 --cfg=~/ti/mcu_plus_sdk/tools/boot/sbl_prebuilt/am62ax-sk/default_sbl_ospi_nand_hs_fs.cfg

Boot the EVM in OSPI NAND boot mode.

Sample Output

After flashing and booting the EVM, you will see below output on the UART console (Complete log is not shown)

SYSFW Version 9.0.5--v09.00.05 (Kool Koala)
SYSFW revision 0x9
DMSC ABI revision 3.1

[BOOTLOADER_PROFILE] Boot Media       : FLASH
[BOOTLOADER_PROFILE] Boot Media Clock : 200.000 MHz
[BOOTLOADER_PROFILE] Boot Image Size  : 158 KB
[BOOTLOADER_PROFILE] Cores present    :
mcu-r5f0-0
r5f0-0
[BOOTLOADER PROFILE] System_init                      :      39447us
[BOOTLOADER PROFILE] Drivers_open                     :        218us
[BOOTLOADER PROFILE] Board_driversOpen                :         88us
[BOOTLOADER PROFILE] Sciclient Get Version            :       9909us
[BOOTLOADER PROFILE] App_loadImages                   :       3218us
[BOOTLOADER PROFILE] App_loadSelfcoreImage            :       9137us
[BOOTLOADER_PROFILE] SBL Total Time Taken             :      62019us

Image loading done, switching to application ...
Starting MCU-r5f and 2nd stage bootloader
[BOOTLOADER_PROFILE] Boot Media       : FLASH
[BOOTLOADER_PROFILE] Boot Media Clock : 200.000 MHz
[BOOTLOADER_PROFILE] Boot Image Size  : 321 KB
[BOOTLOADER_PROFILE] Cores present    :
hsm-m4f0-0
r5f0-0
a530-0
c75ss0
[BOOTLOADER PROFILE] System_init                      :       2412us
[BOOTLOADER PROFILE] Drivers_open                     :        243us
[BOOTLOADER PROFILE] App_loadImages                   :       2361us
[BOOTLOADER PROFILE] App_loadSelfcoreImage            :       8742us
[BOOTLOADER PROFILE] App_loadA53Images                :       6463us
[BOOTLOADER PROFILE] App_loadDSPImages                :       7393us
[BOOTLOADER_PROFILE] SBL Total Time Taken             :      27616us

Image loading done, switching to application ...
Starting RTOS/Baremetal applications
[UDMA] Chaining application started ...
All tests have passed!!

Table of Contents