We are using s132_nrf52_2.0.0_softdevice.hex with the nrf52832 .
We have been having problems with our devices asserting when in the field. Unfortunately we have not been able to reproduce this issue in-house, so I can't say under what circumstances this occured other than that the devices had been operating correctly for several hours before the error occurred. This seems to happen quite infrequently.
The softdevice assert callback indicates NRF_FAULT_ID_SD_ASSERT, with a PC value of 0x1a986 (108934).
We are using the Timeslot API, so I suspect that this may well be due to a timing violation.
Thanks in advance,
Matt