Alternative of mpsl radio notification API in NCS v2.6.0

RE: Alternative of mpsl radio notification API in NCS v2.6.0

Vidar Berg — Thu, 03 Apr 2025 04:56:23 GMT

Hi,

This is different from the request the original poster had. It is not possible to define another ISR for the RADIO IRQ as it is already implemented in the Bluetooth controller. Please create a new ticket and include more details about your setup and what you're trying to achieve.

RE: Alternative of mpsl radio notification API in NCS v2.6.0

lahn — Wed, 02 Apr 2025 13:25:57 GMT

Hi Vidar,

as I'm also in dire need for triggering an event on each ble package sent (NRF_RADIO_EVENT_PHYEND),
is there already an easy way to set this up on nRF54L15?

I tried the following, but it seems like it does not do the trick...

    unsigned int irq = irq_connect_dynamic(DT_IRQN(DT_NODELABEL(radio)), IRQ_PRIO_LOWEST, on_radio_event, NULL, 0);
    irq_enable(DT_IRQN(DT_NODELABEL(radio)));
    nrf_radio_int_enable(NRF_RADIO, NRF_RADIO_INT_PHYEND_MASK);

RE: Alternative of mpsl radio notification API in NCS v2.6.0

Vidar Berg — Fri, 05 Apr 2024 07:06:38 GMT

Yes, the peripheral can check the current connection interval by calling bt_conn_get_info(). It can also register the le_param_updated callback to get notified if the connection parameters are updated.

[quote user="pertan"]Of course, there will be no notification before the first connection event after a connection has been established, but I can live with that.[/quote]

There are other packets that need to be exchanged at the beginning of the connection such the feature exchange, MTU negotiation, PHY update, etc that may also impact the timing. Notifications must also be enabled by client if it can't be restored from bonding information stored in flash.

RE: Alternative of mpsl radio notification API in NCS v2.6.0

pertan — Thu, 04 Apr 2024 13:13:56 GMT

If the delay mechanisms you suggest are sufficiently accurate, that sounds like a promising approach, given that the peripheral is aware of the current connection interval. Of course, there will be no notification before the first connection event after a connection has been established, but I can live with that.

RE: Alternative of mpsl radio notification API in NCS v2.6.0

Vidar Berg — Thu, 04 Apr 2024 11:53:43 GMT

Thank you for explaining the use case. I believe you can still use the connection event trigger for this. After initiating the connection event trigger, you could start a one-off timer, a delayable work item, or something similar to acquire the data and add it to the notification queue before the next connection event occurs.

RE: Alternative of mpsl radio notification API in NCS v2.6.0

pertan — Thu, 04 Apr 2024 07:06:34 GMT

I'm using the signal to prepare and submit real time notification data for transmission. It is a time critical application, so I need to get the notification close to the connection event, but not too close since it takes some time to prepare and submit the outgoing data. This technique is described in this blog post. If there is no direct replacement, I'm interested to know what my options are for implementing this functionality myself.

RE: Alternative of mpsl radio notification API in NCS v2.6.0

Vidar Berg — Thu, 04 Apr 2024 06:37:38 GMT

Hi,

We currently do not have a direct replacement for this feature, unfortunately. Could you say a bit more about your use case for this signal?

RE: Alternative of mpsl radio notification API in NCS v2.6.0

pertan — Thu, 04 Apr 2024 06:17:38 GMT

Hi Vidar,

I'm also looking for an alternative to the MPSL radio notification API in nRF Connect SDK v2.6.0+. More specifically, I'm relying on notifications fired some time before the radio turns on (MPSL_RADIO_NOTIFICATION_DISTANCE_420US). What is the equivalent API in nRF Connect SDK v2.6.0?

Thanks

RE: Alternative of mpsl radio notification API in NCS v2.6.0

Vidar Berg — Tue, 19 Mar 2024 10:24:50 GMT

Hi Narendra,

Thanks. Support for triggering on advertisement events has been added as a feature request internally and should be added in a future release. The only workaround I can think of for now is to use PPI+EGU to trigger a SW interrupt on RADIO events, similar to how the PPI trace library does it. This will require some additional application logic to determine when the advertisement event is completed.

Regards,

Vidar

RE: Alternative of mpsl radio notification API in NCS v2.6.0

Narendra — Tue, 19 Mar 2024 08:55:00 GMT

Hi Vidar,

In our firmware, we are using radio off/inactive events to stop advertisements, switch/change advertisement packets, and measure battery level when the radio is off/inactive.

Regards,

Narendra

RE: Alternative of mpsl radio notification API in NCS v2.6.0

Vidar Berg — Tue, 19 Mar 2024 07:52:02 GMT

Hi Narendra,

Could you please outline your use case and requirements in a bit more detail so I can check if there may be any alternative solutions? The Event Trigger feature is currently limited to BLE connections, unfortunately.

RE: Alternative of mpsl radio notification API in NCS v2.6.0

Narendra — Tue, 19 Mar 2024 06:21:53 GMT

Hi Vidar,

Thank you. I have looked at the suggested example. This example is about how we can get an event for connection, right?

Would you please help how can we get the event for radio off/inactive?

Regards,

Narendra

RE: Alternative of mpsl radio notification API in NCS v2.6.0

Vidar Berg — Fri, 15 Mar 2024 12:25:30 GMT

Hi,

Yes, please have a look at the Bluetooth: Event Trigger sample.

Best regards,

Vidar