SoftDevice induced reset?

[turboscrew]

What are the situations where a SoftDevice calls reset handler?

I have a somewhat heavy data collection (lots of event handling) and those things are logged via RTT backend (non-deferred).

After about 3 min run, SoftDevice (s132_nrf52_7.0.1_softdevice) calls reset handler.

The call happens at address 0x25296, which seems to be in the SoftDevice image.

The system runs on nRF52832.

[turboscrew]

A-ha.. Found it. there was a sleep-call left in the example code on top of which I've been building my code.

This issue can be closed (but it would be good to know if there are ways of figuring out, if a SoftDevice is mad about something).

[Sigurd]

turboscrew said:

A-ha.. Found it. there was a sleep-call left in the example code on top of which I've been building my code.

 Great!

turboscrew said:

but it would be good to know if there are ways of figuring out, if a SoftDevice is mad about something

You would then get an assert. app_error_fault_handler() will be called with id set to NRF_FAULT_ID_SD_ASSERT, or alternatively NRF_FAULT_ID_APP_MEMACC if an invalid memory access happened.