Function address as PPI "Task End-Point"

RE: Function address as PPI "Task End-Point"

Ole Morten — Mon, 05 Aug 2013 07:20:18 GMT

To do this, you will have to use multiple PPI channels. Each channel connects one task with one event. But it's perfectly possible to have multiple channels connected to the same task or event, as stated in section 15.1 in the RM: "One event can trigger multiple tasks by using multiple channels and one task can be triggered by multiple events in the same way."

RE: Function address as PPI "Task End-Point"

Sébastien Despont — Mon, 05 Aug 2013 07:17:56 GMT

One last question : is it possible to define several tasks as PPI TEP to execute more than one task at the same time?

Like Timer1 stop AND Timer2 start AND GPIOTE task

Best regards

RE: Function address as PPI "Task End-Point"

Sébastien Despont — Mon, 05 Aug 2013 07:03:36 GMT

Ok, thanks.

RE: Function address as PPI "Task End-Point"

Ole Morten — Mon, 05 Aug 2013 07:01:52 GMT

There isn't a complete list of all tasks, but in the nRF51 Series Reference Manual, all tasks for each peripheral are listed at the start of each peripheral's register table. See for example table 18 for the radio, table 19 for the TIMERs, table 36 for the TWI and so on.

RE: Function address as PPI "Task End-Point"

Sébastien Despont — Mon, 05 Aug 2013 06:57:33 GMT

Thanks for your quick answer.

Where can I found a list of available tasks which can be bound to the PPI TEP?

Best Regards

RE: Function address as PPI "Task End-Point"

Ole Morten — Mon, 05 Aug 2013 06:54:22 GMT

Any task is a valid end-point for a PPI channel (not just tasks in timers and GPIOTE), but not a code function. The PPI can only be used to connect tasks and events from different peripheral blocks inside the nRF51, not code.