https://devzone.nordicsemi.com/f/nordic-q-a/16303/nrf52-sd-sd_app_evt_wait-wont-sleep-after-ble-connectionTo the wizards at Nordic, I come to you with a rather perplexing issue, we are building a custom application on top of our nrf52 based design. The board seems to work great with all peripherals, and the SD behaving as expected. However we run intoen-USTelligent Community 13Fri, 09 Sep 2016 00:24:09 GMThttps://devzone.nordicsemi.com/thread/62324?ContentTypeID=1Fri, 09 Sep 2016 00:24:09 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b4f74c97-618d-46c4-85bb-1c63748fbebcshaba<p>Now that you put it that way, I think I understand what might be afoot. There is probably a security param update or the like that I am not responding to which is putting the system into an odd state. I expected those to show up when I call sd_ble_evt_get(). Is there a documented place which lists what reasons might cause SWI2 to need handling? Thanks for the quick reply RK! I will report back with any findings.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/62325?ContentTypeID=1Fri, 09 Sep 2016 00:18:41 GMT137ad170-7792-4731-bb38-c0d22fbe4515:46eeab16-40d2-4b13-9d7d-d78747e0a4a4RK<p>SWI2 is the softdevice interrupt which tells <em>YOU</em> you have softdevice events you need to handle, so where&#39;s your SWI2 handler? So no the SD will not be handling those events, you will be.</p><div style="clear:both;"></div>