• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 279 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.

BootUp time between HSFS & NonHSFS

Karen Agüero Meza
Prodigy 150 points

Hi,

We build our application to generate a firmware for HSFS and another one for non-HSFS.

During the Start-Up in both devices, we have noticed that the HSFS needs   ~3.283700s 

compared to NonHSFS needs only  ~0.354450s.

The analysis shows that the bootloader needs aprox. 2.92840s in the functon Bootloader_parseMultiCoreAppImage(), which in case of HSFS calls the following code for the authentication:

// FOR HSFS

if(Bootloader_socIsAuthRequired() == TRUE)

  {

        /* Device is HS, verify image. */

         status = Bootloader_verifyMulticoreImage(handle);

   }

Do you have some idea,  why the bootloader take so long in this part? and how we can optimize this?

Thanks&Regards

Karen Agüero Meza

  • 0
    TI__Mastermind 26145 points

    Hi Karen,

    As per our discussion the application size is 1876KB in case of RAM model on a HSFS device with boot time - 559ms. The ROM model image is 1285KB with boot time of 4.151secs.

    Let me return with some data post experimentation on my end.

    Thanks and Regards,
    Aakash

  • 0 in reply to Aakash Kedia
    Prodigy 10 points

    Hallo Aakash,

    we found out, that the function Sciclient_service() in the module Sciclient.c has a very long duration. Perhaps it´s a hint for you.

    Best regards 

    Hubert

  • +1 in reply to Hubert Raab
    TI__Mastermind 26145 points

    Hi /Karen Agüero Meza

    We have a different observation on TI-EVM with a different example.

     

    RAM Model

    ROM Model

     

    GP

    HS-FS

    GP

    HS-FS

    Image Size

    924KB

    924KB

    24KB

    24KB

    SBL Boot Time

    83ms

    1441ms

    80ms

    124ms

    This is an expected result if Image Integrity is enabled by the System Firmware.

    There are options to disable the image integrity checks in the application build if you are interested. You will definitely save some of your boot time but you will loose out on the minimum security which you have at the moment.

    Let me know if you are interested.

    Best Regards,
    Aakash

  • 0 in reply to Aakash Kedia
    Prodigy 150 points

    Hi Aakash,

    It looks good 124ms.

    Let me ask the Team about the requirements and inform to you.

    Thanks & Regards

    Karen

  • 0 in reply to Karen Agüero Meza
    TI__Mastermind 26145 points

    Hi Karen,

    The time difference in RAM Model and ROM Model is mostly because of difference in size of the application image. In the HS-FS ROM model image the size is 24KB and the size of HS-FS RAM model image the size is 924KB. So, if the image integrity is enabled, the boot time depends on the size of the application.

    If you disable the same, the observation would be that the time difference as seen in GP device i.e. very negligible.

    Please let me know if you have any updates for me.

    Best Regards,
    Aakash

  • 0 in reply to Aakash Kedia
    Prodigy 150 points

    Hi Aakash, 

    we have decided in the first released to disable the image integrity. Let know or send me please a patch how i can do that .

    Thanks för your support,

    Best Regards,

    Karen