26.6.17 RTC TimeStamp Time Register 0 (UTC_MODE)
RTC_TSTR0 reports the timestamp of the first tamper event after reading RTC_TSSR0.
| Name: | RTC_TSTR0 (UTC_MODE) |
| Offset: | 0xB0 |
| Reset: | 0x00000000 |
| Property: | Read-only |
| Bit | 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | |
| BACKUP | TEVCNT[3:0] | ||||||||
| Access | R | R | R | R | R | ||||
| Reset | 0 | 0 | 0 | 0 | 0 | ||||
| Bit | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | |
| Access | |||||||||
| Reset |
| Bit | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | |
| Access | |||||||||
| Reset |
| Bit | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | |
| Access | |||||||||
| Reset |
Bit 31 – BACKUP System Mode of the Tamper (cleared by reading RTC_TSSR0)
| Value | Description |
|---|---|
| 0 |
The state of the system is different from Backup mode when the tamper event occurs. |
| 1 |
The system is in Backup mode when the tamper event occurs. |
Bits 27:24 – TEVCNT[3:0] Tamper Events Counter (cleared by reading RTC_TSSR0)
Each time a tamper event occurs, this counter is incremented. This counter saturates at 15. Once this value is reached, it is no more possible to know the exact number of tamper events.
If this field is not null, this implies that at least one tamper event occurs since last register reset and that the values stored in timestamping registers are valid.