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

3.5 Flashing the Binaries to OSPI

There are multiple methods to flash the binaries to OSPI flash as mentioned in TDA4 Flashing Techniques. This application note uses the u-boot to copy the images onto the OSPI Flash.

  1. Copy four images to SD card boot partition:
    1. combined_opt.appimage
    2. tifs.bin
    3. sbl_ospi_img_hlos_mcu1_0_release.tiimage
    4. Nor_spi_pattern.bin
  2. Flash to OSPI using the below commands:
    sf probe
sf erase 0x0 0x4000000
fatload mmc 1 ${loadaddr} sbl_ospi_img_hlos_mcu1_0_release.tiimage;
sf update $loadaddr 0x0 $filesize;
fatload mmc 1 ${loadaddr} combined_opt.appimage;
sf update $loadaddr 0x100000 $filesize;
fatload mmc 1 ${loadaddr} tifs.bin;
sf update $loadaddr 0x80000 $filesize;
fatload mmc 1 ${loadaddr} nor_spi_patterns.bin;
sf update $loadaddr 0x3fe0000 $filesize;
  3. Switch to OSPI Boot mode. All the boot binaries are now in OSPI.