This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA2EXEVM: early boot late attach: performance report

Part Number: TDA2EXEVM

Hello:

  To  meet the tight time constraints of Rear View Camera, we want to take early boot late attach strategy.(http://processors.wiki.ti.com/index.php/Early_Boot_and_Late_Attach_in_Linux)  

Did TI have the performance report how long it(M4) will take from the power on to one rear camera show up based on TDA2xx SOC?

Thanks.

 

  • Hi,

    The time taken to power-on one one rear camera and show-up on TDA2xx SoC depends on the use-case and the sensor being used.
    If the display is on M4, single camera capture and display can be achieved in <500ms from power-up. If the display is owned by Linux, the long-poll is the kernel initialization, in which case the captured video is displayed only after kernel init which is ~2s (takes ~1s for kernel initialization).

    Regards
    Shravan
  • Hi Shravan:
    Thanks, clear if using M4 for video display out. and can you introduce more about if we using linux for display.
    as you said it depended on the use-case and sensor being used, how long it take to power on from ROM, loading uboot, start to run linux kernel ?
  • Hi,

    The boot-time also depends on the boot-media (lowest for QSPI, highest for SD card), and the size of the firmware. Below are the numbers while booting from QSPI-4 (throughput of 25Mbps), using a single stage boot-loader (MLO) of size 100KB and a IPU firmware of size 800KB.

    PMIC -- 45ms

    ROM code + Load MLO -- 25ms

    Load and boot IPU-firmware -- 60ms 

    Once the firmware is booted, MLO jumps to kernel (~150ms from power-up).

    Regards

    Shravan