We are using v2.1.0 of the SDK with modem firmware v1.3.1.
We are using signed builds which are built with TFM and MCUBoot.
In our firmware we read out the reset cause directly from the NRF_POWER->RESETREAS register.
We test each of the 7 bits which indicate each of the possible reset causes as indicated by the production specification / datasheet.
(https://infocenter.nordicsemi.com/pdf/nRF9160_PS_v2.1.pdf pp.71-72).
At the start of our applicaion we read out the data from that register, save it and then clear the register. We then transmit the saved data with other
What we have seen is that occasionally, none of the seven defined reset causes were detected.
That is all seven of the associated bits NRF_POWER->RESETREAS register bits are 0 when our application starts.
Are there any cases where it is expected not to be able to detect any of the seven reset causes?
Ares there any cases where the reset cause might be cleared in one of the bootloader stages?
