https://devzone.nordicsemi.com/f/nordic-q-a/87824/mpsl-assert-112-2165-in-nrf-connect-sdk-when-setting-breakpoints-in-ble-stackHello, I&#39;m working on a BLE application using zephyr and nRF Connect SDK 1.8.0 on the nrf52840. I&#39;m debugging the BLE stack using ozone but whenever I set breakpoints the program runs to the breakpoint properly, but stepping causes E: MPSL ASSERT: 112en-USTelligent Community 13Thu, 12 May 2022 08:48:20 GMThttps://devzone.nordicsemi.com/thread/367544?ContentTypeID=1Thu, 12 May 2022 08:48:20 GMT137ad170-7792-4731-bb38-c0d22fbe4515:61046e28-5ab5-4c2a-afac-3fe716c39217J&#248;rgen Holmefjord<p>Hi,</p> <p>The BLE stack have strict timing requirements in order to comply with the BLE specifications. By hitting a breakpoint with your debugger, the CPU will be halted, preventing the CPU from handling scheduled events/tasks in the BLE stack. This will lead to the assert you are seeing when trying to continue code execution.</p> <p>You can run the code until you hit the breakpoint, step as far as you are allowed before application asserts, then reset the application and run until a new breakpoint. In nRF5 SDK we had support for&nbsp;Segger Monitor Mode Debugging, but unfortunately, it does not seem like this is supported in nRF Connect SDK as of now. See these two threads for more details and suggestions:</p> <ul> <li><a href="https://devzone.nordicsemi.com/f/nordic-q-a/84514/debugging-with-monitor-mode-on-ncs">https://devzone.nordicsemi.com/f/nordic-q-a/84514/debugging-with-monitor-mode-on-ncs</a></li> <li><a href="https://devzone.nordicsemi.com/f/nordic-q-a/70769/problem-using-monitor-mode-debugging-with-the-nrf-connect-sdk">https://devzone.nordicsemi.com/f/nordic-q-a/70769/problem-using-monitor-mode-debugging-with-the-nrf-connect-sdk</a></li> </ul> <p>Best regards,<br />Jørgen</p><div style="clear:both;"></div>