MPSL ASSERT when debugging with an active IEEE 802.15.4 radiohttps://devzone.nordicsemi.com/f/nordic-q-a/125854/mpsl-assert-when-debugging-with-an-active-ieee-802-15-4-radioI&#39;ve seen this discussed a few times before, but haven&#39;t seen a great answer on this. It seems to be commonly known that attaching a debugger while using the IEEE 802.15.4 radio causes an MPSL ASSERT due to strict timings. I may not have enough knowledgeen-USTelligent Community 13Thu, 27 Nov 2025 12:07:47 GMTRE: MPSL ASSERT when debugging with an active IEEE 802.15.4 radiohttps://devzone.nordicsemi.com/thread/555606?ContentTypeID=1Thu, 27 Nov 2025 12:07:47 GMT137ad170-7792-4731-bb38-c0d22fbe4515:520f028d-8f78-42f6-b84b-5f73f771d61fVidar Berg<p>Hello,</p> <p>Unfortunately, I don&#39;t have a better answer. This is a common limitation when working with protocol stacks that have real time requirements. Segger provides&nbsp;a solution for this called &quot;monitor mode&quot; debugging which basically let you single step and hit breakpoints without blocking the timing critical interrupts, but they have not ported this to the Cortex M33 yet.</p> <p>It should not be a problem to place breakpoints, the limitation is that you may get an assert if you try to resume execution after having reached the breakpoint instead of restarting the FW. &nbsp;</p> <p>Best regards,</p> <p>Vidar</p><div style="clear:both;"></div>