nRFX DPPI single in multiple out for nRF54L15

[PuffinEgg]

Hi,

I would like an nRFX example on how to set up DPPI using single in (1 Event) and multiple out (2 Tasks). I have previously done this using the fork functionality in PPI (

nrfx_gppi_fork_endpoint_setup) when working with nRF52832. However, it looks like DPPI in nRF54L15 no longer supports forking since the concept of subscriber/publisher is used. However, I was not able to get this set up using nrfx_gppi_task_endpoint_setup(). Upon closer inspection at the SDK file, it looks like the definition for that function is not even defined. Therefore, It would be nice to get an example on how to set this up properly using nRFX.

[Håkon Alseth]

Hi,

 

I have previously done this using the fork functionality in PPI (

nrfx_gppi_fork_endpoint_setup) when working with nRF52832.

This shall be available for the nRF54L-series devices as well:

https://github.com/zephyrproject-rtos/hal_nordic/blob/master/nrfx/helpers/nrfx_gppi_dppi_ppib_lumos.c#L582-L596

 

However, it looks like DPPI in nRF54L15 no longer supports forking since the concept of subscriber/publisher is used. However, I was not able to get this set up using nrfx_gppi_task_endpoint_setup(). Upon closer inspection at the SDK file, it looks like the definition for that function is not even defined. Therefore, It would be nice to get an example on how to set this up properly using nRFX.

Forking is not a requirement in the same way as it was with PPI. DPPI has a inbuilt event system, where anyone listening in on the specific event is able to perform a task when it occurs. Forking is effectively not strictly required with DPPI, as it is "forkable" by design.

Could you share a bit more info on what you're trying to do? It sounds like a issue when porting and if you have previously used nrfx_gppi, it should be both PPI and DPPI compliant.

 

Kind regards,

Håkon