Hello,
I am running application with softdevice s130 and nRF51_SDK v 12.2.0 on a custom board. The interrupts that are used by the SD are not used anywhere by the application. I do not use timeslot api. I can do a transfer over BLE and most of the times everything works fine. I do not have easy access to the system but only to the logs from which I extracted the assert information. The device is running fine with BLE communication and suddenly it gave SD assert with the parameters mentioned in the title (id=1 pc=0x104ae, info=0x0).
I have tried to find similar posts like this in the forum but this does not seem to have resemblance to my case (in my case, interrupts are handled through the softdevice and I also crosschecked that the ones used by the softdevice don't seem to be used anywhere else).
Does anyone have any pointers on how to dig deeper? I kind of have hit a wall here.
