The event manager transfers digital events from one entity (for example, a peripheral) to another (for example, a second peripheral, the DMA or the CPU). The event manager implements event transfer through a defined set of event publishers (generators) and subscribers (receivers) that are interconnected through an event fabric containing a combination of static and programmable routes.
Events that are transferred by the event manager include:
- Peripheral event transferred to the CPU as an interrupt request (IRQ) (Static Event)
- Example: GPIO interrupt is sent to the CPU
- Peripheral event transferred to the DMA as a DMA trigger (DMA Event)
- Example: UART data receive trigger to DMA to request a DMA transfer
- Peripheral event transferred to another peripheral to directly trigger an action in hardware (Generic Event)
- Example: TIMx timer peripheral publishes a periodic event to the ADC subscriber port, and the ADC uses the event to trigger start-of-sampling
For more details, see the Event chapter of the MSPM0 L-Series 32MHz Microcontrollers Technical Reference Manual.
Table 8-3 Generic Event Channels A generic route is either a point-to-point (1:1) route or a point-to-two (1:2) splitter route in which the peripheral publishing the event is configured to use one of several available generic route channels to publish the event to another entity (or entities, in the case of a splitter route). An entity can be another peripheral, a generic DMA trigger event, or a generic CPU event.CHANID | Generic Route Channel Selection | Channel Type |
---|
0 | No generic event channel selected | N/A |
1 | Generic event channel 1 selected | 1 : 1 |
2 | Generic event channel 2 selected | 1 : 1 |
3 | Generic event channel 3 selected | 1 : 2 (splitter) |