AN4759

Application note
Using the hardware real-time clock (RTC) in low-power modes with
STM32 microcontrollers
Introduction
A real-time clock (RTC) is a computer clock that keeps track of the current time. Although
the RTCs are often used in personal computers, servers and embedded systems, they are
also present in almost any electronic device that requires an accurate time keeping. The
microcontrollers supporting the RTC can be used for chronometers, alarm clocks, watches,
small electronic agendas, and many other devices.
This application note describes the features of the real-time clock (RTC) controller embedded
in the ultra-low-power STM32 microcontrollers and the steps required to configure the RTC for
the use with the calendar, alarm, periodic wakeup unit, tamper detection, timestamp and
calibration applications.
Software examples are then provided to show how to use the RTC in the low-power modes
and how to ensure the tampering detection and timestamp while the main supply is switched
off and the MCU is supplied by an alternate battery. One example is showing also a possible
implementation of the smooth calibration features.
The X-CUBE-RTC embedded software package is delivered with this application note,
containing the source code of the RTC examples and all the embedded software modules
required to run the examples.
Table 1. Applicable products
Type
Microcontrollers

October 2016

Product series and part number

STM32L0 Series, STM32L1 Series, STM32L4 Series, STM32F0 Series,
STM32F2 Series, STM32F3 Series, STM32F4 Series, STM32F7 Series,
X-CUBE-RTC

DocID028310 Rev 2

1/51
www.st.com

Contents

AN4759

Contents
1

Overview of the STM32 MCU advanced RTC . . . . . . . . . . . . . . . . . . . . . 6

1.1

1.2

1.3

1.4

2/51

1.1.1

Software calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1.2

RTC hardware calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1.3

Initializing the calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1.4

RTC clock configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

RTC alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

1.2.1

RTC alarm configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.2.2

Alarm sub-second configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

RTC periodic wakeup unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1.3.1

Programming the auto-wakeup unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1.3.2

Maximum and minimum RTC wakeup period . . . . . . . . . . . . . . . . . . . . 16

Digital smooth calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

1.4.1

RTC calibration basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

1.4.2

Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

1.5

Synchronizing the RTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

1.6

RTC reference clock detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

1.7

Time-stamp function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

1.8

RTC tamper detection function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

1.8.1

Edge detection on tamper input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

1.8.2

Level detection on tamper input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

1.8.3

Timestamp on tamper detection event . . . . . . . . . . . . . . . . . . . . . . . . . . 26

1.9

Backup registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

1.10

Alternate function RTC outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

1.11

RTC calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.10.1

RTC_CALIB output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

1.10.2

RTC_ALARM output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

RTC security aspects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

1.11.1

RTC register write protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

1.11.2

Enter/exit initialization mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

1.11.3

RTC clock synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Advanced RTC features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

DocID028310 Rev 2

AN4759

Contents

Reducing power consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3.1

Using the right power reduction mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3.2

Use tamper pin internal pull-up resistor . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3.3

Setting the RTC prescalers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

STM32L4 API and tampering detection application example . . . . . . . 37

4.1

STM32 Cube firmware libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4.2

STM32 Cube expansion firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4.3

Application example project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4.3.1

Hardware Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4.3.2

Software setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.3.3

LED meaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.3.4

Tampering detection during normal operation . . . . . . . . . . . . . . . . . . . . 40

4.3.5

Tampering detection when main power supply is off . . . . . . . . . . . . . . . 41

STM32L4 API and digital smooth calibration application example . . 42

5.1

STM32 Cube firmware libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

5.2

STM32 Cube expansion firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

5.3

Application example project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

5.3.1

Hardware setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

5.3.2

Software setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

5.3.3

Application block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

5.3.4

Run time observations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

STM32L0 API and tampering detection application example . . . . . . . 45

6.1

STM32 Cube firmware libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

6.2

STM32 Cube expansion firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

6.3

Application example project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

6.3.1

Hardware setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

6.3.2

Software setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

6.3.3

LED meaning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

6.3.4

Tampering detection during normal operation . . . . . . . . . . . . . . . . . . . . 48

Reference documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

DocID028310 Rev 2

3/51
3

List of tables

AN4759

List of tables
Table 1.
Table 2.
Table 3.
Table 4.
Table 5.
Table 6.
Table 7.
Table 8.
Table 9.
Table 10.
Table 11.
Table 12.
Table 13.
Table 14.
Table 15.
Table 16.
Table 17.
Table 18.
Table 19.

4/51

Applicable products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Steps to initialize the calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Calendar clock equal to 1 Hz with different clock sources . . . . . . . . . . . . . . . . . . . . . . . . . 10
Steps to configure the alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Alarm combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Alarm sub-second mask combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Steps to configure the auto-wakeup unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Timebase/wakeup unit period resolution with clock configuration 1 . . . . . . . . . . . . . . . . . . 16
Min. and max. timebase/wakeup period when RTCCLK= 32768 . . . . . . . . . . . . . . . . . . . . 17
Time-stamp features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Tamper features (edge detection) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Tamper features (level detection) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
RTC_CALIB output frequency versus clock source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Advanced RTC features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Tampering detection status when Power-On-Reset is detected. . . . . . . . . . . . . . . . . . . . . 48
Tampering detection status when tamper event is detected . . . . . . . . . . . . . . . . . . . . . . . 48
Tampering detection status when reset is detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Tampering detection status when tamper event is detected . . . . . . . . . . . . . . . . . . . . . . . 48
Document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

DocID028310 Rev 2

AN4759

List of figures

List of figures
Figure 1.
Figure 2.
Figure 3.
Figure 4.
Figure 5.
Figure 6.
Figure 7.
Figure 8.
Figure 9.
Figure 10.
Figure 11.
Figure 12.
Figure 13.
Figure 14.
Figure 15.
Figure 16.
Figure 17.
Figure 18.
Figure 19.
Figure 20.
Figure 21.
Figure 22.
Figure 23.
Figure 24.
Figure 25.
Figure 26.

RTC calendar fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Example of calendar displayed on an LCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
STM32L0 Series, STM32L1 Series, STM32F2 Series and STM32F4 Series
RTC clock sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
STM32L4 Series and STM32F7 Series RTC clock sources . . . . . . . . . . . . . . . . . . . . . . . . . 9
STM32F0 Series and STM32F3 Series RTC clock sources. . . . . . . . . . . . . . . . . . . . . . . . . 9
Prescalers from RTC clock source to calendar unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Alarm A fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Alarm sub-second field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Prescalers connected to the timebase/wakeup unit for configuration 1 . . . . . . . . . . . . . . . 16
Prescalers connected to the wakeup unit for configurations 2 and 3 . . . . . . . . . . . . . . . . . 17
Typical crystal accuracy plotted against temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Smooth calibration block. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
RTC shift register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
RTC reference clock detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Time-stamp event procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Tamper with edge detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Tamper with level detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Tamper sampling with precharge pulse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
RTC_CALIB clock sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Alarm flag routed to RTC_ALARM output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Periodic wakeup routed to RTC_ALARM pinout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Application example flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
STM32L476 evaluation board. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
STM32L476RG-Nucleo board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
STM32L053R8-Nucleo board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
LED LD2 behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

DocID028310 Rev 2

5/51
5

Overview of the STM32 MCU advanced RTC

AN4759

Overview of the STM32 MCU advanced RTC

The real-time clock (RTC) embedded in STM32 MCUs acts as an independent Binary
Coded Decimal (BCD) timer/ counter. The RTC can be used to provide a full-featured
calendar, alarm, periodic wakeup unit, digital calibration, synchronization, time-stamp, and
an advanced tamper detection.
Refer to Table 14: Advanced RTC features for the complete list of features available on
each device.

1.1

RTC calendar
A calendar keeps track of the time (hours, minutes and seconds) and date (day, week,
month, year). The RTC calendar offers several features to easily configure and display the
calendar data fields:

Calendar with:

Sub-seconds (not programmable)

Seconds

Minutes

Hours in 12-hour or 24-hour format

Day of the week (day)

Day of the month (date)

Month

Year

Calendar in binary-coded decimal (BCD) format

Automatic management of 28-, 29- (leap year), 30-, and 31-day months

Daylight saving time adjustment programmable by software

Figure 1. RTC calendar fields

'$7(
'DWH

:HHN
GDWH

