Dear Sirs
We are using android_p9.0.0_1.0.2-auto-beta release on IMX8QXP MEK board.
These days we are focusing on the M4 Core booting time(from POW ON to m4 demp app run).
As we tested it always need 170~250ms.
Then we enabled the scfw debug log, it shows the SCU ROM boot time need 150ms!
-------------------------------
Hello from SCU (Build 3014, Commit f0226b37, Mar 2Hello from SCU (Build 3014, Commit f0226b37, Mar 27 2019 14:44:44)
SCFW: DDR frequency = 1200000000
ROM boot time = 154894 usec <<< Here, does it really mean the SCU PROM loading time ?
SCFW boot time = 20852 usec
Banner = 6 usec
Init = 5447 usec
Config = 2969 usec
DDR = 5797 usec
SConfig = 196 usec
Prep = 4310 usec
*** Debug Monitor ***
--------------------------------
If it's true, is it possible to reduce the ROM boot time in obviously?
In our system design, we hope the M4 can hold the CAN bus msg in < 50ms after power on.
Thanks
Hi tiebing
>is it possible to reduce the ROM boot time
I am afraid not, since rom sources can not be changed.
In general one can check boot mode settings which may affect speed,
like SCU_ICACHE_DISABLE described inTable 5-3. Boot eFuse Descriptions
i.MX8QXP Reference Manual. Avoid logo and ddr initialization and run code from
internal memories. Also additional boot time optimizations may be provided
based on customer specific needs with NXP Professional Services | NXP
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Dear Igorpadykov
Thanks for kindly reply at all.
About the Boot eFuse:
Is there any visible result about ROM boot speed improvement after fused some boot eFuse bits?
Can NXP help to give us the best eFuse set for boot speed improve? As you know eFuse is one time writable area, customer has no much opportunity to try find the best set....
About the Avoid logo and ddr initialization and run code from internal memories
This is talking about the SCU FW and M4 core execution, is it right?
According to the standard Boot Flow, during scu rom booting seq, it needs the SECO FW to authentication image containers, it would take some time... is it possible to ignore the image authentication for faster boot, like the early boot flow in SCFW?
Thanks very much~
Hi tiebing
one can look at boot optimizations implemented in Android AUTO :
>Can NXP help to give us the best eFuse set for boot speed improve?
I am afraid there will be no significant improvement with fuse boot option.
>it needs the SECO FW to authentication image containers, it would take some time...
> is it possible to ignore the image authentication for faster boot, like the early boot flow in SCFW?
not, sorry.
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------