nRF52840 NRF_RADIO->SHORTS Register

RE: nRF52840 NRF_RADIO->SHORTS Register

AKV — Tue, 08 Nov 2022 14:32:58 GMT

Thanks for the response.

I have checked the register by using the ble_radio_notification_evt_handler, as you said that the values are correct. READY_START and END_DISABLE is True.

RE: nRF52840 NRF_RADIO->SHORTS Register

Jørgen Holmefjord — Tue, 08 Nov 2022 08:55:56 GMT

The SoftDevice is already highly optimized to limit CPU time and keep power consumption as low as possible. The shorts you mention are already used by the SoftDevice, so you do not need to enable them manually.

You can check this by enabling the Radio Notification feature, then read out the RADIO->SHORTS register using a debugger when hitting a breakpoint in the radio notification handler:

RE: nRF52840 NRF_RADIO->SHORTS Register

AKV — Tue, 08 Nov 2022 06:30:38 GMT

Thanks for the prompt response.

Basically we would like the CPU load to be reduced to enable time for our application. For this, we want to eliminate the time that the CPU spends in the setting the Radio from end state to Disable state and Ready to Start states ( eliminate the time the Radio is in the RXIDLE and TXIDLE states ) of the Radio. Believe the Shorts aid in this. These state transitions are handled by interrupts to the CPU, I believe. Eliminating these interrupts will aid in getting more time for our application. Since the Radio is capable of handling these by just setting the registers, we would like to take advantage of that.

The shorts we are trying to implement is described in Fig 114 ( for Tx ) and Fig 117 (for Rx ) in the Ver 1.5 specification sheet of the nRF52840.

We want to do this through the softdevice only so that we dont break anything in the system.

Hope there is a mechanism to achieve this .

RE: nRF52840 NRF_RADIO->SHORTS Register

Jørgen Holmefjord — Mon, 07 Nov 2022 15:05:48 GMT

Hi,

Access to the RADIO peripheral is "Blocked" when the SoftDevice is enabled, see Hardware peripherals. It is not possible to set the SHORTS register when the SoftDevice is enabled, apart from inside a Timeslot, see Concurrent multiprotocol implementation using the Radio Timeslot API. Changing the register value when the SoftDevice have control of the RADIO would potentially break the SoftDevice functionality. What are you trying to achieve by setting this registers?

Best regards,
Jørgen