https://devzone.nordicsemi.com/f/nordic-q-a/24755/knowing-nvmc-operation-is-finished-inside-ble-event(nRF51822, but also concerned with nRF52832, SD130, SDK 12.1) I&#39;m trying to write/erase flash from a bluetooth event handler. As it&#39;s been outlined in other questions, while being in the event handler, other events aren&#39;t fired (like NRF_EVT_FLASH_OPERATION_SUCCESSen-USTelligent Community 13Wed, 30 Aug 2017 18:44:10 GMThttps://devzone.nordicsemi.com/thread/97497?ContentTypeID=1Wed, 30 Aug 2017 18:44:10 GMT137ad170-7792-4731-bb38-c0d22fbe4515:bf917ae3-673d-4fa5-9d83-91505e935a41Jonathan<p>Thanks! I will investigate that lead! I know ideally it should be out of the event handler, however that makes the complete code considerably more complex, splitting everything into a lot of callbacks. Down the road I&#39;ll probably resort to it but if in the the meantime I can avoid it, I will...</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/97498?ContentTypeID=1Wed, 30 Aug 2017 18:08:06 GMT137ad170-7792-4731-bb38-c0d22fbe4515:9d8a9d2f-6c0f-4925-81e2-78ecb0a631e5Hung Bui<p>Hi Jonathan,</p> <p>I don&#39;t think it&#39;s a good solution. The reason <code>NRF_NVMC-&gt;READY is set to 1 very quickly</code> is that the flash operation may not have started when you check that yet. The softdevice schedules the flash operation, it may delay the operation until the BLE event is finished for example. What you should do is to move your operation out of the event handler and wait for NRF_EVT_FLASH_OPERATION_SUCCESS in main context.</p><div style="clear:both;"></div>