https://devzone.nordicsemi.com/f/nordic-q-a/11821/soft-device-threading---when-and-what-are-calls-safeI would like to learn more about when it is safe to invoke soft device methods and when it is not. For example, are the following &#39;allowed&#39; to make soft device calls to update a characteristic? If not, what is the suggested workaround? For example, canen-USTelligent Community 13Mon, 15 Feb 2016 09:07:08 GMThttps://devzone.nordicsemi.com/thread/44705?ContentTypeID=1Mon, 15 Feb 2016 09:07:08 GMT137ad170-7792-4731-bb38-c0d22fbe4515:709f3c5d-c87b-4d13-b805-ef96d1e42736Susheel Nuguru<p>All application related interrupts (interrupts caused by peripherals not reserved by softdevice, like, RADIO, RNG, TIMER0 etc) will wake your main when you call sd_app_evt_wait in a loop.</p> <p>Read <a href="https://devzone.nordicsemi.com/question/16515/sd_app_evt_wait/">here</a></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/44706?ContentTypeID=1Sun, 14 Feb 2016 04:37:43 GMT137ad170-7792-4731-bb38-c0d22fbe4515:ce6e98bf-b544-4ea3-ac21-daa44c39c0bbGlennEngel<p>Is use of the scheduler required or can one just check a &#39;pend&#39; variable in the main loop? It&#39;s not clear to me what events trigger the main loop to wake up and run.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/44704?ContentTypeID=1Thu, 11 Feb 2016 08:57:57 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3680e58c-6b91-4d39-a81d-9adb883f0832Susheel Nuguru<p>1 &amp; 2) Yes, as long as the interrupt handler priority is less than SVC IRQ priority.</p> <p>3 &amp; 4) Technically Yes, but some has seen problems in few cases, that is why using a scheduler and moving the context to main is recommended here.</p><div style="clear:both;"></div>