nRF5340 event channels

[turboscrew]

The documentation (Product specification v1.2) is not very clear about the event channels.

I wonder if there are:

- 32 event channels

- 6 event channel groups

- 16 EGUs

Writing "1" to EGU[n] tasks_trigger triggers the event configured to EGU[n] publish_triggered?

Reading EGU[n] events_triggered gives "1" if event configured to EGU[n] subscribe_trigger has happened?

One EGU can only trigger one event and "listen to" one event?

Even if 8-bit values (0-255) can be entered in the subscribe-registers, only values 0 - 31 make sense?

You can only use channel groups by SW via DPPIC? Or is there (at least in theory) possibility to configure channel groups as triggers to some peripherals?

[Edvin]

Hello,

Writing "1" to EGU[n] tasks_trigger triggers the event configured to EGU[n] publish_triggered?

Yes.

Reading EGU[n] events_triggered gives "1" if event configured to EGU[n] subscribe_trigger has happened?

Yes.

One EGU can only trigger one event and "listen to" one event?

No. *

Even if 8-bit values (0-255) can be entered in the subscribe-registers, only values 0 - 31 make sense?

What 8 bit value are you talking about here?

You can only use channel groups by SW via DPPIC? Or is there (at least in theory) possibility to configure channel groups as triggers to some peripherals?

What do you mean by "channel groups by SW via DPPIC"? I believe you can have one event triggering several tasks, and several tasks triggering one event. At least that is my understanding, but I haven't had the chance to test this on the nRF53 yet.

* regarding the EGU only triggered by one event and listen to one event, I think that is more related to the DPPI, and you can link multiple tasks to the same EGU event, and vice versa. How many DPPI channels you need to use depends on your setup.

Best regards,

Edvin

[turboscrew]

I was talking about these 8-bit values (SAADC_SUBSCRIBE_START):

About the channel groups:

And yes, I'm trying to keep tasks, events, interrupts and event channels apart, like Nordic, in general, seems to do.

About the channels: I meant, to my understanding, there are 32 event channels, regardless of my needs.

[Edvin]

Hello,

I see that it says in the section "Subsicribing to and publishing on channels" that "Writing non-existing channel index (CHIDX) numbers into a peripheral's publish or subscribe registers will yield unexpected results."

So you should only use the values 0 -> 31.

BR,
Edvin