MPSL Assert 112,2165 in nRF Connect SDK when Setting Breakpoints in BLE Stack

[jake11212]

Hello,

I'm working on a BLE application using zephyr and nRF Connect SDK 1.8.0 on the nrf52840.  I'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: 112, 2165.  I think this is a common error with debugging breakpoints in the BLE stack but I was wondering if there were any solutions, or if it was just impossible to debug using breakpoints in the BLE stack.

Thanks,

Jake

[Jørgen Holmefjord]

Hi,

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.

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 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:

• https://devzone.nordicsemi.com/f/nordic-q-a/84514/debugging-with-monitor-mode-on-ncs
• https://devzone.nordicsemi.com/f/nordic-q-a/70769/problem-using-monitor-mode-debugging-with-the-nrf-connect-sdk

Best regards,
Jørgen