• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 359 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.

TDA4VM: How to optimize the BOOT process?

Ni Hua
Prodigy 235 points
Part Number: TDA4VM

Hi Ti,

    The current secure boot sequence I'm using is:

         SBL->BOOT_APP->lateapp1->lateapp2->ATF/OPTEE->tikernel->tidtb

         Actual startup time is greater than 20s. Is there a solution to speed up the startup time, making it significantly less than 20s? If so, please provide instructions on how to implement the solution.

        The SDK I am currently using is: ti-processor-sdk-rtos-j721e-evm-08_06_00_12

        Current Device type: HS

thanks.

  • 0
    TI__Mastermind 42135 points

    Hi,

    Ni Hua said:
    Actual startup time is greater than 20s.

    When you say the startup time are you referring to the first CAN response or the time till complete Linux boot?

    Regards,
    Parth

  • 0 in reply to Parth Nagpal
    Prodigy 235 points

    Hi Parth,

        The startup time I mentioned refers to the time from power-on to the moment before Linux kernel starts running.

    Urgent attention is needed for this issue. Please try to provide a solution as soon as possible.

    thanks.

  • 0 in reply to Ni Hua
    TI__Mastermind 42135 points

    Hi, 

    Can you please share what are your timing requirements and what is the boot mode that you are using?

    Regards,
    Parth

  • 0 in reply to Parth Nagpal
    Prodigy 235 points

    My timing requirements are:

        The time from SBL (Secondary Bootloader) initiation to Linux boot must be less than 2 seconds. Specifically, for a Linux kernel image with a size of 16MB, the signature verification operation must be completed within 1 second. The combined size of other images should be less than or equal to 16MB.

    My BOOT MODE is:

         OSPI mode, with the sequence being SBL -> BOOT_APP -> lateapp1 -> lateapp2 -> ATF/OPTEE -> tikernel -> tidtb.

    The resolution of this issue is quite urgent. Please assist in resolving it as soon as possible today.

    thanks.

  • 0 in reply to Ni Hua
    TI__Mastermind 42135 points

    Hi,

    Apologies for delay in response.

    Is this issue still open.

    Ni Hua said:
     OSPI mode, with the sequence being SBL -> BOOT_APP -> lateapp1 -> lateapp2 -> ATF/OPTEE -> tikernel -> tidtb.

    Try using the combined appImage for faster Linux start. In case of booting with bootApp Linux will be loaded in the end after other cores have been loaded, 

    In case of combined appimage, Linux can be loaded before any other core.

    Regards,
    Parth