Cleanup at timeslot end

[rgrr2]

Hi

if one searches the examples using the timeslot API, every application seems to do it's own timeslot cleanup.  Also documentation is not very clear about this.

Best/most confusing is nrf_raal_softdevice.c which does an exit with explicitly raising the radio interrupt (nrf_raal_continuous_mode_exit()).  I'm looking with some big question mark in my head at those __DMB()s.  Are they really required?

So my question: in what state RADIO/TIMER0/PPI etc should be left so that softdevice operation can continue correctly?

Thanks

Hardy

[Hung Bui]

Hi Hardy, 

If you want to test timeslot, I would suggest you to have a look here: https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/running-micro-esb-concurrently-with-ble

It's pretty old but the principle is the same. When you receive NRF_RADIO_CALLBACK_SIGNAL_TYPE_TIMER0 you have to stop the TIMER, RADIO etc. 
It's showed in the code above where TIMESLOT_END_IRQHandler() is called. 

I also attached here an example on SDK v15.0 . The radio is not used but you can find the TIMER being stopped in NRF_RADIO_CALLBACK_SIGNAL_TYPE_TIMER0 event in timeslot.c (the example is in \examples\ble_peripheral\ble_app_uart) 

nRF5_SDK_15.0.0_Timeslot.zip

[rgrr2]

Hi Hung Bui

don't want to waste *your* time, but I'm already discussing an occuring failed assertion inside the softdevice in another thread with a colleague of you, see https://devzone.nordicsemi.com/f/nordic-q-a/58373/timeslots-and-softdevice-assertion-failed-pcxxx-0x2552e

My original idea of incorrect cleanup at end of timeslot seems to lead in the right direction: it has (hopefully) something to do with changed interrupt priorities of the radio.

Thanks for your support again.

Hardy