Question of setting NRF_RADIO->TASKS_DISABLE

[stephen]

Hi there,

I'm developing some proprietary RF application recently with nRF52. In this application, the radio frequency (tx and rx) is changed very often(every 3ms) by calling timeslot API. I know the NRF_RADIO->TASKS_DISABLE =1 should be set before setting another radio frequency. The following is some part of my code.

NRF_RADIO->TASKS_DISABLE = 1;
while (NRF_RADIO->EVENTS_DISABLED == 0) {}
NRF_RADIO->FREQUENCY= freq;

In most case, it seems work well. But, sometimes it will never get events_disabled =1 and can not get out of while loop. Anyone know what's wrong? In addition, is it okay to execute tasks_disable anytime even if the radio state machine is running in the tx or rx?

[ovrebekk]

Hi Stehpen

What SoftDevice are you running?

Do you make sure not to exceed the length of the timeslot?

You can disable the radio in the middle of a TX/RX packet, aborting the current transaction.

Best regards

[stephen]

Hi Torbjørn,

Thanks for replying my question! I use s132 v3.0. The length of timeslot are set to be 50ms, but it failed around "16ms" rarely. So, I think it should be within the timeslot. Do you have any idea? Stephen

[stephen]

Hi Torbjørn, Do you have a better way to know whether the device is in timeslot or not while getting failture of frequency change?

[ovrebekk]

Hi Stephen

It is recommended to use TIMER0 to measure the length of the timeslot. It will be reset automatically at the start of the timeslot, and you can use the CC registers to trigger various events relative to the start of the timeslot.

Are you running the radio code inside the timeslot interrupt, or in the main context?

Best regards

[stephen]

Hi Torbjørn, Thanks for your suggestion about measuring timeslot. I was running the radio code inside the main context. Is that okay? Or, is it more safe to change radio frequency inside timeslot interrupt? Look forward to your reply. Stephen