TDA4AL-Q1: How to implement raw sensor output YUV image within 4 seconds?

Hi, ti exports

Is it feasible to use aewb target processing function as follows?

Of course, the function should be refactored with removing openvx framework code

Thanks

Hi,

Well, possible, but it is not supported in the standard SDK. In SDK, this algorithm is available in the OpenVX node only. 

Before going into it, can you please refer to below FAQ? It talks about how you can optimize the usecase to get better latency numbers.

[FAQ] TDA4VM: How to optimize surround view use case to 2-3 Seconds from power on - Processors forum - Processors - TI E2E support forums

Regards,

Brijesh

Hi Brijesh  Jadav,

      we use SBL,  but startup time in SBL mode is 30s， please refer to another case

      e2e.ti.com/.../4845977

Dear Brijesh，

      I don't understand  why it is not supported in the standard SDK.  Can't we directly call the interface functions of AE and AWB algorithms

Hi Qin,

Sorry this ticket is for AEWB, for SBL startup time, it can expected. Because if you are using UDA partition and SBL, it takes time to tune the eMMC and then to read from UDA partition. 

Regarding AEWB, we support usecases using OpenVX framework, so AEWB is integrated in OpenVX in standard SDK. You can directly call AEWB algorithm API, but then you would have to integrate it in your application. 

Regards,

Brijesh 

Hi  Brijesh

        How long does it take  if we use emmc UDA ?

        How long does it take  if we use emmc  boot0 ?

Dear  Brijesh

     "Because if you are using UDA partition and SBL, it takes time to tune the eMMC and then to read from UDA partition"

    This  will take 30s and than start linux ?

Hi  Brijesh

       If we want to  raw sensor output YUV image within 4 seconds, are there any better suggestions? Thank you very much.

Hi Qin,

but what's your bootmedia? Are you booting from OSPI? Then yes, it can improved, but for eMMC boot0 partition, i really doubt we can do much.

Regards,

Brijesh

Dear Brijesh,

      We are booting from  eMMC boot0.

      How long does it take and than start linux  if  boot from  eMMC boot0 ?  

Hello Qin,

But is it only for SBL? What about the rest components? Can you please share details about your bootflow with the storage device used for each component? 

Regards,

Brijesh

Hi  Brijesh,

     SBL mode and  emmc boot0

ok, then SBL loads the different components from boot0 partition only? 

Hi Brijesh,

The EMMC partition is divided into BOOT partition and UDA partition.
In the BOOT partition, sbl boot0 boot files are burned and written: tiboot3. bin is written at address 0, tifs. bin is written at 0x400, and app is written at 0x1400.
In the UDA partition, commands are used to create logical partitions into boot partition and rootfs partition, with kernel and other images placed in the boot partition.

Hi  Brijesh,

     Please help me check.  Thank you very much

Hi Qin,

What's the size of the app binary? Also how much time it takes to initialize and load TIFS? Have you done some detailed measurement as to which component is taking more time to load? Is it TIFS, or App or Linux booting is taking more time? 

eMMC initialization should not take so much time, but lets first profile it.

Regards,

Brijesh