PPI radio events with SoftDevice Controller

[cegerer]

Hello!

With nRF52, nRF5 SDK and SoftDevice S130, we were using some of the Radio's PPI events (e.g. EVENT_END) for some functionality.

Now we plan to move to nRF54L and while porting some of the code to nRF Connect SDK, I noticed that the Radio's DPPI configuration (e.g. PUBLISH_ADDRESS) is reset once I start advertising.

Is this expected behaviour with the nRF Connect SDK and SoftDevice Controller? Searching the docs, I found that the MPSL owns the Radio peripheral on nRF54L. I guess that means that it owns it exclusively and all configurations done will have no effect?

Is there another possibility to use events of the Radio peripheral?

[Hung Bui]

Hi Christian, 

I assume you are asking about the radio notification callback feature. It now a Bluetooth library  in the SDK: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/libraries/bluetooth/radio_notification_conn_cb.html

There is a sample that you can try https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/bluetooth/radio_notification_cb/README.html#ble-radio-notification-conn-cb

But as far as I know it only give you a callback before the radio event, not after it. 


You can still access DPPI but as you mentioned it get reset after every radio event. Here is some info from R&D when suggested a "hack" to use the PUBLISH_TXREADY register: 
one hacky way to work around that could be to re-write PUBLISH_TXREADY after every radio interrupt here for example https://github.com/nrfconnect/sdk-nrf/blob/4eb29ffba260d2138cccfa18b59fe92d63e7239a/subsys/mpsl/init/mpsl_init.c#L244
Also there are some debug pin toggling that you can use: 
https://docs.nordicsemi.com/bundle/ncs-latest/page/kconfig/index.html#!MPSL_PIN_DEBUG