when debugging BTmesh (with MPSL) breakpoints trigger an assert. This is listed in the known issues of the nrfConnectVScode page:
Does this apply to VScode only and using SES would be a work-around? Or is there no work-around possible?
Yes, this is recommended as of now. Does the issue persist when you use the Monitor Mode Debugging? (for nrf52 and nrf53)
You could try debugging with Ozone (or even SES). But the limitation is in MPSL and in any case, using the Monitor Mode Debugging can help avoid problems.
I am using NCS 1.8.0 and SES, but the issue persists on single-core nRF52832
My quick test on nRF5340 did not appear to show this problem, albeit I only set a breakpoint/resumed on nRF5340 Application core.
Priyanka I have used Monitor Mode Debugging successfully on the previous Nordic SDK ( non-Zephyr )
Is using Monitor Mode Debugging a recommended path for NCS/Zephyr, notably on nRF52x ICs ?
Is it even necessary for multi-core nRF5340 application core ?