What resource is used by IDLE-STATE TimeSlot?

RE: What resource is used by IDLE-STATE TimeSlot?

Hung Bui — Mon, 22 Jul 2019 15:07:12 GMT

Hi Syuji,

The application should only call sd_radio_session_close() when there is no scheduled timeslot, it want to stop the session (when in IDLE).

Between timeslots, the application doesn't need to call sd_radio_session_close().

There should be no peripheral occupied between timeslot (not in timeslot, but before you call sd_radio_session_close() )

In other words, there shouldn't be any peripheral occupied when in IDLE mode, unless it's the softdevice activity.

RE: What resource is used by IDLE-STATE TimeSlot?

loquat — Mon, 22 Jul 2019 14:12:02 GMT

Sorry,

timeslot_open() -> sd_radio_session_open()
timeslot_request() -> sd_radio_request()
timeslot_end() -> sd_radio_session_close()

After receive NRF_EVT_RADIO_SESSION_IDLE(timeslot end),
If I do not call sd_radio_session_close(), Are there any resources that will not be released?

RE: What resource is used by IDLE-STATE TimeSlot?

Hung Bui — Mon, 15 Jul 2019 07:37:50 GMT

Hi Syuji,

I'm not quite sure I fully understand your question.

Please post your code inside timeslot_open(), timeslot_request() and timeslot_end()

What exactly you meant by "timeslot_request() - timeslot_end()" ?

When in timeslot period, there will be only RTC0 (and SWI5) occupied by the softdevice. No other peripheral will be used unless you use them in your code.

Timeslot is automatically closed base on the timeslot period that you request. The softdevice uses RTC0 to count this.