7,0(

KRUKIRUPDW

0RQWK

<HDU

$0
30

57&B'5

KK

57&B75

PP

VV

57&B665

069

1. RTC_DR, RTC_TR are RTC Date and Time registers.

2. The sub-second field (RTC_SSR) is the value of the synchronous prescalers counter. This field is not
writable.

6/51

DocID028310 Rev 2

AN4759

1.1.1

Overview of the STM32 MCU advanced RTC

Software calendar
A software calendar can be a software counter (usually 32 bits long) that represents the
number of seconds. The software routines convert the counter value to hours, minutes, day
of the month, day of the week, month and year. This data can be converted to BCD format
and displayed on a standard LCD. Conversion routines use a significant program memory
space and are CPU-time consuming, which may be critical in certain real-time applications.

1.1.2

RTC hardware calendar

When using the RTC calendar, the software conversion routines are no longer needed
because their functions are performed by hardware.
The STM32 RTC calendar is provided in BCD format. This avoids binary to BCD software
conversion routines, which use significant program memory space and a CPU-load that may
be critical in certain real-time applications.
Figure 2. Example of calendar displayed on an LCD

09:40:28:09 PM
SUN AUG 23 2015

1.1.3

Initializing the calendar

Table 2 describes the steps required to correctly configure the calendar time and date.
Table 2. Steps to initialize the calendar
Step

What to do

How to do it

Comments

Write "0xCA" and then

Disable the RTC registers write
"0x53" into the
protection
RTC_WPR register

Enter Initialization mode

Set INIT bit to 1 in

RTC_ISR register

The calendar counter is

stopped to allow its update

Wait for the confirmation of

Initialization mode (clock
synchronization)

Poll INITF bit of in

RTC_ISR until it is set

It takes around 2 RTCCLK

clock cycles due to clock
synchronization.

RTC_PRER register:
Program the prescaler values if Write first the
synchronous value and
needed
then write the
asynchronous value

Load time and date values in

the shadow registers

Set RTC_TR and

RTC_DR registers

Configure the time format (12h

or 24h)

Set FMT bit in RTC_CR FMT = 0: 24 hour/day format

register
FMT = 1: AM/PM hour format

DocID028310 Rev 2

RTC registers can be modified

By default, the RTC_PRER

prescalers register is initialized
to provide 1Hz to the Calendar
unit when RTCCLK = 32768Hz
-

7/51
50

Overview of the STM32 MCU advanced RTC

AN4759

Table 2. Steps to initialize the calendar (continued)

Step

1.1.4

What to do

How to do it

Comments

Exit Initialization mode

Clear the INIT bit in

RTC_ISR register

Enable the RTC Registers

Write Protection

Write "0xFF" into the

RTC_WPR register

The current calendar counter is

automatically loaded and the
counting restarts after 4
RTCCLK clock cycles
RTC Registers can no longer
be modified

RTC clock configuration

RTC clock source
The RTC calendar can be driven by three clock sources LSE, LSI or HSE (see Figure 3 and
Figure 4).
Figure 3. STM32L0 Series, STM32L1 Series, STM32F2 Series and STM32F4 Series
RTC clock sources

+6(26&
0+]

+6(


+6(B57&

/6(26&
N+]

/6(

7R57&
57&&/.

57&6(/>@

/6,5&
N+]

/6,

06Y9

Note:

8/51

The RTCSEL[1:0] bits are the RCC Control/status register (RCC_CSR) [17:16] bits.

DocID028310 Rev 2

AN4759

Overview of the STM32 MCU advanced RTC

Figure 4. STM32L4 Series and STM32F7 Series RTC clock sources
/6,5&
N+]

/6,

57&6(/>@

/6,5&
N+]

7R57&

/6(26& /6(
N+]

+6(26& +6(
0+]

57&&/.



+6(B57&
06Y9

Note:

The RTCSEL[1:0] bits are the backup domain control register (RCC_BDCR) [9:8] bits.
Figure 5. STM32F0 Series and STM32F3 Series RTC clock sources
+6(

+6(26&
0+]


+6(B57&

/6(26&
N+]

7R57&

/6(

57&&/.

57&6(/>@

/6,5&
N+]

/6,

069

How to adjust the RTC calendar clock

The RTC features several prescalers that allow delivering a 1 Hz clock to the calendar unit,
regardless of the clock source.
Figure 6. Prescalers from RTC clock source to calendar unit
57&
&ORFN

$V\QFKURQRXV
SUHVFDOHU
35(',9B$

6\QFKURQRXV
SUHVFDOHU
35(',9B6

$V\QFKURQRXVELW
SUHVFDOHUGHIDXOW 

6\QFKURQRXVELW
SUHVFDOHUGHIDXOW 

&NB6SUH

&DOHQGDUXQLW
6KDGRZUHJLVWHUV
57&B75DQG
57&B'5
069

DocID028310 Rev 2

9/51
50

Overview of the STM32 MCU advanced RTC

AN4759

The formula to calculate ck_spre is:

RTCCLK
ck_spre = ----------------------------------------------------------------------------------------------( PREDIV_A + 1 ) ( PREDIV_S + 1 )

where:

RTCCLK can be any clock source: HSE_RTC, LSE or LSI

PREDIV_A can be 1,2,3,..., or 127

PREDIV_S can be 0,1,2,..., or 32767

Table 3 shows several ways to obtain the calendar clock (ck_spre) = 1 Hz.
Table 3. Calendar clock equal to 1 Hz with different clock sources
Prescalers

RTCCLK

10/51

ck_spre

Clock source

PREDIV_A[6:0]

PREDIV_S[14:0]

HSE_RTC = 1 MHz

124
(div 125)

7999
(div 8000)

1 Hz

LSE = 32.768 kHz

127
(div 128)

255
(div 256)

1 Hz

LSI = 32 kHz

127
(div 128)

249
(div 250)

1 Hz

LSI = 37 kHz

124
(div 125)

295
(div 296)

1 Hz

LSI = 40 kHz

127
(div 128)

311
(div 312)

1 Hz

DocID028310 Rev 2

AN4759

Overview of the STM32 MCU advanced RTC

1.2

RTC alarms

1.2.1

RTC alarm configuration

The RTC embeds two alarms, alarm A and alarm B, which are similar. An alarm can be
generated at a given time or/and date programmed by the user.
The RTC provides a rich combination of alarms settings, and offers many features to make
it easy to configure and display these alarms settings.
Each alarm unit provides the following features:

Fully programmable alarm: sub-second (this is discussed later), seconds, minutes,

hours and date fields can be independently selected or masked to provide a rich
combination of alarms.

Ability to exit the device from low power modes when the alarm occurs.

The alarm event can be routed to a specific output pin with configurable polarity.

Dedicated alarm flags and interrupt.

Figure 7. Alarm A fields

KRUK
IRUPDW

$ODUPGDWH
'D\RIZHHN

$0
30

'DWH

0DVN

KK

0DVN

57&B$/50$5

$ODUPWLPH
PP

0DVN

0DVN

VV

0DVNVV

57&B$/50$665
069

1. RTC_ALRMAR is an RTC register. The same fields are also available for the RTC_ALRMBR register.
2. RTC_ALRMASSR is an RTC register. The same field is also available for the RTC_ALRMBSSR register.
3. Maskx are the bits in the RTC_ALRMAR register that enable/disable the RTC_ALARM fields used for
alarm A. For more details, refer to Table 5.
4. Mask ss are the bits in the RTC_ALRMASSR register.

An alarm consists of a register with the same length as the RTC time counter. When the
RTC time counter reaches the value programmed in the alarm register, a flag is set to
indicate that an alarm event occurred.
The RTC alarm can be configured by hardware to generate different types of alarms. For
more details, refer to Table 5.

DocID028310 Rev 2

11/51
50

Overview of the STM32 MCU advanced RTC

AN4759

Programming the alarm

Table 4 describes the steps required to configure alarm A.
Table 4. Steps to configure the alarm
Step

What to do

How to do it

Comments

Write "0xCA" and then

Disable the RTC registers Write
"0x53" into the
protection
RTC_WPR register.

Disable alarm A

Clear ALRAE(1) bit in

RTC_CR register(2).

Check that the RTC_ALRMAR

register can be accessed

It takes around 2 RTCCLK

Poll ALRAWF(3) bit until
clock cycles due to clock
it is set in RTC_ISR.
synchronization.

Configure the alarm

Configure
RTC_ALRMAR(4)
register.

Re-enable alarm A

Set ALRAE(6) bit in

RTC_CR register.

Enable the RTC registers Write

protection

Write "0xFF" into the

RTC_WPR register.

RTC registers can be modified

The alarm hour format must be

the same(5) as the RTC
Calendar in RTC_ALRMAR.
RTC registers can no longer be
modified

1. Respectively ALRBE bit for alarm B.

2. RTC alarm registers can only be written when the corresponding RTC alarm is disabled or during RTC
Initialization mode.
3. Respectively ALRBWF bit for alarm B.
4. Respectively RTC_ALRMBR register for alarm B.
5. As an example, if the alarm is configured to occur at 3:00:00 PM, the alarm will not occur even if the
calendar time is 15:00:00, because the RTC calendar is 24-hour format and the alarm is 12-hour format.
6. Respectively ALRBE bit for alarm B.

Configuring the alarm behavior using the MSKx bits

The alarm behavior can be configured using the MSKx bits (x = 1, 2, 3, 4) of the
RTC_ALRMAR register for alarm A (RTC_ALRMBR register for alarm B).
Table 5 shows all the possible alarm settings. As an example, to configure the alarm time to
23:15:07 on monday (assuming that the WDSEL = 1), configure the RTC_ALRMAR register
(resp. RTC_ALRMBR register) with the MSKx bits set to 0000b. When the WDSEL = 0, all
the cases are similar, except that the Alarm Mask field compares with the day number and
not the day of the week, and MSKx bits must be set to 0000b.
Table 5. Alarm combinations
MSK3 MSK2 MSK1 MSK0

Alarm behavior

All the fields are used in the alarm comparison:

The alarm occurs at 23:15:07, each Monday.

The seconds do not matter in the alarm comparison

The alarm occurs every second of 23:15, each Monday.

The minutes do not matter in the alarm comparison

The alarm occurs at the 7th second of every minute of 23:XX, each Monday.

12/51

DocID028310 Rev 2

AN4759

Overview of the STM32 MCU advanced RTC

Table 5. Alarm combinations (continued)

MSK3 MSK2 MSK1 MSK0

Alarm behavior

The minutes and seconds do not matter in the alarm comparison

The hours do not matter in the alarm comparison

The hours and seconds do not matter in the alarm comparison

The hours and minutes do not matter in the alarm comparison

The hours, minutes and seconds do not matter in the alarm comparison
The alarm is set every second, each Monday, during the whole day.

The week day (or date, if selected) do not matter in the alarm comparison
The alarm occurs all the days at 23:15:07.

The week day and seconds do not matter in the alarm comparison

The week day and minutes do not matter in the alarm comparison

The week day, minutes and seconds do not matter in the alarm comparison

The week day and hours do not matter in the alarm comparison

The week day, hours and seconds do not matter in the alarm comparison

The week day, hours and minutes do not matter in the alarm comparison

The alarm occurs every second

Caution:

If the second field is selected (MSK0 bit reset in RTC_ALRMAR or RTC_ALRMBR), the
synchronous prescaler division factor PREDIV_S set in the RTC_PRER register must be at
least 3 to ensure a correct behavior.

1.2.2

Alarm sub-second configuration

The RTC unit provides programmable alarms, sub-second A and B, which are similar. They
generate alarms with a high resolution (for the second division).
The value programmed in the alarm sub-second register is compared to the content of the
sub-second field in the calendar unit.
The sub-second field counter counts down from the value configured in the synchronous
prescaler to zero, and then reloads a value from the RTC_SPRE register.
Figure 8. Alarm sub-second field

KRUK
IRUPDW
$0
30

7LPH
KK

PP

$ODUPVXEVHFRQG
V

VV

VV

0DVNVV

$ODUPIODJ
069

DocID028310 Rev 2

13/51
50

Overview of the STM32 MCU advanced RTC

Note:

AN4759

Mask ss is the most significant bit in the sub-second alarm. This bit is compared to the
synchronous prescaler register.
The alarm sub-second can be configured using the mask ss bit in the alarm sub-second
register. Table 6: Alarm sub-second mask combinations shows the configuration
possibilities for the mask register and provides an example with the following settings:

Select LSE as the RTC clock source (for example LSE = 32768 Hz).

Set the Asynchronous prescaler to 127.

Set the Synchronous prescaler to 255 (the calendar clock is equal to 1Hz).

Set the alarm A sub-second to 255 (put 255 in the SS[14:0] field).
Table 6. Alarm sub-second mask combinations

MASK SS

14/51

Alarm A sub-second behavior

Example result

There is no comparison on sub-second for alarm. The alarm is

activated when the second unit is incremented.

The alarm is activated every

1 second

Only the AlarmA_SS[0] bit is compared to the RTC sub-second

register RTC_SSR

The alarm is activated every

(1/128) s

Only the AlarmA_SS[1:0] bit is compared to the RTC sub-second

register RTC_SSR

The alarm is activated every

(1/64) s

Only the AlarmA_SS[2:0] bit is compared to the RTC sub-second

register RTC_SSR

The alarm is activated every

(1/32) s

Only the AlarmA_SS[3:0] bit is compared to the RTC sub-second

register RTC_SSR

The alarm is activated every

(1/16) s

Only the AlarmA_SS[4:0] bit is compared to the RTC sub-second

register RTC_SSR

The alarm is activated every

125 ms

Only the AlarmA_SS[5:0] bit is compared to the RTC sub-second

register RTC_SSR

The alarm is activated every

250 ms

Only the AlarmA_SS[6:0] bit is compared to the RTC sub-second

register RTC_SSR

The alarm is activated every

500 ms

Only the AlarmA_SS[7:0] bit is compared to the RTC sub-second

register RTC_SSR

The alarm is activated every 1 s

Only the AlarmA_SS[8:0] bit is compared to the RTC sub-second

register RTC_SSR

The alarm is activated every 1 s

10

Only the AlarmA_SS[9:0] bit is compared to the RTC sub-second

register RTC_SSR

The alarm is activated every 1 s

11

Only the AlarmA_SS[10:0] bit is compared to the RTC sub-second

The alarm is activated every 1 s
register RTC_SSR

12

Only the AlarmA_SS[11:0] bit is compared to the RTC sub-second

The alarm is activated every 1 s
register RTC_SSR

13

Only the AlarmA_SS[12:0] bit is compared to the RTC sub-second

The alarm is activated every 1 s
register RTC_SSR

14

Only the AlarmA_SS[13:0] bit is compared to the RTC sub-second

The alarm is activated every 1 s
register RTC_SSR

15

Only the AlarmA_SS[14:0] bit is compared to the RTC sub-second

The alarm is activated every 1 s
register RTC_SSR

DocID028310 Rev 2

AN4759

Overview of the STM32 MCU advanced RTC

Note:

The overflow bit in the sub-second register (bit15) is never compared.

1.3

RTC periodic wakeup unit

The STM32 MCUs provide several low-power modes to reduce the power consumption.
The RTC features a periodic timebase and wakeup unit able to wake up the system from
low-power modes. This unit is a programmable down-counting auto-reload timer. When this
counter reaches zero, a flag and an interrupt (if enabled) are generated.
The wakeup unit has the following features:

Programmable down-counting auto-reload timer.

1.3.1

Specific flag and interrupt capable of waking up the device from low-power modes.

Wakeup alternate function output which can be routed to RTC_ALARM output (unique
pad for alarm A, alarm B or Wakeup events) with configurable polarity.

A full set of prescalers to select the desired waiting period.

Programming the auto-wakeup unit

Table 7 describes the steps required to configure the Auto-wakeup unit.
Table 7. Steps to configure the auto-wakeup unit
Step

What to do

How to do it

Disable the RTC registers Write protection

Write "0xCA" and

then "0x53" into the
RTC_WPR register

Disable the wakeup timer.

Clear WUTE bit in

RTC_CR register

Ensure access to Wakeup auto-reload

Poll WUTWF until it
counter and bits WUCKSEL[2:0] is allowed. is set in RTC_ISR

Program the value into the wakeup timer.

Select the desired clock source.

Comments
RTC registers can be
modified

It takes around
2 RTCCLK clock cycles
due to clock
synchronization

Set WUT[15:0] in
RTC_WUTR register See Section 1.3.2:
Maximum and minimum
Program
WUCKSEL[2:0] bits RTC wakeup period
in RTC_CR register

Re-enable the wakeup timer.

Set WUTE bit in

RTC_CR register

Enable the RTC registers Write protection

Write "0xFF" into the RTC registers can no

RTC_WPR register
more be modified

DocID028310 Rev 2

The wakeup timer

restarts counting down

15/51
50

Overview of the STM32 MCU advanced RTC

1.3.2

AN4759

Maximum and minimum RTC wakeup period

The wakeup unit clock is configured through the WUCKSEL[2:0] bits of RTC_CR1 register.
Three different configurations are possible:

Configuration 1: WUCKSEL[2:0] = 0xxb for short wakeup periods

(see Periodic timebase/wakeup configuration for clock configuration 1)

Configuration 2: WUCKSEL[2:0] = 10xb for medium wakeup periods

(see Periodic timebase/wakeup configuration for clock configuration 2)

Configuration 3: WUCKSEL[2:0] = 11xb for long wakeup periods

(see Periodic timebase/wakeup configuration for clock configuration 3)

Periodic timebase/wakeup configuration for clock configuration 1

Figure 9 shows the prescaler connection to the timebase/wakeup unit and Table 8 gives the
timebase/wakeup clock resolutions corresponding to configuration 1.
The prescaler depends on the wakeup clock selection:

WUCKSEL[2:0] =000: RTCCLK/16 clock is selected

WUCKSEL[2:0] =001: RTCCLK/8 clock is selected

WUCKSEL[2:0] =010: RTCCLK/4 clock is selected

WUCKSEL[2:0] =011: RTCCLK/2 clock is selected

Figure 9. Prescalers connected to the timebase/wakeup unit for configuration 1
:8&.6(/>@

57&&/.

57&B:875

3UHVFDOHU

:8&.6(/>@

3HULRGLF
ZDNHXSIODJ

ELWZDNHXS
DXWRUHODRGWLPHU

06Y9

Table 8. Timebase/wakeup unit period resolution with clock configuration 1

Clock source
LSE = 32 768 Hz

Wakeup period resolution

WUCKSEL[2:0] = 000b (div16)

WUCKSEL[2:0] = 011b (div2)

488.28 s

61.035 s

When RTCCLK= 32768 Hz, the minimum timebase/wakeup resolution is 61.035 s, and the
maximum resolution is 488.28 s. As a result:

The minimum timebase/wakeup period is (0x0001 + 1) x 61.035 s = 122.07 s.

The timebase/wakeup timer counter WUT[15:0] cannot be set to 0x0000 with
WUCKSEL[2:0]=011b (fRTCCLK/2) because this configuration is prohibited. Refer to the
STM32Lx reference manuals for more details.

16/51

The maximum timebase/wakeup period is (0xFFFF+ 1) x 488.28 s = 32 s.

DocID028310 Rev 2

AN4759

Overview of the STM32 MCU advanced RTC

Periodic timebase/wakeup configuration for clock configuration 2

Figure 10 shows the prescaler connection to the timebase/wakeup unit corresponding to
configuration 2 and 3.
Figure 10. Prescalers connected to the wakeup unit for configurations 2 and 3

57&&ORFN

$V\QFKURQRXV
SUHVFDOHU
35(',9B$

6\QFKURQRXV
SUHVFDOHU
35(',9B6

$V\QFKELWSUHVFDOHU
GHIDXOW 

6\QFKURQRXVELW
3UHVFDOHUGHIDXOW 

:8&.6(/>@

:DNHXS
DXWRUHORDG
WLPHU
57&B:875

3HULRGLF
ZDNHXSIODJ

ELWZDNHXSDXWR
UHORDGWLPHU
06Y9

If ck_spre (synchronous prescaler output clock) is adjusted to 1 Hz, then:

The minimum timebase/wakeup period is (0x0000 + 1) x 1 s = 1 s.

The maximum timebase/wakeup period is (0xFFFF+ 1) x 1 s = 65536 s (18 hours).

Periodic timebase/wakeup configuration for clock configuration 3

For this configuration, the resolution is the same as for configuration 2. However, the
timebase/wakeup counter downcounts starting from 0x1FFFF to 0x00000, instead of
0xFFFF to 0x0000 for configuration 2.
If ck_spre is adjusted to 1 Hz, then:

The minimum timebase/wakeup period is:

(0x10000 + 1) x 1 s = 65537 s (18 hours + 1 s)

The maximum timebase/wakeup period is:

(0x1FFFF+ 1) x 1 s = 131072 s (36 hours).

Summary of timebase/wakeup period extrema

When RTCCLK= 32768 Hz and ck_spre (Synchronous prescaler output clock) is adjusted to
1 Hz, the minimum and maximum period values are listed in Table 9.
Table 9. Min. and max. timebase/wakeup period when RTCCLK= 32768
Configuration

Minimum period

Maximum period

122.07 s

32 s

1s

18 hours

18 hours +1 s

36 hours

DocID028310 Rev 2

17/51
50

Overview of the STM32 MCU advanced RTC

1.4

Digital smooth calibration

1.4.1

RTC calibration basics

AN4759

The term quartz-accurate has become a familiar phrase used to describe the accuracy of
many time keeping functions. The quartz oscillators provide an accuracy far superior to that
of other conventional oscillator designs, but they are not perfect. The quartz crystals are
sensitive to temperature variations. Figure 11 shows the relationship between accuracy
(acc), temperature (T) and curvature (K) for a typical 32.768 kHz crystal. The curve follows
the general formula given below:
acc = K x (T-To), where:

Note:

To = 25 C 5 C

K = 0.032 ppm/C2

The variable K is crystal-dependent, the value indicated here is for the crystal mounted on
the STM32L476RG-Nucleo board. Refer to the crystal manufacturer for more details on this
parameter.
The clocks used in most applications require a high degree of accuracy, and there are
several factors involved in achieving this accuracy. Typically most crystals are compensated
for by adjusting the load capacitance of the oscillator. This method, though effective, has
several disadvantages:
1.

It requires external components (trim capacitors)

2.

It can increase the oscillator current (a major factor in battery-supported applications)

Instead of this crude analog method, the STM32 products use a digital calibration feature
that gives the user software control over the calibration procedure, and makes it userfriendly.
Figure 11. Typical crystal accuracy plotted against temperature




n

n




n
n

4EMPERATURE#
















n
n
n
!CCURACYPPM
n
AIB

18/51

DocID028310 Rev 2

AN4759

1.4.2

Overview of the STM32 MCU advanced RTC

Methodology
The RTC clock frequency can be corrected using a series of small adjustments by adding or
subtracting individual RTCCLK pulses.The RTC clock can be calibrated with a resolution of
about 0.954 ppm with a range from -487.1 ppm to +488.5 ppm.
This digital smooth calibration is designed to compensate for the inaccuracy of crystal
oscillators due to the temperature, crystal aging.
Figure 12. Smooth calibration block
+]

57&B&$/,%

57&
&ORFN

6PRRWK
FDOLEUDWLRQ

+]

$V\QFKURQRXV
SUHVFDOHU

6\QFKURQRXV
SUHVFDOHU

&DOHQGDU
&NB6SUH

$V\QFKELWSUHVFDOHU
GHIDXOW 

6\QFKURQRXVELW
SUHVFDOHUGHIDXOW 

6KDGRZUHJLVWHUV
57&B7557&B'5

06Y9

The user can compute the clock deviation using the RTC_CALIB signal, then update the
calibration block. It is also possible to input an external 1 Hz reference and make the
adequate processing inside the MCU to correct the RTC clock. The user finds such example
in Section 5.3: Application example project.
It is possible to check the calibration result using the calibration output 512 Hz or 1 Hz for
the RTC_CALIB signal. Refer to Table 14: Advanced RTC features.
A smooth calibration consists of masking and adding N (configurable) 32 kHz pulses that
are well distributed in a configurable window (8 s, 16 s or 32 s).
The number of masked or added pulses is defined using CALP and CALM in the
RTC_CALR register.
By default, the calibration window is 32 seconds. It can be reduced to 8 or 16 seconds by
setting the CALW8 bit or the CALW16 bit in the RTC_CALR register:
Example 1: setting CALM[0] to 1, CALP=0 and using 32 seconds as a calibration window
results in exactly one pulse being masked for 32 seconds.
Example 2: setting CALM[2] to 1, CALP=0 and using 32 seconds as a calibration window
results in exactly 4 pulses being masked for 32 seconds.
Note:

Both the CALM and CALP can be used and, in this case, an offset ranging from -511 to
+512 pulses can be added for 32 seconds (calibration window).
When the asynchronous prescaler is less than 3, CALP cannot be set to 1.
The formula to calculate the effective calibrated frequency (FCAL), given the input
frequency (FRTCCLK), is:
FCAL = FRTCCLK x [1 + (CALP x 512 - CALM) / (220 + CALM - CALP x 512)].

DocID028310 Rev 2

19/51
50

Overview of the STM32 MCU advanced RTC

AN4759

A smooth calibration can be performed on the fly so that it can be changed when the
temperature changes or if other factors are detected.

Checking the smooth calibration

The smooth calibration effect on the calendar clock (RTC Clock) can be checked by:

1.5

Calibration using the RTC_CALIB output (512 Hz or 1 Hz).

Calibration using the sub-second alarms.

Calibration using the wakeup timer.

Synchronizing the RTC

The RTC calendar can be synchronized to a more precise clock, remote clock, using the
RTC shift feature. After reading the RTC sub-second field, a calculation of the precise offset
between the time being maintained by the remote clock and the RTC can be made. The
RTC can be adjusted by removing this offset with a fine adjustment using the shift register
control.
Figure 13. RTC shift register
+]

57&B&$/,%
+]

6KLIW
57&B6+,)7(5
GHOD\

57&&ORFN

DGYDQFH

6\QFKURQRXV
SUHVFDOHU

$V\QFKURQRXV
SUHVFDOHU

&DOHQGDU
&NB6SUH

6\QFKURQRXVELW
SUHVFDOHUGHIDXOW 

$V\QFKELWSUHVFDOHU
GHIDXOW 

6KDGRZUHJLVWHUV
57&B7557&B'5

06Y9

It is not possible to check the Synchronization shift function using the RTC_CALIB output
since the shift operation has no impact on the RTC clock, other than adding or subtracting a
few fractions from the calendar counter.
Correcting the RTC calendar time
If the RTC clock is advanced compared to the remote clock by n fractions of seconds, the
offset value must be written in SUBFS, which will be added to the synchronous prescalers
counter. As this counter counts down, this operation effectively subtracts from (delays) the
clock by:
Delay (seconds) = SUBFS / (PREDIV_S + 1)
If the RTC is delayed compared to the remote clock by n fractions of seconds, the offset
value can effectively be added to the clock (advancing the clock) when the ADD1S function
is used in conjunction with SUBFS, effectively advancing the clock by:
Advance (seconds) = (1 - (SUBFS / (PREDIV_S + 1))).

20/51

DocID028310 Rev 2

AN4759

1.6

Overview of the STM32 MCU advanced RTC

RTC reference clock detection

The reference clock (at 50 Hz or 60 Hz) should have a higher precision than the 32.768 kHz
LSE clock. This is why the RTC provides a reference clock input (RTC_REFIN pin) that can
be used to compensate the imprecision of the calendar frequency (1 Hz).
The RTC_REFIN pin should be configured in input floating mode.
This mechanism enables the calendar to be as precise as the reference clock.
The reference clock detection is enabled by setting the REFCKON bit of the RTC_CR
register.
When the reference clock detection is enabled, PREDIV_A and PREDIV_S must be set to
their default values: PREDIV_A = 0x007F and PREDIV_S = 0x00FF.
When the reference clock detection is enabled, each 1 Hz clock edge is compared to the
nearest reference clock edge (if one is found within a given time window). In most cases, the
two clock edges are properly aligned. When the 1 Hz clock becomes misaligned due to the
imprecision of the LSE clock, the RTC shifts the 1 Hz clock a bit so that future 1 Hz clock
edges are aligned. The update window is 3 ck_apre periods.
If the reference clock halts, the calendar is updated continuously based solely on the LSE
clock. The RTC then waits for the reference clock using a detection window centered on the
Synchronous Prescaler output clock (ck_spre) edge. The detection window is 7 ck_apre
periods.
The reference clock can have a large local deviation (for instance in the range of 500 ppm),
but in the long term it must be much more precise than 32 kHz quartz.
The detection system is used only when the reference clock needs to be detected back after
a loss. As the detection window is a bit larger than the reference clock period, this detection
system brings an uncertainty of 1 ck_ref period (20 ms for a 50 Hz reference clock) because
it is possible to have 2 ck_ref edges in the detection window. Then the update window is
used, which brings no error as it is smaller than the reference clock period.
Assuming that ck_ref is not lost more than once a day. So the total uncertainty per month
would be 20 ms *1* 30 = 0.6 s, which is much less than the uncertainty of a typical quartz
(1.53 minute per month for 35 ppm quartz).
Figure 14. RTC reference clock detection

&DOHQGDU
&.B6SUH
6KDGRZUHJLVWHUV
57&B75
57&B'5

$XWRGHWHFWLRQ
RIRU+]

57&B5(),1

9ROWDJH
$GDSWRU9
WR9RU9
06Y9

DocID028310 Rev 2

21/51
50

Overview of the STM32 MCU advanced RTC

Note:

AN4759

The reference clock calibration and the RTC synchronization (shift feature) cannot be used
together.
The reference clock calibration is the best (ensures a high calibrated time) if the 50 Hz is
always available. If the 50 Hz input is lost, the RTC accuracy is provided by the LSE crystal.
The reference clock detection cannot be used in Vbat mode.
The reference clock calibration can only be used if the user provides a precise 50 or 60 Hz
input.

1.7

Time-stamp function
The Time-stamp feature provides the means to automatically save the current calendar.
Figure 15. Time-stamp event procedure

'$7(
57&B'5
'DWH

:HHN
GDWH

7,0(
57&B75

KRUK
IRUPDW
$0
30

0RQWK

KK

PP

6XEVHFRQG
57&B665
V

VV

&DOHQGDU8QLW
&RS\
57&B7675 57&B75
57&B76'5 57&B'5
57&B76665 57&B665

2Q7LPH6WDPS
HYHQW
'$7(
57&B76'5
'DWH

:HHN
GDWH

0RQWK

6XEVHFRQG
57&B76665

7,0(
57&B7675
<HDU

$0
30

KK

PP

VV

069

Provided that the time-stamp function is enabled, the calendar is saved in the time-stamp
registers (RTC_TSTR, RTC_TSDR, RTC_TSSSR) when an internal or external time-stamp
event is detected. When a time-stamp event occurs, the time-stamp flag bit (TSF) in the
RTC_ISR register is set.
The events that can generate a timestamp are:

22/51

An edge detection on the RTC_TS I/O

A tamper event detection (from all RTC_TAMP I/Os)

A switch to VBAT when the main supply if powered off (STM32L4x devices only)

DocID028310 Rev 2

AN4759

Overview of the STM32 MCU advanced RTC

Table 10. Time-stamp features
What to do
Enable Time-stamp

How to do it

Comments

Setting the TSE or ITSE bit

ITSE is only available on L4
of RTC_CR register to 1

Detect a time-stamp event by Setting the TSIE bit in the

interrupt
RTC_CR register

An interrupt is generated when a timestamp event occurs.

By polling on the timeDetect a time-stamp event by stamp flags (TSF or

polling
ITSF(1)) in the RTC_ISR
register

To clear the flag, write zero on the TSF

bit or ITSF.(2)

Detect a Time-stamp
overflow event(3)

To clear the flag, write zero in the

TSOVF bit.
Time-stamp registers (RTC_TSTR
By checking on the timeand RTC_TSDR, RTC_TSSSR)
stamp over flow flag
maintain the results of the previous
(TSOVF(4)) in the RTC_ISR
event.
register.
If a time-stamp event occurs
immediately after the TSF bit is
supposed to be cleared, then both
TSF and TSOVF bits are set.

1. TSF is set 2 ck_apre cycles after the time-stamp event occurs due to the synchronization process.
2. To avoid masking a time-stamp event occurring at the same moment, the application must not write 0 into
TSF bit unless it has already read it to1.
3. The time-stamp overflow event is not connected to an interrupt.
4. There is no delay in the setting of TSOVF. This means that if two time-stamp events are close to each
other, TSOVF can be seen as '1' while TSF is still '0'. As a consequence, it is recommended to poll TSOVF
only after TSF has been set.

1.8

RTC tamper detection function

The RTC includes up to 3 tamper detection inputs. The tamper input active level/edge can
be configured and each one has an individual flag (TAMPxF bit in RTC_ISR register).
A tamper detection event generates an interrupt when the TAMPIE or TAMPxIE bit in
RTC_TAMPCR register is set.
The configuration of the tamper filter, TAMPFLT bits, defines whether the tamper detection
is activated on edge (set TAMPFLT to 00), or on level (TAMPFLT must be different from
00).

Note:

The number of tamper inputs depends on product packages. Each input has a TAMPxF
individual flag in the RTC_TAMP register.

DocID028310 Rev 2

23/51
50

Overview of the STM32 MCU advanced RTC

1.8.1

AN4759

Edge detection on tamper input

When the TAMPFLT bits are set to zero, the tamper input detection triggers when a rising
edge or a falling edge (depending on the TAMPxTRG bit) is observed on the corresponding
RTC_TAMPx input pin.
Figure 16. Tamper with edge detection
(GJHGHWHFWLRQ
9''
RU
2SWLRQDO
UHVLVWRU

5[
57&B7$03[

7DPSHU[

&[

VZLWFK

2SWLRQDO
FDSDFLWRU

670/

06Y9

1. If the power consumption is not a concern, the internal 40 k pull-up resistor can be used.

Note:

With the edge detection, the sampling and precharge features are deactivated.
Table 11. Tamper features (edge detection)
What to do

1.8.2

How to do it

Comments

Enable Tamper

Set the TAMPxE bit of

RTC_TAMPCR register to 1

Select Tamper active edge

detection

Select with TAMPxTRG bit

in RTC_TAMPCR register

The default edge is rising edge.

Detect a Tamper event by

interrupt

Set the TAMPIE or

TAMPxIE bit in the
RTC_TAMPCR register

An interrupt is generated when a tamper

detection event occurs.

Detect a Tamper event by

polling

Poll the time-stamp flag

(TAMPxF) in the RTC_ISR
register

To clear the flag, write zero in the

TAMPxF bit.

Level detection on tamper input

Setting the tamper filter TAMPFLT to a value other than zero means that the tamper input
triggers when a selected level (high or low) is observed on the corresponding RTC_TAMPx
input pin.
A tamper detection event is generated when either 2, 4 or 8 (depending on the TAMPFLT
value) consecutive samples are observed at the selected level.

24/51

DocID028310 Rev 2

AN4759

Overview of the STM32 MCU advanced RTC

Figure 17. Tamper with level detection

/HYHOGHWHFWLRQ
;
;

57&B7$03[
7DPSHU[
VZLWFK

&[
2SWLRQDO
&DSDFLWRU

670/

06Y9

Using the level detection (tamper filter set to a non-zero value), the tamper input pin can be
precharged by resetting TAMPPUDIS through an internal resistance before sampling its
state. In order to support the different capacitance values, the length of the pulse during
which the internal pull-up is applied can be 1, 2, 4 or 8 RTCCLK cycles.
Figure 18. Tamper sampling with precharge pulse
57&FORFN

VDPSOLQJ
)ORDWLQJLQSXW

6ZLWFKRSHQHG
3UHFKDUJH 57&&/.
3UHFKDUJH 57&&/.
3UHFKDUJH 57&&/.
3UHFKDUJH 57&&/.QRWVKRZQ
06Y9

Note:

When the internal pull-up is not applied, the I/Os Schmitt triggers are disabled in order to
avoid an extra consumption if the tamper switch is open.
The trade-off between the tamper detection latency and the power consumption through the
weak pull-up or external pull-down can be reduced by using a tamper sampling frequency
feature. The tamper sampling frequency is determined by configuring the TAMPFREQ bits
in the RTC_TAMPCR register. When using the LSE at 32768 Hz as the RTC clock source,
the sampling frequency can be 1, 2, 4, 8, 16, 32, 64, or 128 Hz.

DocID028310 Rev 2

25/51
50

Overview of the STM32 MCU advanced RTC

AN4759

Table 12. Tamper features (level detection)

What to do

1.8.3

How to do it

Comments

Enable Tamper

Set the TAMPxE bit of

RTC_TAMPCR register to 1

Configure Tamper filter count

Configure TAMPFLT bits in

RTC_TAMPCR register

Configure Tamper sampling

frequency

Configure TAMPFREQ bits Default value is 1Hz

in RTC_TAMPCR register

Configure tamper internal

pull-up and precharge
duration

Configure TAMPPUDIS
and TAMPPPRCH bits in
RTC_TAMPCR register

Select Tamper active

edge/Level detection

Select with TAMPxTRG bit

in RTC_TAMPCR register

Edge or Level is depending on tamper

filter configuration.

Detect a Tamper event by

interrupt

Set the TAMPIE or

TAMPxIE bit in the
RTC_TAMPCR register

An interrupt is generated when tamper

detection event occurs.

Detect a Tamper event by

polling

Poll the time-stamp flag

(TAMPxF) in the RTC_ISR
register

To clear the flag, write zero in the

TAMPxF bit.

Timestamp on tamper detection event

By setting the TAMPTS bit to 1, any tamper event (with edge or level detection) causes a
timestamp to occur. Consequently, the timestamp flag and timestamp overflow flag are set
when the tamper flag is set and work in the same manner as when a normal timestamp
event occurs.

Note:

It is not necessary to enable or disable the timestamp function when using this feature.

1.9

Backup registers
The 32-bit backup registers (RTC_BKPxR) are reset when a tamper detection event occurs.
These registers are powered-on by VBAT when VDD is switched off (except for STM32L0
Series and STM32L1 Series), they are not reset by a system reset, and their contents
remain valid when the device operates in low-power mode.
For STM32L0 Series, STM32L4 Series and STM32F7 Series, the 32-bit backup registers
(RTC_BKPxR) are not reset if the TAMPxNOERASE bit is set, or if TAMPxMF (Tamper
Mask Flag) is set in the RTC_TAMPCR register. Disabling the backup register reset feature
allows to trigger a LPTIM event from the tamper pin without erasing the backup
registers.This also allows to take benefit of the tamper input digital filtering, either to
generate triggers or to generate interrupts.

Note:

26/51

The VBAT availability and the LPTIM availability depend on the number of backup registers
depends on the product. Please refer to Table 14: Advanced RTC features.

DocID028310 Rev 2

AN4759

1.10

Overview of the STM32 MCU advanced RTC

Alternate function RTC outputs

The RTC peripheral has two outputs:

1.10.1

RTC_CALIB, used to generate an external clock.

RTC_ALARM, a unique output resulting from the multiplexing of the RTC alarm and
wakeup events.

RTC_CALIB output
The RTC_CALIB output can be used to generate a 1 Hz or 512 Hz signal and used to
measure the deviation of the RTC clock when compared to a more precise clock.

Setting 512 Hz as the output signal

1.

Select LSE at 32768 Hz as RTC clock source.

2.

Set the asynchronous prescaler to the default value 128.

3.

Enable the output calibration by setting COE to 1.

4.

Select 512 Hz as the calibration output by setting COSEL to 0.

Setting 1 Hz as the output signal

1.

Select LSE at 32768 Hz as the RTC clock source.

2.

Set the asynchronous prescaler to the default value 128.

3.

Set the synchronous prescaler to the default value 256.

4.

Enable the output calibration by setting COE to 1.

5.

Select 1 Hz as the calibration output by setting COSEL to 1.

Figure 19. RTC_CALIB clock sources
+]

57&B&$/,%
+]
&26(/

57&&ORFN

$V\QFKURQRXV
SUHVFDOHU

$V\QFKURQRXVELW
SUHVFDOHUGHIDXOW 

6\QFKURQRXV
SUHVFDOHU
6\QFKURQRXVELW &NB6SUH
SUHVFDOHUGHIDXOW 

&DOHQGDU
6KDGRZUHJLVWHUV
57&B75DQG
57&B'5

06Y9

DocID028310 Rev 2

27/51
50

Overview of the STM32 MCU advanced RTC

AN4759

Maximum and minimum RTC_CALIB 512 Hz output frequency

The RTC_CALIB output can also be used to generate a variable-frequency signal.
Depending on the user application, this signal can play the role of a source clock for an
external device, or be connected to a buzzer to generate sound.
The signal frequency is configured using the 6 LSB bits (PREDIV_A [5:0]) of the
asynchronous prescaler PREDIV_A[6:0].
Table 13. RTC_CALIB output frequency versus clock source
RTC_CALIB output frequency
Minimum
(PREDIV_A[5:0] = 111 111b)

Maximum
(PREDIV_A[5:0] = 100 000b(1))

(div64)

(div32)

HSE_RTC = 1 MHz

15,625 kHz

30.303 kHz

LSE = 32768 Hz

512 Hz
(default output frequency)

993 Hz

LSI = 32 kHz

500 Hz

969 Hz

LSI = 37 kHz

578 Hz

1.121 kHz

LSI = 40 kHz

625 Hz

1.212 kHz

RTC clock source

1.

1.10.2

PREDIV_A[5] must be set to 1 to enable the RTC_CALIB output signal generation. If PREDIV_A[5] bit is zero, no signal
is output on RTC_CALIB.

RTC_ALARM output
The RTC_ALARM output can be connected to the RTC alarm unit A or B to trigger an
external action, or connected to the RTC wakeup unit to wake up an external device.

RTC_ALARM output connected to an RTC alarm unit

When the calendar reaches the alarm A pre-programmed value in the RTC_ALRMAR
register (TC_ALRMBR register for alarm B), the alarm flag ALRAF bit (ALRBF bit), in the
RTC_ISR register, is set to 1. If the alarm A or alarm B flag is routed to the RTC_ALARM
output (RTC_CR_OSEL[1:0] =01 for alarm A, and RTC_CR_OSEL[1:0] =10 for alarm B),
this pin is set to VDD or to GND, depending on the polarity selected. The output toggles
when the selected alarm flag is cleared.

28/51

DocID028310 Rev 2

AN4759

Overview of the STM32 MCU advanced RTC

Figure 20. Alarm flag routed to RTC_ALARM output
$ODUP$

VVPP++GDWH
$ODUP$
IODJ
&DOHQGDU

57&B$/$50
RXWSXW
'D\GDWHPRQWK
\HDU

26(/>@

KKPPVV
IRUPDW

$ODUP%
IODJ

$ODUP%

VVPP++GDWH
06Y9

RTC_ALARM output connected to the wakeup unit

When the wakeup downcounting timer reaches 0, the wakeup flag is set to 1. If this flag is
selected as the source for the RTC_ALARM output (OSEL[1:0] bits set to 11 in RTC_CR
register), the output will be set depending on the polarity selected and will remain set as
long as the flag is not cleared.
Figure 21. Periodic wakeup routed to RTC_ALARM pinout
26(/>@ 

57&B$/$50
RXWSXW
:DNHXSXQLW
ELWDXWRUHORDG
WLPHU

3HULRGLF
ZDNHXSIODJ

06Y9

DocID028310 Rev 2

29/51
50

Overview of the STM32 MCU advanced RTC

1.11

RTC security aspects

1.11.1

RTC register write protection

AN4759

To protect the RTC registers against possible parasitic write accesses after reset, the RTC
registers are automatically locked. They must be unlocked to update the current calendar
time and date.
Writing to the RTC registers is enabled by programming a key in the Write protection
register (RTC_WPR).
The following steps are required to unlock the write protection of the RTC register:
1.
2.

Write 0xCA into the RTC_WPR register.

Write 0x53 into the RTC_WPR register.

Writing an incorrect key automatically reactivates the RTC register write access protection.

1.11.2

Enter/exit initialization mode

The RTC can operate in two modes:

Initialization mode, where the counters are stopped.

Free-running mode, where the counters are running.

The calendar cannot be updated while the counters are running. The RTC must
consequently be switched to the Initialization mode before updating the time and date.
When operating in this mode, the counters are stopped. They start counting from the new
value when the RTC enters the Free-running mode.
The INIT bit of the RTC_ISR register enables the user to switch from one mode to another,
and the INITF bit can be used to check the RTC current mode.
The RTC must be in Initialization mode to program the time and date registers (RTC_TR
and RTC_DR) and the prescalers register (RTC_PRER). This is done by setting the INIT bit
and waiting until the RTC_ISR_INITF flag is set.
To return to the Free-running mode and restart counting, the RTC must exit the Initialization
mode. This is done by resetting the INIT bit.
Only a power-on reset can reset the calendar. A system reset does not affect it but resets
the shadow registers that are read by the application. They are updated again when the
RSF bit is set. After a system reset, the application can check the INITS status flag in the
RTC_ISR register to verify if the calendar is already initialized. This flag is reset when the
calendar year field is set to 0x00 (power-on reset value), meaning that the calendar must be
initialized.

1.11.3

RTC clock synchronization

When the application reads the calendar, it accesses shadow registers that contain a copy
of the real calendar time and date clocked by the RTC clock (RTCCLK). The RSF bit is set
in the RTC_ISR register each time the calendar time and date shadow registers are updated
with the real calendar value. The copy is performed every two RTCCLK cycles,
synchronized with the system clock (SYSCLK). After a system reset or after exiting the
initialization mode, the application must wait for the RSF bit to be set before reading the
calendar shadow registers.

30/51

DocID028310 Rev 2

AN4759

Overview of the STM32 MCU advanced RTC

When the system is woken up from low-power modes (SYSCLK was off), the application
must first clear the RSF bit, and then wait until it is set again before reading the calendar
registers. This ensures that the value read by the application is the current calendar value,
and not the value before entering the low-power mode.
By setting the BYPSHAD bit to 1 in the RTC_CR register, the calendar values are taken
directly from the calendar counters instead of reading the shadow register. In this case, it is
not mandatory to wait for the synchronization time, but the calendar registers consistency
must be checked by the software. The user must read the required calendar field values.
The read operation must then be performed again. The results of the two read sequences
are then compared. If the results match, the read result is correct. If they do not match, the
fields must be read one more time, and the third read result is valid.

Note:

After resetting the BYPSHAD bit, the shadow registers may be incorrect until the next
synchronization. In this case, the software should clear the RSF bit then wait for the
synchronization (RSF should be set) and finally read the shadow registers.

DocID028310 Rev 2

31/51
50

Advanced RTC features

Table 14. Advanced RTC features
RTC features

STM32L0
Series

STM32L1
STM32L1
Cat.
Cat. 1
2/3/4/5/6

STM32L4
Series

STM32F0
Series

STM32F2
Series

STM32F3 STM32F4
Series
Series

STM32F7
Series

RTC clock source (LSE, LSI, HSE with

prescaler)

Asynchronous

X (7 bits)

X (7 bits)

X (7 bits)

X (7 bits)

X (7 bits)

X (7 bits)

X (7 bits)

X (7 bits)

X (7 bits)

Synchronous

X (15 bits)

X (15 bits) X (13 bits)

X (1 5
bits)

X (15 bits)

X (13 bits) X (15 bits) X (15 bits)

X (15 bits)

Prescalers

DocID028310 Rev 2

12/24 format

Hour, minutes
and seconds

Sub-second

Not
available

Not
available

Date

Daylight operation

Bypass the shadow registers

Not
available

Not
available

Not
available

Not
available

Not
available

Time

Calendar

VBAT mode

Advanced RTC features

32/51

AN4759

RTC features

STM32L1
STM32L1
Cat.
Cat. 1
2/3/4/5/6

STM32L4
Series

STM32F0
Series

STM32F2
Series

STM32F3 STM32F4
Series
Series

STM32F7
Series

Alarm B

Not
available

12/24 format

Hour, minutes
and seconds

Sub-second

Not
available

Not
available

Date or week day

Configurable input mapping

Not
available

Not
available

Configurable edge detection

Configurable Level detection

(filtering, sampling and
precharge configuration on
tamper input)

Not
available

Not
available

2 inputs /
1 event

2 inputs /
2 events

2 inputs /
2 events

3 inputs/
3 events

1 input

1 input

2 inputs

2 inputs

Alarm
Time

DocID028310 Rev 2

Number of tamper inputs

3 inputs /
3 events

3 inputs /
3 events

1 input /
1 event

3 inputs /
3 events

2 inputs
3 inputs (for
STM32F07x
and
STM32F09x)

VBAT mode pins

Not
available

Not
available

Not
available

3 inputs

1 input

33/51

Advanced RTC features

Alarm A

Alarms
available

Tamper
detection

STM32L0
Series

AN4759

Table 14. Advanced RTC features (continued)

RTC features

STM32L0
Series

STM32L1
STM32L1
Cat.
Cat. 1
2/3/4/5/6

STM32L4
Series

STM32F0
Series

STM32F2
Series

STM32F3 STM32F4
Series
Series

STM32F7
Series

X(1)

Not
available

Not
available

X(1)

Hours, minutes
and seconds

Sub-seconds

Not
available

Not
available

Date (Day, Month)

Time Stamp on tamper

detection event

Not
available

Not
available

Not
available

Not
available

Not
available

Not
available

Not
available

Alarm event

Wakeup event

512 Hz

1 Hz

Not
available

Not
available

Coarse Calibration

Not
available(2)

Not
available(2)

Not
available(2)

Not
available(2)

Not
available(2)

Smooth Calibration

Not
available

Not
available

Synchronizing the RTC

Not
available

Not
available

Reference clock detection

Configurable input mapping

Time
Time
Stamp

DocID028310 Rev 2

Time Stamp on switch to

VBAT mode
RTC_
ALARM
RTC
Outputs

RTC
Calibration

RTC_
CALIB

Advanced RTC features

34/51

Table 14. Advanced RTC features (continued)

AN4759

Backup
registers

RTC features

STM32L0
Series

STM32L1
STM32L1
Cat.
Cat. 1
2/3/4/5/6

Powered-on VBAT

Not
available

Not
available

Reset on a tamper detection

Reset when Flash readout

protection is disabled
Number of backup registers

STM32L4
Series

STM32F0
Series

STM32F2
Series

STM32F3 STM32F4
Series
Series

STM32F7
Series

Not
available

Not
available

Not
available

32(3)

20(4)

32

20

16

20

32

AN4759

Table 14. Advanced RTC features (continued)

1. Thanks to timestamp on tamper event.

2. Obsolete, replaced by smooth calibration.
3. Cat. 3/4/5/6.

DocID028310 Rev 2

4. Cat. 1 and Cat. 2.

Advanced RTC features

35/51

Reducing power consumption

AN4759

Reducing power consumption

The RTC is designed to minimize the power consumption: the Real-Time Clock functionality
only adds typically 300nA to the current consumption.
The RTC keeps working in reset mode and its registers are only reset by a VDD or VBAT
power-on, if both supplies have previously been powered off. As the RTC register values
are not lost after a system reset, the calendar keeps the correct time and date until VDD and
VBAT power down.

Note:

In the STM32L0 Series and STM32L1 Series, the VBAT mode is not available.

3.1

Using the right power reduction mode

Depending on the application constraints, such as the maximum or average current
consumption, the frequency of wake-ups, or alternatively the maximum wake-up time,
several low-power modes can be used.
The RTC peripheral can be active in the following low-power modes:

3.2

Sleep mode

Low-power Run mode

Low-power Sleep mode

Stop mode if the RTC clock is provided by LSE or LSI(a)

Standby mode if the RTC clock is provided by LSE or LSI

Shutdown mode if the RTC clock is provided by LSE(b)

Use tamper pin internal pull-up resistor

For all STM32 MCUs (except STM32L1 Cat 1. and STM32F2 Series), the internal pull-up
resistor in the Tamper Input pad is only applied for a short period of time (1, 2, 4 or 8
RTCCLK cycles) so using the RTC internal pull-up resistor instead of standard IO pullup/pull-down or external pull-up/pull-down ensures the lowest power consumption.
The trade-off between the tamper detection latency and the power consumption by the RTC
internal pull-up can be optimized using TAMPFREQ field. It determines the frequency of the
tamper sampling from 128 Hz to 1 Hz when RTCCLK equals 32768 Hz.

3.3

Setting the RTC prescalers

The prescalers used for the calendar are divided into a asynchronous and a synchronous
prescalers. Increasing the value of the asynchronous prescaler (and reducing the
synchronous prescaler accordingly to keep the 1 Hz output) reduces the RTC power
consumption.

a. In the STM32L4 Series, there are 3 Stop modes. In order to select the most relevant mode, please refer to [11]
and [12] for the other series.
b. Only for the STM32L4 Series.

36/51

DocID028310 Rev 2

AN4759

STM32L4 API and tampering detection application example

STM32L4 API and tampering detection application

example

4.1

STM32 Cube firmware libraries

The Real-Time Clock peripheral comes with:

4.2

A firmware driver API abstracting the RTC features for the end-user. Refer to
stm32l4xx_hal_rtc.c and stm32l4xx_hal_rtc_ex.c files in
\STM32Cube_FW_L4_Vx.y.z\Drivers\STM32L4xx_HAL_Driver\

A set of example projects so that the user can quickly become familiar with the RTC
peripheral. Refer to the examples in
\STM32Cube_FW_L4_Vx.y.z\Projects\STM32L476RG-Eval\Examples\RTC

STM32 Cube expansion firmware

This application note comes with the X-CUBE-RTC expansion software upon the STM32
Cube firmware libraries.
It shows a concrete example where a real-time clock must be maintained alive while using
as less power as possible. The firmware implements:

A few hints order to ensure a low current consumption,

A display in the debugger (date and time, timestamp date and time) and on LEDs
(power up events, reset events, tamper events, error)

A display on the TFT screen, using STemWin library

The tampering detection capability both when the main power supply (VDD) is
present and when the RTC is battery powered,

The ability to timestamp the tampering event,

The ability to erase the backup registers that may contain sensitive data upon
tamper detection.

The application flowchart is shown in Figure 22

DocID028310 Rev 2

37/51
50

STM32L4 API and tampering detection application example

AN4759

Figure 22. Application example flowchart

,QLWLDOL]DWLRQ

&RQILJXUH57&
&ORFNDQG
SUHVFDOHUV

7DPSHU,QWHUUXSW
+DQGOHU

*UHHQ/('RQ
/('

7DPSHU
'HWHFWLRQGXULQJ
3RZHUGRZQ"

<HV

*UHHQ/('RQ
/('

1R
5LVHIODJIRUPDLQ
3URJUDP

&RQILJXUH7DPSHU
'HWHFWLRQRQ3$

5HWXUQWRPDLQ
SURJUDP

%DFN8S
5HJLVWHUV
(UDVHG"

<HV

:ULWHEDFNXS
UHJLVWHU

1R

3RZHU
2Q5HVHW
2FFXUUHG"

3RZHU
2Q5HVHW
2FFXUUHG"

<HV

<HV

5HG/('RQ
/('

&RQILJXUH
&DOHQGDU

1R
(QGRILQLWLDOL]DWLRQ

1R

'LVSOD\'DWHDQG
7LPH

1R

(QWHU/RZ3RZHU
0RGH6WRS

'LVSOD\7LPHVWDPS'DWHDQG7LPH

&KHFN%DFN8S5HJLVWHUVDUHFOHDUHG
7DPSHU
'HWHFWHGLQ,7
"

<HV

'HDFWLYDWH7DPSHU

$OZD\VH[HFXWHGXSRQV\VWHPUHVHW
([HFXWHGXSRQSRZHURQUHVHW
([HFXWHGXSRQEDFNXSGRPDLQUHVHW

38/51

DocID028310 Rev 2

06Y9

AN4759

STM32L4 API and tampering detection application example

4.3

Application example project

4.3.1

Hardware Setup
In order to use the application example project, the user needs a STM32L476 evaluation
board (order code: STM32L476G-EVAL).
Figure 23. STM32L476 evaluation board

-3

3$

-3

-3

86%
3RZHU6XSSO\

8VHU/('V

Supply the board using the USB cable. For this example to work, the user needs to tie PA0
(tamper pin 2) to 0. In order to do that :

Note:

Remove the jumper JP7

Connect the CN7 pin 37 to GND.

PC13 (tamper pin 1) connected to the blue push-button is not used in this demonstration
firmware as it is connected to an external pull-down resistor preventing the use of the
tamper detection on level with internal pull-up (lowest consumption mode).
For more information, refer to [9].

DocID028310 Rev 2

39/51
50

STM32L4 API and tampering detection application example

4.3.2

AN4759

Software setup
Open the project under the users favorite integrated development environment. For IAR
EWARM, open the project.eww file. For Keil MDK-ARM, open the project.uvprojx file,
compile and launch the debug session. For SW4STM32, open the SW4STM32 toolchain,
browse to the SW4STM32 workspace directory, select and import the project
RTC_TamperVBATT. Launching the debug session will load the program in the internal
Flash memory and execute it.
In EWARM debug session, the user can view the calendar and tamper event timestamp
(time and date) by opening a Live watch window (View -> Live watch) and observe the
following global variables:

aShowTime

aShowDate

aShowTimeStampTime

aShowTimeStampDate

The same observation can be done using Keil/MDK-ARM development tools. To open
"Watch1" window, do View->Watch Windows -> Watch1.

4.3.3

LED meaning
LD1 (Green): Tamper event detected
TFT displays: the Tamper date and the Tamper time are different from their initialization
state
LD2 (Orange): Power-On Reset occurred
TFT displays: the Tamper date and the Tamper time are at their initialization state
LD3 (Red): Error (RTC or RCC configuration error, backup registers not erased)
TFT displays: error occurred is displayed
LD4 (Blue): Reset occurred.
TFT displays: the Tamper date and the Tamper time are at their initialization state

4.3.4

Tampering detection during normal operation

Disconnect the debugger. A Power-On Reset can be generated by removing the JP17
jumper and placing it again on STlk.
Open PA0 (input is now floating), the LD1 lits showing that a tamper event is detected. On
TFT, the Tampering date and Tampering time will be updated with the timestamp of the
Tamper event. Note that the user observes a long delay (up to 2 seconds) before the tamper
event is detected. This is due to the trade-off in the tamper detection frequency
(TAMPFREQ) chosen which ensures the lowest power consumption.
A reset can be applied by pushing the black reset button. The application is now able the
detect a new tamper event.

40/51

DocID028310 Rev 2

AN4759

4.3.5

STM32L4 API and tampering detection application example

Tampering detection when main power supply is off

If the user supplies the VBAT pin with the external CR1220 battery (JP12 on BAT position),
the tamper event can be detected even if the main power supply is off. Proceed as follow:

Remove the JP17 jumper

Open PA0

Tie PA0 to GND (this is simulating that the end-user takes care to close the box
containing the electronics before supplying it again)

Set JP17 on STlk

The LD1 lits showing that a tamper event has been detected during the power down
and on TFT, the Tampering date and Tampering time will be updated with the
timestamp of the Tamper event

Note that if the user supplies the VBAT pin with 3V (JP12 on VDD position), the RTC is no
longer supplied when the main power supply is switched off. In this case, the application is
no longer able to detect the tampering event while the main power supply is off.

DocID028310 Rev 2

41/51
50

STM32L4 API and digital smooth calibration application example

STM32L4 API and digital smooth calibration

application example

5.1

STM32 Cube firmware libraries

AN4759

The TIMER peripheral comes with:

A firmware driver API abstracting the TIMER features for the end-user. Refer to
stm32l4xx_hal_tim.c and stm32l4xx_hal_tim_ex.c files in
\STM32Cube_FW_L4_Vx.y.z\Drivers\STM32L4xx_HAL_Driver\

A set of example projects so that the user can quickly become familiar with the TIMER
peripheral. Refer to the examples in
\STM32Cube_FW_L4_Vx.y.z\Projects\STM32L476RG-Nucleo\Examples\TIM

The Real-Time Clock peripheral comes with:

5.2

A firmware driver API abstracting the RTC features for the end-user. Refer to
stm32l4xx_hal_rtc.c and stm32l4xx_hal_rtc_ex.c files in
\STM32Cube_FW_L4_Vx.y.z\Drivers\STM32L4xx_HAL_Driver\

A set of example projects so that the user can quickly become familiar with the RTC
peripheral. Refer to the examples in
\STM32Cube_FW_L4_Vx.y.z\Projects\STM32L476RG-Nucleo\Examples\RTC

STM32 Cube expansion firmware

This application note comes with the X-CUBE-RTC expansion software upon the STM32
Cube firmware libraries.
This example shows an implementation of the digital smooth calibration feature of the RTC.
It also uses the GPTIMER HAL API.
It shows a concrete example where RTC_CLK is smoothly calibrated based on an external
1 Hz reference. The firmware implements:

A GP timer in Master mode using channel 1 in output compare mode. It uses an

external trigger clock.

A GP timer in Master mode using channel 1 in input capture mode and channel 2
in output compare mode. It is also configured to use the LSE clock thanks to the
TIM option register.

The RTC with the programmation of the CALR register.

GPIOs to connect the input 1 Hz reference clock and the corrected

RTC_OUT_CALIB clock.

The application block diagram is shown in Figure 24.

42/51

DocID028310 Rev 2

AN4759

STM32L4 API and digital smooth calibration application example

5.3

Application example project

5.3.1

Hardware setup
In order to use the application example project, the user needs a STM32L476RG Nucleo
board.
Figure 24. STM32L476RG-Nucleo board

Supply the board using the USB cable. For this example, the user needs to:

5.3.2

Connect PD2 to a signal generator driving 1 Hz clock with 3.3 V amplitude. It is advised
to control the generated frequency at few ppm.

Connect PB2 to an oscilloscope. Note that the accuracy of the frequency measurement
is ideally in the range of 1 ppm.

Software setup
Open the project under the users favorite integrated development environment. For IAR
EWARM, open the "RTC_SmoothCalib.eww" file. For Keil MDK-ARM, open the
"RTC_SmoothCalib.uvprojx" file. For SW4STM32, open the SW4STM32 toolchain, browse
to the SW4STM32 workspace directory, select and import the project RTC_SmoothCalib.
Compile and launch the debug session. It loads the program in the internal Flash memory
and executes it.
After a maximum of 64 seconds, make a frequency measurement of the CALIB_OUT clock
on PB2. The user shall get a frequency accurate at 1 ppm compared to the 1 Hz reference
clock sent on PD2.

DocID028310 Rev 2

43/51
50

STM32L4 API and digital smooth calibration application example

AN4759

The user can then modify the PD2 clock by few ppm, wait 64 seconds and check that the
PB2 clock has been changed accordingly.
Under debugger, the user can monitor the evolution of the CALR register fields: CALP and
CALM.

5.3.3

Application block diagram

d/D,

(;775,*#+]LQWHUUXSW

7,0 +] 7,0

,QSXW
&DSWXUH
7,0[B&&5

0

57&B&$/5

57&
&DOLEUDWLRQ

5()&/.
+]

57&
%/2&.6

57&&/.
/6(
N+]

57&&/.B&255(&7('

287387
+]

08;

57&
&DOLEUDWLRQEDVHGRQH[WHUQDOVLJQDO
06Y9

The application is based on 4 steps:

1.

A 1Hz reference clock is connected to TIM3 through the PD2 GPIO

2.

TIM3 is configured to generate a rising edge after 32 x 1 Hz reference rising edges.

This gives an event every 32 seconds.

3.

TIM2 is configured to increment its counter on CLK_RTC and to get the counter value
on the rising edge generated by TIM3 and stores it in the TIM2_CCR1 register. It then
reset itslef.

4.

The cortex-M4 core gets the TIM2_CCR1 value, compares it with the number of
CLK_RTC cycles expected in 32 seconds and processes the comparison results to
update the CALP and CALM fields of the RTC_CALR register.

The calibration is continous.

5.3.4

Run time observations

To check the correct functionality:
1.

Modify the 1 Hz reference clock, for instance by forcing 1.0001 Hz

2.

Wait 2 x 32 seconds

3.

Measure the output frequency. Depending of the accuracy of the generator and the
measurement device used, the user can see around 1 ppm accuracy.

The user can also monitor in debug mode:

44/51

The RTC_CALR register (CALM and CALP fields)

The TIM2_CCR1 register (which contains the number of CLK_RTC cycles within a
32 second window)

DocID028310 Rev 2

AN4759

STM32L0 API and tampering detection application example

STM32L0 API and tampering detection application

example

6.1

STM32 Cube firmware libraries

The Real-Time Clock peripheral comes with:

6.2

A firmware driver API abstracting RTC features for the end-user. Refer to
stm32l0xx_hal_rtc.c and stm32l0xx_hal_rtc_ex.c files in
\STM32Cube_FW_L0_Vx.y.z\Drivers\STM32L0xx_HAL_Driver\

A set of example projects so that the user can quickly become familiar with the RTC
peripheral. Refer to the examples in
\STM32Cube_FW_L0_Vx.y.z\Projects\STM32L053R8-Nucleo\Examples\RTC

STM32 Cube expansion firmware

This application note comes with the X-CUBE-RTC expansion software upon the STM32
Cube firmware libraries.
It shows a concrete example where a real-time clock must be maintained alive while using
as less power as possible. The firmware implements:

A few hints order to ensure a low current consumption,

A display in the debugger (date and time, timestamp date and time) and on a
single LED (power up events, reset events, tamper events, error)

The tampering detection capability,

The ability to timestamp the tampering event,

The ability to erase the backup registers that may contain sensitive data upon
tamper detection.

The application flowchart is shown in Figure 22: Application example flowchart.

DocID028310 Rev 2

45/51
50

STM32L0 API and tampering detection application example

6.3

Application example project

6.3.1

Hardware setup

AN4759

In order to use the application example project, the user needs a STM32L053R8-Nucleo
board (order code STM32L053R8-NUCLEO).
Figure 25. STM32L053R8-Nucleo board

Supply the board using the USB cable. In this example, the user uses the B1 push button to
simulate the external tamper event. The user can observe the software "private variables"
on LED LD2 and CN5 Pin 6 (SCK/D13). Details regarding the LED LD2 behavior are
available in main.c file.
Figure 26. LED LD2 behavior
&13LQ

7LPH

/('/'VWDWH
/('B*UHHQB7DPSHU

/('B5HGB3RZHUB2QB5HVHW

/('B5HGB(UURU

/('B%OXHB5HVHW
06Y9

46/51

DocID028310 Rev 2

AN4759

6.3.2

STM32L0 API and tampering detection application example

Software setup
Open the project under the users favorite integrated development environment. For IAR
EWARM, open the "project.eww" file. For Keil MDK-ARM, open the "project.uvprojx" file. For
SW4STM32, open the SW4STM32 toolchain, browse to the SW4STM32 workspace
directory, select and import the project RTC_Tamper.
Compile and launch the debug session. This will load the program in the internal Flash
memory and execute it.
In EWARM debug session, the user can view the calendar and tamper event timestamp
(time and date) by opening a "Live watch" window (View -> Live Watch) and observe the
following global variables:

aShowTime

aShowDate

aShowTimeStampTime

aShowTimeStampDate

The user can add and follow these "private variables":

LED1_Green_Tamper_event_detected

LED2_Red_Power_On_Reset_occurred

LED3_Red_Error

LED4_Blue_Reset_occurred

The same observation can be done using Keil/MDK-ARM development tools. To open
"Watch1" window, do View->Watch Windows -> Watch1.

6.3.3

LED meaning.
Only one LED (LD2) is available on the STM32L053R8-Nucleo board. To match with the
STM32L4 examples, described in Section 4: STM32L4 API and tampering detection
application example, LED1, LED2, LED3 and LED4 are replaced by 4 integers:

uint32_t LED1_Green_Tamper_event_detected:
Set when tamper1 event is detected.
Equivalent to LED1_Green in STM32L4 examples.

uint32_t LED2_Red_Power_On_Reset_occurred:
Set when power-on reset is detected.
Equivalent to LED2_Red in STM32L4 examples.

uint32_t LED3_Red_Error:
Set in errors cases.
Equivalent to LED3_Red in STM32L4 examples.

uint32_t LED4_Blue_Reset_occurred:
Set when reset is detected (B2 black push button).
Equivalent to LED4_Blue in STM32L4 examples.

The user can observe these "private variables" using the live watch feature in the debugger.
The user can observe these "private variables" on LED LD2 and CN5 Pin 6 (SCK/D13).
Regarding the LED LD2 behavior, see details in main.c file.

DocID028310 Rev 2

47/51
50

STM32L0 API and tampering detection application example

6.3.4

AN4759

Tampering detection during normal operation

Step1: a Power-On-Reset can be generated by disconnecting/connecting the USB cable on
CN1.
Table 15. Tampering detection status when Power-On-Reset is detected
Meaning

Status

LED LD2 (Blink)

LED1_Green_Tamper_event_detected

OFF

LED2_Red_Power_On_Reset_occurred

ON

LED3_Red_Error

OFF

LED4_Blue_Reset_occurred

ON

Step2: Push B1 to simulate a tamper event.

Table 16. Tampering detection status when tamper event is detected
Meaning

Status

LED LD2 (Blink)

LED1_Green_Tamper_event_detected

ON

LED2_Red_Power_On_Reset_occurred

ON

LED3_Red_Error

OFF

LED4_Blue_Reset_occurred

ON

Step3: Push B2 to simulate a reset.

Table 17. Tampering detection status when reset is detected
Meaning

Status

LED LD2 (Blink)

LED1_Green_Tamper_event_detected

OFF

LED2_Red_Power_On_Reset_occurred

OFF

LED3_Red_Error

OFF

LED4_Blue_Reset_occurred

ON

Step4: Push B1 to simulate a tamper event.

Table 18. Tampering detection status when tamper event is detected
Meaning

48/51

Status

LED LD2 (Blink)

LED1_Green_Tamper_event_detected

ON

LED2_Red_Power_On_Reset_occurred

OFF

LED3_Red_Error

OFF

LED4_Blue_Reset_occurred

ON

DocID028310 Rev 2

AN4759

Reference documentation

Reference documentation
[1]. STM32L4x6 advanced ARM-based 32-bit MCUs reference manual (RM0351)
[2]. Ultra-low-power STM32L0xx advanced ARM-based 32-bit MCUs reference manuals
(RM0367, RM0376, RM0377)
[3]. STM32L100xx, STM32L151xx, STM32L152xx and STM32L162xx advanced ARMbased 32-bit MCUs (RM0038)
[4]. STM32F0x1/STM32F0x2/STM32F0x8 advanced ARM-based 32-bit MCUs reference
manual (RM0091)
[5]. STM32F205xx, STM32F207xx, STM32F215xx and STM32F217xx advanced ARMbased 32-bit MCUs reference manual (RM033)
[6]. STM32F301x6/8 and STM32F318x8 advanced ARM-based 32-bit MCUs reference
manual (RM0366)
[7]. STM32F405/415, STM32F407/417, STM32F427/437 and STM32F429/439 advanced
ARM-based 32-bit MCUs reference manual (RM090)
[8]. STM32F75xxx and STM32F74xxx advanced ARM-based 32-bit MCUs reference
manual (RM0385)
[9]. Evaluation board with STM32L476ZGT6 MCU user manual (UM1855)
[10]. STM32 Nucleo-64 boards user manual (UM1724)
[11]. Optimizing power and performances with STM32L4 Series microcontrollers application
note (AN4746)
[12]. STM32L0xx ultra-low power features overview application note (AN4445)

DocID028310 Rev 2

49/51
50

Revision history

AN4759

Revision history
Table 19. Document revision history
Date

Revision

26-May-2016

Initial release.

Updated Table 1: Applicable products adding product series

and part number.
Updated Figure 3: STM32L0 Series, STM32L1 Series,
STM32F2 Series and STM32F4 Series RTC clock sources.
Updated Figure 4: STM32L4 Series and STM32F7 Series
RTC clock sources
Added Figure 5: STM32F0 Series and STM32F3 Series RTC
clock sources.
Updated Table 3: Calendar clock equal to 1 Hz with different
clock sources.
Updated Section 1.4: Digital smooth calibration adding the
RTC calibration basics.
Updated Table 14: Advanced RTC features.
Updated Section 4.3.3: LED meaning.
Added Section 5: STM32L4 API and digital smooth calibration
application example.
Updated Section 6.3.1: Hardware setup.
Updated Section 6.3.2: Software setup.
Updated Section 7: Reference documentation.

25-Oct-2016

50/51

Changes

DocID028310 Rev 2

AN4759

IMPORTANT NOTICE PLEASE READ CAREFULLY

STMicroelectronics NV and its subsidiaries (ST) reserve the right to make changes, corrections, enhancements, modifications, and
improvements to ST products and/or to this document at any time without notice. Purchasers should obtain the latest relevant information on
ST products before placing orders. ST products are sold pursuant to STs terms and conditions of sale in place at the time of order
acknowledgement.
Purchasers are solely responsible for the choice, selection, and use of ST products and ST assumes no liability for application assistance or
the design of Purchasers products.
No license, express or implied, to any intellectual property right is granted by ST herein.
Resale of ST products with provisions different from the information set forth herein shall void any warranty granted by ST for such product.
ST and the ST logo are trademarks of ST. All other product or service names are the property of their respective owners.
Information in this document supersedes and replaces information previously supplied in any prior versions of this document.
2016 STMicroelectronics All rights reserved

DocID028310 Rev 2

51/51
51