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.

TDA4VEN-Q1: sbl quick start display avm

Part Number: TDA4VEN-Q1
Other Parts Discussed in Thread: TDA4VM, TDA4VL

Tool/software:

Hi, experts

I have successfully booted and avm has been displayed properly by referring to this link J722S MCU+ SDK: SBL SD HLOS,but found that it takes a very long time to load the app as a firmware.

I have thought of using SBL OSPHLOS to boot this way, but the app is already 32+MB and my nor flash only uses 32M!

Is there any other way to speed up the boot please.

There is an eMMC on the board and the boot partition is only 32M.

 

board: custom board

sdk: 10_00_00_08

Best Regards,

Bing

  • Hi Bing,

    the app is already 32+MB and my nor flash only uses 32M

    Could you please let me know the app you're referred and how long it will take for it to load?

    Regards,

    Karthik

  • Hi Karthik,

    [2025/2/6 13:48:14.694] DMSC Firmware Version 10.0.8--v10.00.08 (Fiery Fox)
    [2025/2/6 13:48:14.697] DMSC Firmware revision 0xa
    [2025/2/6 13:48:14.698] DMSC ABI revision 4.0
    [2025/2/6 13:48:14.698] 
    [2025/2/6 13:48:18.926] [BOOTLOADER_PROFILE] Boot Media       : SD Card 
    [2025/2/6 13:48:18.930] [BOOTLOADER_PROFILE] Boot Image Size  : 32087 KB 
    [2025/2/6 13:48:18.936] [BOOTLOADER_PROFILE] Cores present    : 
    [2025/2/6 13:48:18.937] mcu-r5f0-0
    [2025/2/6 13:48:18.937] wkup-r5f0-0
    [2025/2/6 13:48:18.939] main-r5f0-0
    [2025/2/6 13:48:18.939] c75ss0
    [2025/2/6 13:48:18.939] c75ss1
    [2025/2/6 13:48:18.939] a530-0
    [2025/2/6 13:48:18.945] [BOOTLOADER PROFILE] System_init                      :      24838us 
    [2025/2/6 13:48:18.952] [BOOTLOADER PROFILE] Drivers_open                     :      16377us 
    [2025/2/6 13:48:18.958] [BOOTLOADER PROFILE] Board_driversOpen                :          0us 
    [2025/2/6 13:48:18.969] [BOOTLOADER PROFILE] Sciclient Get Version            :       9769us 
    [2025/2/6 13:48:18.971] [BOOTLOADER_PROFILE] SBL Total Time Taken             :      50986us 
    [2025/2/6 13:48:18.972] 
    [2025/2/6 13:48:18.976] Image loading done, switching to application ...
    [2025/2/6 13:48:18.980] Starting linux and RTOS/Baremetal applications
    [2025/2/6 13:48:19.003] Sciserver Testapp Built On: Oct 23 2024 14:48:18
    [2025/2/6 13:48:19.008] Sciserver Version: v2024.07.0.0REL.MCUSDK.10.00.00.13+
    [2025/2/6 13:48:19.011] RM_PM_HAL Version: v10.00.07
    [2025/2/6 13:48:19.014] Starting Sciserver..... PASSED
    [2025/2/6 13:48:19.021] [IPC RPMSG ECHO] Version: REL.MCUSDK.09.00.00.16 (Oct 21 2024 10:17:13):  
    [2025/2/6 13:48:23.355] [IPC RPMSG ECHO] Remote Core waiting for messages at end point 13 ... !!!
    [2025/2/6 13:48:23.361] [IPC RPMSG ECHO] Remote Core waiting for messages at end point 14 ... !!!

    As you can see from the startup log above loading the app took 4.2s, I think it would be best if it didn't take more than 1s to load the app.

    Best Regards,

    Bing

  • Hi Bing,

    SBL is just the boot loader, it just loads the firmwares after some initialization. Firmware needs to be optimized for the early display. We have an FAQ which explains different techniques to optimize the bootflow for TDA4VM. I think many of these techniques can still be applicable here also. So can you please refer to below link?

    https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1110814/faq-tda4vm-how-to-optimize-surround-view-use-case-to-2-3-seconds-from-power-on

      

    Regards,

    Brijesh

  • Hi Brijesh,

    This link has been referenced before and implemented on tda4vl and was able to save some time. The current method is still too slow for us to start.

    Previously the boot method was sbl->app->ubootspl->uboot->kernel, so the app firmware was small enough to burn the app into the nor flash. Now it is sbl->app->kernel, so the app firmware is bigger and can't be burned into the nor flash.

    Is there any way to split the app into two parts, one in nor flash and one in eMMC. Or put the app firmware all in eMMC, but speed up the app loading.

    Best Regards,

    Bing

  • Hi Bing,

    Sorry, did not get your boot flow. In both the cases, app (i guess this means firmwares), are loaded by SBL, so is the change in "app"'s  size? 

    and when you want to store firmwares in eMMC, you want again SBL to load these firmwares? 

    SBL does support eMMC and so it can read it from the raw/uda partition, but it may not be as fast as nor flash.  

    Regards,

    Brijesh  

  • Hi Brijesh,

    SBL does support eMMC and so it can read it from the raw/uda partition

    I refer to that link J722S MCU+ SDK: SBL EMMC HLOS as booting from boot0, is there an example of a reference from the uda partition?

    Best Regards,

    Bing

  • Hi Bing,

    uda partition is not supported in the MCU+ SDK. Confirmed with the team.

    Regards,

    Brijesh

  • Hi Brijesh,

    Can you please provide the patch for uda partition boot? Because my boot0 partition is also only 32M not enough.

    Best Regards,

    Bing

  • Hi Bing,

    unfortunately, no, we dont currently have patch to enable this feature. I can raise requirement, but not sure when this can be available. 

    Regards,

    Brijesh

  • Hi Brijesh,

    Thank you. I'll be waiting for your good news.

    Best Regards,

    Bing

  • Hi Bing,

    I have raised this requirement, but not sure when it would be implemented. 

    https://jira.itg.ti.com/browse/JACINTOREQ-8521

    Regards,

    Brijesh

  • Hi Brijesh,

    jira.itg.ti.com/.../quote]

    Thank you. I can't access the link you gave

    Best Regards,

    Bing

  • Hi Bing,

    This is internal jira link, that i have put here for the reference. 

    Regards,

    Brijesh