Bluetooth timeslot: sd_radio_request() takes a few ms which glitches an interrupt

RE: Bluetooth timeslot: sd_radio_request() takes a few ms which glitches an interrupt

Susheel Nuguru — Tue, 24 Mar 2020 11:24:43 GMT

updated the links, this is softdevice feature and I think it has changed before SDv6. Which softdevice version are you using?

RE: Bluetooth timeslot: sd_radio_request() takes a few ms which glitches an interrupt

Jordan Archer — Mon, 23 Mar 2020 23:00:56 GMT

Is this still true? And in what version of the SDK, on what parts? And please update the link to the diagram.

RE: Bluetooth timeslot: sd_radio_request() takes a few ms which glitches an interrupt

Susheel Nuguru — Thu, 22 Nov 2018 15:05:33 GMT

Hi Liam,

on S140 the MCU is not blocked while using radio. So the application still has access to it apart from the pre and post processing it needs which can be seen in this diagram. As you can see that worst timing here that the softdevice steals MCU from APP is around 9uS and in your case your interrupt being masked for milliseconds does seem too much. How many milli seconds does it gets masked in worst case? Is it possible that some other high priority interrupt is masking your interrupt? Also what is the priority of your interrupt?