Do peripheral events used in shortcuts still generate interrupts?

RE: Do peripheral events used in shortcuts still generate interrupts?

Andrew Kohlsmith — Tue, 10 Jul 2018 12:25:25 GMT

Oh! I understand now, and this makes perfect sense.

THANK YOU. I now understand the issue. The nRF51 is doing exactly what I told it to do, but not necessarily what I want it to do. :-)

RE: Do peripheral events used in shortcuts still generate interrupts?

ovrebekk — Tue, 10 Jul 2018 12:07:39 GMT

Hi Andrew

If the DISABLED_RXEN field is set in the SHORTCUTS register when you run the _disable_radio() function, then the radio will enter RX mode before you have time to enter TX mode.

A simple way to check if this is the case is to clear this field at the start of _disable_radio(), and set it again afterwards:

// Clear Disabled -> RXEN shortcutNRF_RADIO->SHORTS &= ~RADIO_SHORTS_DISABLED_RXEN_Msk;

// Set Disabled -> RXEN shortcutNRF_RADIO->SHORTS |= RADIO_SHORTS_DISABLED_RXEN_Msk;

Best regards
Torbjørn

RE: Do peripheral events used in shortcuts still generate interrupts?

Andrew Kohlsmith — Tue, 10 Jul 2018 03:58:14 GMT

Good evening, Torbjørn,

I believe I am doing things correctly; is my _disable_radio() function above doing the correct thing? (clearing the event flag, then setting the task and spinning, waiting for the event flag to become set again)

RE: Do peripheral events used in shortcuts still generate interrupts?

ovrebekk — Mon, 09 Jul 2018 13:04:30 GMT

Hi Andrew

Do you make sure to set the SHORTCUT register only after you have run the _disable_radio() function?

Otherwise you will inadvertently enable the RX mode by disabling the radio, and you won't be able to enter TX.

I just did a quick test using the nrf_esb library, and I can see the END interrupt firing even if the shortcuts are used.

Best regards
Torbjørn