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

2.2 Falcon Boot Flow

Falcon mode allows direct booting to the Linux kernel, bypassing the U-Boot stage for faster boot time.

  1. After Power on secure Rom runs on M3/M4 core
  2. Release reset of R5, Public ROM starts of MCU R5F
  3. Public Rom reads the tiboot3.bin from boot media and sends this to secure ROM for authentication. After authentication secure ROM loads R5 SPL to MCU R5F and TIFS to M3 and M4 core.
  4. R5 SPL reads tispl.bin from boot media, authenticates using TIFS service and then loads ATF, OPTEE, and Linux to the respective location.
  5. Release reset on A72 and load DM to itself.
  6. Linux loads the remote core fw on Main R5F.
  7. Linux loads the remote core fw on Main C7x
Note: Loading remote core firmware require DM (Device Manager) services, that is the reason for loading the firmware from Linux once the DM is up and running on the MCU R5F.
Falcon Boot Flow Figure 2-3 Falcon Boot Flow
Falcon Boot Flow Figure 2-4 Falcon Boot Flow

See E2E™ design support forum for more information.