SDAA123 January   2026 DRA821U-Q1 , DRA829J-Q1 , DRA829V-Q1 , TDA4AH-Q1 , TDA4AL-Q1 , TDA4AP-Q1 , TDA4APE-Q1 , TDA4VE-Q1 , TDA4VH-Q1 , TDA4VL-Q1 , TDA4VM , TDA4VM-Q1 , TDA4VP-Q1 , TDA4VPE-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
    1. 1.1 ROM Loading Bootloader
  5. 2Secondary Program Loader
    1. 2.1 Normal Boot Flow
    2. 2.2 Falcon Boot Flow
  6. 3Secondary Boot Loader
    1. 3.1 Development Boot Flow
    2. 3.2 Optimized Boot Flow
    3. 3.3 Boot APP (Tertiary Bootloader)
  7. 4Summary
  8. 5References

3.2 Optimized Boot Flow

  1. After Power on Secure ROM runs on M3 and M4 core
  2. Release reset of R5, Public ROM starts on MCU R5F
  3. Public ROM reads the tiboot3.bin from boot media and sends this to secure ROM for authentication and after authentication, public ROM loads R5 SBL to MCU R5F.
  4. R5 SBL reads tifs.bin from boot media, authenticates and then loads on M3 and M4 core using secure ROM service.
  5. SBL authenticates combined app image using TIFS service and load remote core firmware on Main R5F.
  6. SBL loads remote core firmware on C7x.
  7. SBL loads ATF, OPTEE and Linux to the respective location. This flow eliminates the U-Boot stage by loading Linux directly from SBL, reducing boot time.
  8. SBL releases the reset of A72 and load DM.
Optimized Boot Flow Figure 3-3 Optimized Boot Flow
Image Format (Optimized Boot Flow) Figure 3-4 Image Format (Optimized Boot Flow)