SPRADE5 February   2025 TDA4VM , TDA4VM-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2Optimization Methology
    1. 2.1 Bootloader Switch to SBL From OSPI Boot Media
    2. 2.2 Linux Device Tree Optimizations
    3. 2.3 File System Switch to Tiny rootfs
    4. 2.4 Vision_apps Framework Optimizations
    5. 2.5 Imaging Framework Optimizations
    6. 2.6 Vision_apps SRV Application Redesign
  6. 3Detailed Design Procedure
    1. 3.1 Linux Integration (PSDKLA)
    2. 3.2 Imaging Integration(PSDKRA)
    3. 3.3 Vision_apps Integration (PSDKRA)
    4. 3.4 PDK Implementation (PSDKRA)
      1. 3.4.1 Build R5 SBL for OSPI Boot Mode
      2. 3.4.2 Build combined_appImage
      3. 3.4.3 Copy TIFS and phy Tuning Parameters
    5. 3.5 Flashing the Binaries to OSPI
    6. 3.6 Steps to Install vision_apps With tiny-rootfs on SD Card
    7. 3.7 Copy Test Data to SD card (one time only)
    8. 3.8 Init Script
    9. 3.9 Moving File System From SD to eMMC
  7. 4Logs
  8. 5Summary
  9. 6References

2.1 Bootloader Switch to SBL From OSPI Boot Media

In the case of SPL-based boot flow, the MCU2_0 firmware loading happens only at the U-Boot stage. This implies that it can take around 1.8 sec to load the firmware.

On the other hand, with the SBL-based boot flow, the firmware loading is supported from SBL. This implies that firmware loading starts as early as 100 ms.

Choosing the OSPI as the boot media further speeds up the booting against MMCSD boot media.

With the above path and chosen optimizations, it saved about 1.5 Seconds.