Secure bootloader and Logs

RE: Secure bootloader and Logs

Sigurd — Mon, 30 Aug 2021 08:28:29 GMT

Do you have the same reset reason at each startup?

Try printing the reset reason when you print the first timestamp.

uint32_t reset_reason = NRF_POWER->RESETREAS;

RE: Secure bootloader and Logs

LSz — Tue, 24 Aug 2021 12:05:46 GMT

Hi,
I have a timestamp in every log, the timestamp goes back to 00:00:00 only when a reset has occurred. When I checked the logs after the reset, the timestamp turned to 00:00:00 and a startup process has started. Then another log with the timestamp 00:00:00 is printed and the startup process has started again.

Moreover, my device has a screen you can clearly see that during the reset using NVIC_SystemReset() a second reset is occurring before the first one is finished.
This doesn't happen every time I use the NVIC_SystemReset(), and it never happens to me when I disable the logs on my application, or when I am running the application without the bootloader.

I have tried to find a connection between the Logs and the bootloader that could cause this reset.

RE: Secure bootloader and Logs

Sigurd — Tue, 24 Aug 2021 11:19:01 GMT

Hi,

How did you determine if a "double reset" is occurring?

As you might know, default behavior if an error code is passed into APP_ERROR_CHECK() is to do a reset.