Hi,
Furhter to this post, I still getting unexplained behavior.
I use timeslot api to generate a burst of 10 hard-real time-pulses 29000us apart.
For the first 9 pulses, in the TIMER0 event callback I set the returned action to NRF_RADIO_SIGNAL_CALLBACK_ACTION_REQUEST_AND_END and the request.p_next member to the request structure.
On the 10th pulse, in the TIMER0 event callback, I set the return value to NRF_RADIO_SIGNAL_CALLBACK_ACTION_END (and the request.p_next to NULL).
I expect to get NRF_EVT_RADIO_SESSION_IDLE in the event signal handler but it does not show.
The above prevents (I assume) the session from being closed (does not get NRF_EVT_RADIO_SESSION_CLOSED event) and re-opened (I get NRF_ERROR_BUSY error)
What can be wrong? Why the session seem to remain busy and doesn't move to IDLE ?
Thanks