Is there any way to reduce the startup time?
It is too long for the bulb device, so we need to solve this issue.
Hi,
Please try to select the RNG — Random number generator as the entropy source instead of using the CRYPTOCELL — ARM TrustZone CryptoCell 310 (default) by adding the following to your board DT file (or in an overlay):
chosen {
zephyr,entropy = &rng;
};
This accounts for about 400 ms of the startup time according to the thread here: High Current 400ms+ Startup Delay BLE Beacon Using RC Oscillator
What signature type have you selected for MCUBoot, RSA or ECDSA_P256?
Best regards,
Vidar
Thank you for your help.
RNG is set by default in the nrf52840dk_nrf52840.overlay.
And the signature type is ECDSA_P256, it's also set by default on the nrfConnect SDK of 2.1.1 version.
We expect the startup time to be reduced to 500ms,
this is very important for our bulb product. Please help solve it as soon as possible. Thanks a lot.
# MCUBoot settings # # CONFIG_SINGLE_APPLICATION_SLOT is not set # CONFIG_BOOT_SIGNATURE_TYPE_NONE is not set # CONFIG_BOOT_SIGNATURE_TYPE_RSA is not set CONFIG_BOOT_SIGNATURE_TYPE_ECDSA_P256=y
Hi,
What SDK sample is your project based on? Is it Matter, Homekit, or something else? And how do you measure the startup time?
Our project is based on the light_bulb.
It's a matter over thread project.
We output GPIO high level in Main application, and then use oscilloscope to check the time difference between 3.3V power supply and GPIO.
Thanks for confirming. I measure 1.1 second here with the original sample project between systeminit() in MCUBoot and app main(). I am checking internally if there is a way to optimize this.

Edit: for me to better understand the problem, could you say something about how this delay affects your application? For instance, if your app requires frequent reboots?