Introduction
- SBL booting Linux from eMMC (see SBL EMMC Linux Multistage) is a secondary bootloader application that boots Linux on A53 core and RTOS/NORTOS application on R5, C7x, M4 cores.
- The bootloader makes use of 7 appimages
- A Linux appimage containing the Linux binaries (ATF, OPTEE, A53 SPL).
- 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
- Boots R5F, MCU-R5, HSM-M4, C75 cores and Linux on A53 from eMMC.
- SBL booting Linux can be used when early booting of R5F, HSM-M4, C75 and MCU-R5 cores are required. When using uBoot, the application will start running on R5F, HSM-M4, C75 and MCU-R5 cores only after booting Linux
- The Linux appimage can be generated by using Linux Appimage Generator Tool
- The appimages will be flashed to the offset on eMMC specified by SysCfg, the SBL parses the appimages from these locations, loads and run the cores.
Bootflow for SBL booting linux from eMMC
- Note
- The binaries for R5F, M4F, C75 cores need not be in the linux root partition
(root/lib/firmware)
, when SBL is booting Linux.
- The bootflow for SBL booting Linux is as follows
Bootflow for SBL booting Linux
EMMC Partitioning
- Note
- The default SD card image for AM62Ax-evm can be used to boot Linux using SBL
-
The tiboot3.bin, tispl.bin will not be used for booting Linux when using SBL booting Linux.
-
The R5 binaries in the root partition (eg :
root/lib/firmware/am62a-mcu-r5f0_0-fw
) will not be used when SBL boots Linux and MCU-R5,C75 cores.
- eMMC uses two patitions to boot Linux
- A boot patition
- tiboot3.bin
- tispl.bin
- u-boot.img
- uboot.env
- A ext4 partition in the user data area containing
- Linux Kernel image
- Linux DTB
- Linux file system
See Also