SLAU846B June 2023 – November 2024 MSPM0G1105 , MSPM0G1106 , MSPM0G1107 , MSPM0G1505 , MSPM0G1506 , MSPM0G1507 , MSPM0G1519 , MSPM0G3105 , MSPM0G3105-Q1 , MSPM0G3106 , MSPM0G3106-Q1 , MSPM0G3107 , MSPM0G3107-Q1 , MSPM0G3505 , MSPM0G3505-Q1 , MSPM0G3506 , MSPM0G3506-Q1 , MSPM0G3507 , MSPM0G3507-Q1 , MSPM0G3519
In RTC_x instances only, an RTC timestamp feature allows the capture of an RTC status on the detection of a timestamp event. When a timestamp event happens, the whole RTC register from seconds to years is copied to the timestamp capture registers. In case of multiple timestamp events, the TSCAPTURE register defines whether only the first or every (last) RTC status should be captured. The timestamp event status is sticky and needs to be cleared by software with the TSCLR register bit.
See Figure 28-4 for the RTC block diagram and timestamping.
The following timestamp events are supported:
VDD fail event
The VDD fail event allows the capture of a timestamp when the main supply (VDD) is lost. Once the device's main supply regains power, the timestamp status information indicates that a power low timestamp event happened.