https://devzone.nordicsemi.com/f/nordic-q-a/57467/softdevice-assertion-failure-while-using-radio-timeslot-pc-0x00000tima60Hi, [Softdevice 6.1.1] I am developing an application which uses the radio timeslot api in conjunction with BLE. Even without starting BLE advertising, or any other BLE timeslot activity, I still get asserts. I am getting soft device asserts approximatelyen-USTelligent Community 13Thu, 06 Feb 2020 21:25:16 GMThttps://devzone.nordicsemi.com/thread/233154?ContentTypeID=1Thu, 06 Feb 2020 21:25:16 GMT137ad170-7792-4731-bb38-c0d22fbe4515:57004ddb-3285-46d7-9bcf-cb79e6f07319robwasab<p>I think the issue is that I was using NRF_RNG (random number generator) in the timeslot. According to the specification, its access is restricted and can only be used through the softdevice.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/233045?ContentTypeID=1Thu, 06 Feb 2020 12:29:35 GMT137ad170-7792-4731-bb38-c0d22fbe4515:9f82fd33-9ea5-4e3f-883f-e38a31b76697Susheel Nuguru<p>It is really difficult to narrow down what caused the hardfault you mentioned. But 0xA60 is softdevice hardfault assert handler. I am guessing since you saw this PC value, you are running your code in debugger and you see that the execution halts here? If this is the case, you can continue the execution and most likely this will call your application assert handler and that will provide more information as to where the hardfault was created. If this is application generated hardfault, it would be easy to analyze it thereafter.</p><div style="clear:both;"></div>