SLAU846A June 2023 – October 2023 MSPM0G1105 , MSPM0G1106 , MSPM0G1107 , MSPM0G1505 , MSPM0G1506 , MSPM0G1507 , MSPM0G3105 , MSPM0G3105-Q1 , MSPM0G3106 , MSPM0G3106-Q1 , MSPM0G3107 , MSPM0G3107-Q1 , MSPM0G3505 , MSPM0G3505-Q1 , MSPM0G3506 , MSPM0G3506-Q1 , MSPM0G3507 , MSPM0G3507-Q1
The RTC module contains two event publishers and no event subscribers. One event publisher (CPU_INT) manages RTC interrupt requests (IRQs) to the CPU subsystem through a static event route. The second event publisher (GEN_EVENT) can be used to publish RTC events to a subscriber through a generic event route channel.
The RTC events are summarized in Table 26-125.
Event | Type | Source | Destination | Route | Configuration | Functionality |
---|---|---|---|---|---|---|
CPU interrupt event | Publisher | RTC | CPU Subsystem | Static route | CPU_INT registers | Fixed interrupt route from RTC to CPU |
Generic event | Publisher | RTC | Generic event channel | Generic route (FPUB_0) | GEN_EVENT registers, FPUB_0 register | Trigger generic event channel from RTC |