TDA4VM: Is this reasonable that the boot-up timing of TDA4VM HS version almost twice of TDA4VM GP version?

Jingchun,

This question is now included here: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1190288/tda4vm-what-are-the-differences-of-the-tda4vm-gp-version-and-hs-version-from-hw-side-and-sw-side

I'm going and closing this ticket.  

John 

Upon conferring with Suman - re-opening this ticket for the time being. 

John 

Hi Jingchun,

Thanks for the boot-flow summary. 

The GP version doesn't need any decryption or authentication of your application images (lateapp1, lateapp2, ATF/OPTEE etc), only the SBL and TIFS will need to be signed with a degenerate key (essentially have an X509 certificate).

The HS version will definitely need authentication and optionally decryption depending on the image. A majority of additional time on HS in general is taken up during the SHA computation and this depends on the size of the file the hash is being computed on.

You haven't mentioned the sizes of any of these binaries or what images were signed or encrypted. The AutoSarBootManager and the autoSAR APPL are your implementations, and it is not clear whether you are signing your lateapp1/lateapp2 images.

Please provide the sizes of the GP vs HS images, and which images were signed and optionally encrypted? The 6s vs 12s difference is also just the overall difference, do you have a split of time difference between the different phases of your SecureBootSequence?

regards

Suman