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 provides six interrupt sources, of which one can be configured to publish an event to a generic event route channel are given in Table 28-506.
Index | Name | Description |
---|---|---|
0 | RTCRDY | Indicates that the RTC counter/calendar registers are safe to be read for approximately one second |
1 | RTCTEV | Interval interrupt, configurable as once per minute, per hour, at midnight, or at noon |
2 | RTCA1 | Calendar alarm 1 interrupt |
3 | RTCA2 | Calendar alarm 2 interrupt |
4 | RTC0PS | Prescaler 0 periodic alarm interrupt |
5 | RTC1PS | Prescaler 1 periodic alarm interrupt |
The generic event publisher configuration is managed with the GEN_EVENT event management registers. See Section 7.2.5 for guidance on configuring the event registers for generic event publishers.
The generic event channel which generic event is to publish to must be selected by writing the target generic channel ID to the FPUB_0 register in the RTC. See Section 7.1.3.3 for guidance on configuring generic event routes.
If this publisher is not used in an application, the FPUB_0 register can be left in a disconnected state (set equal to zero) and no events should be unmasked through the MIS register in the RTC GEN_EVENT register set.