RADIO_STATE_STATE_TxDisable associated handle

[avaldes]

Is there a way to obtain context on when a particular BLE transmission ends

RADIO_STATE_STATE_TxDisable == NRF_RADIO->STATE

An by context I mean to know what handle was the one transmitted?

So at the moment we are able to get the event of TXDisable but we are not able to be sure of what handle that belongs to.

[Susheel Nuguru]

Hi avaldes,

Before I could assist you, could you please give me some more info.
Are you using softdevice for your BLE operations or is this based on NCS/Zephyr?
Which API have you used to get the TxDisable event?

[avaldes]

Hi Susheel

Sorry for the confusion.

1-) We are using Softdevice.

2-) In order to get o the TxDisable we are usingthe PPI module to route the NRF_RADIO->EVENTS_END to be routed to SWI3_EGU3_IRQHandler

This part works as expected

void SWI3_EGU3_IRQHandler(void)
{
    if (nrf_egu_event_check(NRF_EGU3, NRF_EGU_EVENT_TRIGGERED0))
    {
        if(RADIO_STATE_STATE_TxDisable == NRF_RADIO->STATE)
        {
            // some work specific to a particular message
        }

        nrf_egu_event_clear(NRF_EGU3, NRF_EGU_EVENT_TRIGGERED0);
    }
}

So we just want to know if there is any way to know which handle just got out.

[Susheel Nuguru]

Unfortunately no then.

Both PPI and sd_radio_notifications are context less. Unless you are using timeslots API for every BLE transaction and keep track of the context in the application, it seems it is not possible to keep track the context of the transaction.