This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Are PPI events and interrupt connected?

How should we comprehend the nature of PPI, when dealing with radio interrupts?

For example, if I point radio event handler call back ( of this type:

static nrf_radio_signal_callback_return_param_t*)

to a radio interrupt event handler function of my own, let's call it radio_event_handler, I can do switch-case on these 4:

NRF_RADIO->EVENTS_END

NRF_RADIO->BCMATCH

NRF_RADIO->READY

NRF_RADIO->ADDRESS

in order to tackle different scenarios.

I'm however curious as is there a connection between generating a radio event/interrupt (on NVIC if I'm not mistaken) and producing a PPI event like NRF_RADIO->EVENTS_END? Are they, for example, synchronized? Completely unrelated (Which is very unlikely)?

Parents
  • I having trouble understanding what you mean. PPI allows you to connect an event in one peripheral to a task in another peripheral, the event will trigger the task without CPU intervention. If you don't use PPI you usually configure the peripheral to trigger an interrupt when a certain event happens, so that the CPU can react to it, with for example setting a task in another peripheral.

Reply
  • I having trouble understanding what you mean. PPI allows you to connect an event in one peripheral to a task in another peripheral, the event will trigger the task without CPU intervention. If you don't use PPI you usually configure the peripheral to trigger an interrupt when a certain event happens, so that the CPU can react to it, with for example setting a task in another peripheral.

Children
No Data
Related