SLAU847D October 2022 – May 2024 MSPM0L1105 , MSPM0L1106 , MSPM0L1227 , MSPM0L1228 , MSPM0L1228-Q1 , MSPM0L1303 , MSPM0L1304 , MSPM0L1304-Q1 , MSPM0L1305 , MSPM0L1305-Q1 , MSPM0L1306 , MSPM0L1306-Q1 , MSPM0L1343 , MSPM0L1344 , MSPM0L1345 , MSPM0L1346 , MSPM0L2227 , MSPM0L2228 , MSPM0L2228-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 25-144.
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 |