https://devzone.nordicsemi.com/f/nordic-q-a/21690/unable-to-find-source-of-issuehi i am unable to find cause of issue i am working on BLE and PWM driver when i get data in nus_data_handler i am calling pwm init function. and then it is going to ble_advertising_on_ble_evt(p_ble_evt); in ble dispatch event. after that stucks aten-USTelligent Community 13Sat, 29 Apr 2017 10:47:28 GMThttps://devzone.nordicsemi.com/thread/85191?ContentTypeID=1Sat, 29 Apr 2017 10:47:28 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a3484868-6419-4765-83a1-0e92662d8e1bTurbo J<p>That is a <em>small</em> PC value - so the error origin is in the soft device, unfortunately. The error code in <code>p_error_info</code> is obviously bogus, as this points to <code>NULL</code> (0x00000000) which is in flash (vector table in the softdevice).</p> <p>You can only check the basics here, like whether your interrupt priorities are correct. Remember that the default 0 level is forbidden for application interrupts when softdevice is active.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/85190?ContentTypeID=1Fri, 28 Apr 2017 11:46:38 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b3511dc2-7741-439d-a325-0485140275abSigurd<p>Hi,</p> <p>Are you still having this problem? If you are trying to init the PWM, and it&#39;s already initialized you will get an error. 1401(0x579) is not a valid error code, the valid ones are listed in nrf_error.h.</p><div style="clear:both;"></div>