MPSL disabling USB interrupts

[AGeegee]

I note that calling:

mpsl_lib_init causes the POWER . INTENSET to be cleared (including the USB interrupts and POF WARN).

My device uses the USB stack, as such, calling MPSL lib init/unint causes the USB stack to miss these interrupts. As well as the POF Warn interrupt.

What is the best sequence to initialise the USB/POWER POF warn if MPSL is used in Zephyr 3.0.0, ncs-3.0.0?

I also have other radio protocols, so I need to runtime disable/enable MPSL via the lib_init/uninit functions. However doing so causes USB and other Power related interrupts to miss. Is there any documentation around these side-effects?

Regards,

[Einar Thorsrud]

Hi,

I have not seen any other such issues reported, and looking at the code I do not find any instances where MPSL writes to the POWER registers. Can you share more details about how you see and reproduce this?

[AGeegee]

SET the POWER.INTENSET interrupts to 1. Then call mpsl_uninit followed by mpsl_init. Observe the POWER.INTENSET registers and note that the interrupt enables are cleared. 

[Einar Thorsrud]

Hi,

I reproduce the same on my end. We are looking into this and I will get back to you.

[Einar Thorsrud]

Hi,

I confirm that the behaviour you see is part of the MPSL binary, and that all POWER interrupts are disabled. We are looking into if this can be done differently, but for the short term there is no solution other than re-enabling immediately after disabling MPSL as a (non-perfect) workaround as the MPSL is distributed as a binary library.

[AGeegee]

Hi Einar,

Thanks for confirming that. How does the MPSL affect the POWER/CLOCK interrupt?

Does it disconnect / reconnect existing IRQs?

Using Zephyr, there is a

"nrfx_power_clock_irq_handler"

Seeing as this calls the MPSL POWER IRQ handler, just want to confirm that no additional IRQs for POWER/CLOCK need to be CONNECTED before and after mpsl_lib_init/uninit.

[Einar Thorsrud]

Hi,

The MPSL itself does not disconnect interrupts in the NVIC, but it disables the enabled interrupts in POWER/CLOCK regsiter and do not re-enable any. So any that you need (for instance for USB in this case), needs to be re-enabled.

[Einar Thorsrud]

Hi,

This will be fixed in nRF Connect SDK 3.2.0 (and is currently fixed in main).