• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 226 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TDA4VH-Q1: How to optimize the initialization time of U-Boot

hongyao.jin
Expert 1220 points
Part Number: TDA4VH-Q1
Other Parts Discussed in Thread: TDA4VH

Tool/software:

Hardware: TDA4VH
SDK: 1001 linux + RTOS


By obtaining the GTC time, we found that uboot spent 2 seconds between board_init_f_alloc_reserve() and display_options(), we want to know if this is reasonable and how we should find the location that consumes the most time and optimize it.

We tried to troubleshoot by enabling the BOOTSTAGE option, but once uboot enabled this option, it couldn't run normally. Does TI support the BOOTSTAGE option?

  • 0
    TI__Guru**** 163630 points

    Hello,

    Couple of requests:

    • Please share the logs. 
    • Which boot media are you using?
    • What is the target U-Boot time?
    • Is this a custom board or TI EVM?

    - Keerthy

  • 0 in reply to Keerthy J
    Expert 1220 points

    hi

    Keerthy J said:
    Which boot media are you using?

    We use emmc boot mode

    Keerthy J said:
    What is the target U-Boot time?

    Currently, the duration of the U-Boot phase is approximately 3 seconds. We hope to reduce it to within 1 second.

    Keerthy J said:
    Is this a custom board or TI EVM?

    custom board

    Keerthy J said:
    Please share the logs. 

    We measured the time after the execution of SBL and ATF through GTC time, which were 116ms and 238ms respectively. We also estimated the end time of U-boot based on the GTC time of the first log of MCU20, which was 5.145S(MCU20)-2S(U-boot delay).

    MCU20 is loaded via uboot, while the other cores are loaded via linux

  • 0 in reply to Keerthy J
    Expert 1220 points

    And currently, we have investigated that the dm_init_and_scan function has taken approximately 1 second

  • 0 in reply to hongyao.jin
    TI__Guru**** 163630 points

    Hi,

    hongyao.jin said:

    And currently, we have investigated that the dm_init_and_scan function has taken approximately 1 second

    Apologies for the delay in responding. This is the core function which probes devices in a tree like sequence. It is expected to take 1 Second as it is the function that probes all the relevant devices in the DT. The U-Boot should not be taking 3 seconds. There is a timer of 2 seconds before loading kernel that is autoboot delay we can reduce that to 0.

    - Keerthy