{"id":3151,"date":"2025-01-11T14:26:37","date_gmt":"2025-01-11T14:26:37","guid":{"rendered":"https:\/\/blog.embeddedexpert.io\/?p=3151"},"modified":"2025-01-11T14:26:38","modified_gmt":"2025-01-11T14:26:38","slug":"getting-started-with-stm32h5-arm-cortex-m33-internal-rtc","status":"publish","type":"post","link":"https:\/\/blog.embeddedexpert.io\/?p=3151","title":{"rendered":"Getting Started with STM32H5 ARM Cortex M33: Internal RTC"},"content":{"rendered":"
\n
\"\"<\/figure><\/div>\n\n\n

In this guide on RTC (Real-Time Clock), we shall explore the features of the RTC on STM32H5, its functional block diagram, and how to develop a driver using STM32CubeMX.<\/p>\n\n\n\n

In this guide, we shall cover the following:<\/p>\n\n\n\n

\u2022 What is RTC.<\/p>\n\n\n\n

\u2022 STM32CubeIDE Configuration.<\/p>\n\n\n\n

\u2022 Firmware development.<\/p>\n\n\n\n

\u2022 Results.<\/p>\n\n\n\n

<\/p>\n\n\n\n

1. What is RTC:<\/h2>\n\n\n\n

Introduction to the STM32H5 Internal RTC<\/strong><\/p>\n\n\n\n

The STM32H5 microcontroller features a highly versatile Real-Time Clock (RTC)<\/strong> designed for applications that require precise timekeeping and date tracking. The internal RTC operates independently of the main system clock, ensuring accurate functionality even during low-power modes. This makes it ideal for devices such as smart meters, data loggers, wearable electronics, and other time-sensitive embedded systems.<\/p>\n\n\n\n

Key Features of the Internal RTC:<\/strong><\/p>\n\n\n\n

1. Low-Power Operation<\/strong>:<\/p>\n\n\n\n

\u2022 The RTC can remain operational in Standby or Stop modes, consuming minimal power.<\/p>\n\n\n\n

2. Flexible Clock Source<\/strong>:<\/p>\n\n\n\n

\u2022 Supports multiple clock sources, including the Low-Speed External oscillator (LSE), Low-Speed Internal oscillator (LSI), and High-Speed External oscillator (HSE).<\/p>\n\n\n\n

3. Calendar Functionality<\/strong>:<\/p>\n\n\n\n

\u2022 Tracks year, month, day, hours, minutes, and seconds with leap year compensation.<\/p>\n\n\n\n

4. Programmable Alarms and Wakeup Timer<\/strong>:<\/p>\n\n\n\n

\u2022 Features two alarms and a wakeup timer for precise timing events and system wake-ups.<\/p>\n\n\n\n

5. Backup Registers<\/strong>:<\/p>\n\n\n\n

\u2022 Includes 20 backup registers to retain user data during power loss or system resets.<\/p>\n\n\n\n

6. Tamper Detection<\/strong>:<\/p>\n\n\n\n

\u2022 Monitors tamper events and secures critical data.<\/p>\n\n\n\n

Block Diagram Overview<\/strong><\/p>\n\n\n\n

The block diagram of the RTC provides a clear representation of its components and connections. It includes the following elements:<\/p>\n\n\n\n

\u2022 Clock Sources<\/strong>:<\/p>\n\n\n\n

\u2022 LSE, LSI, and HSE provide the flexibility to select the most appropriate clock source for the application.<\/p>\n\n\n\n

\u2022 Prescaler and Divider<\/strong>:<\/p>\n\n\n\n

\u2022 Adjusts the input clock to generate the 1 Hz signal required for the RTC core.<\/p>\n\n\n\n

\u2022 Calendar Unit<\/strong>:<\/p>\n\n\n\n

\u2022 Maintains accurate time and date with leap year adjustments.<\/p>\n\n\n\n

\u2022 Alarm and Wakeup Unit<\/strong>:<\/p>\n\n\n\n

\u2022 Enables system alerts and wakeup events.<\/p>\n\n\n\n

\u2022 Backup Registers<\/strong>:<\/p>\n\n\n\n

\u2022 Stores user data securely during power cycles.<\/p>\n\n\n\n

\u2022 Tamper Detection<\/strong>:<\/p>\n\n\n\n

\u2022 Protects sensitive information by detecting external tamper events.<\/p>\n\n\n\n

The internal RTC of the STM32H5 is a reliable and flexible solution for managing time-critical operations in embedded systems. The following block diagram illustrates its architecture and connections:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

2. STM32CubeIDE Configuration:<\/h2>\n\n\n\n

We start off by creating new project with name of Internal RTC. For how to create project using STM32CubeIDE, please refer to this guide here<\/a>.<\/p>\n\n\n\n

After creating the project, the STM32CubeMX configuration window will appear.<\/p>\n\n\n\n

From System Core from left, select RCC then enable external low speed oscillator as following:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Next, from timers section, select RTC then activate Clock Sources and Calendar as following:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Also, set the time and date as you wish. Here, the values are random.<\/p>\n\n\n\n

Next, go to clock configuration, set the RTC clock source to be LSE (Low Speed External) as following:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Also, enable the UART to print the RTC value. For how to enable the uart, please refer to this guide here<\/a>.<\/p>\n\n\n\n

Thats all for the configuration.<\/p>\n\n\n\n

Save the project and this will generate the project.<\/p>\n\n\n\n

<\/p>\n\n\n\n

3. Firmware Development:<\/h2>\n\n\n\n

In main.c file.<\/p>\n\n\n\n

In user begin includes, include the stdio header file as following:<\/p>\n\n\n\n

\/* USER CODE BEGIN Includes *\/\n#include "stdio.h"\n\/* USER CODE END Includes *\/<\/pre><\/div>\n\n\n\n
Next, in user code begin PV, declare the following two data structure for the RTC operation:<\/p>\n\n\n\n
\/* USER CODE BEGIN PV *\/\nRTC_TimeTypeDef gTime = {0};\nRTC_DateTypeDef gDate = {0};\n\/* USER CODE END PV *\/<\/pre><\/div>\n\n\n\n
First data structure is to store the time while the second one is to store the date.<\/p>\n\n\n\n
In user code begin 0, we shall retarget the printf to user UART as following:<\/p>\n\n\n\n
int __io_putchar(int ch)\n{\n\tHAL_UART_Transmit(&huart2, &ch, 1, 5);\n\n\treturn ch;\n}<\/pre><\/div>\n\n\n\n
This will allow us to use terminal to display the results.<\/p>\n\n\n\n
In RTC_MX_Init function, at user code begin check_RTC_BKUP:<\/p>\n\n\n\n
  \/* USER CODE BEGIN Check_RTC_BKUP *\/\n  if (HAL_RTCEx_BKUPRead(&hrtc, RTC_BKP_DR1)== 0x4567)\n  {\n\t  return ;\n  }\n  \/* USER CODE END Check_RTC_BKUP *\/<\/pre><\/div>\n\n\n\n
This line, will prevent entering new date and time once the MCU is reseted.<\/p>\n\n\n\n
At user code begin RTC_Init_2, add this line:<\/p>\n\n\n\n
  \/* USER CODE BEGIN RTC_Init 2 *\/\n  HAL_RTCEx_BKUPWrite(&hrtc, RTC_BKP_DR1, 0x4567);\n\n\n  \/* USER CODE END RTC_Init 2 *\/<\/pre><\/div>\n\n\n\n
<\/p>\n\n\n\n
By writing any value to the RTC backup register, this will lock the RTC from configuration. During the boot, we shall check this register if it has the same value, then no need to reinitialize the RTC data.<\/p>\n\n\n\n
In while 1 loop, user code begin 3:<\/p>\n\n\n\n
<\/p>\n\n\n\n
\t\tif (HAL_RTC_GetTime(&hrtc, &gTime, RTC_FORMAT_BIN) != HAL_OK)\n\t\t{\n\t\t\tError_Handler();\n\t\t}\n\t\tif(HAL_RTC_GetDate(&hrtc, &gDate, RTC_FORMAT_BIN)!=HAL_OK)\n\t\t{\n\t\t\tError_Handler();\n\t\t}\n\n\t\tprintf("Time is %d:%d:%d\\r\\n",gTime.Hours,gTime.Minutes,gTime.Seconds);\n\t\tprintf("Date is %d\/%d\/%d\\r\\n",gDate.Date,gDate.Month,gDate.Year);\n\t\tHAL_Delay(500);<\/pre><\/div>\n\n\n\n
Thats all for the firmware development.<\/p>\n\n\n\n
Save the project, build it and run it on your STM32H563Zi board.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
<\/p>\n\n\n\n
4. Results:<\/h2>\n\n\n\n
<\/p>\n\n\n\n
After the running the project, open your favourite serial terminal and set the baud rate to 115200 and you should get the RTC values as following:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
<\/p>\n\n\n\n
Happy coding \ud83d\ude09<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
In this guide on RTC (Real-Time Clock), we shall explore the features of the RTC on STM32H5, its functional block diagram, and how to develop a driver using STM32CubeMX. In this guide, we shall cover the following: \u2022 What is RTC. \u2022 STM32CubeIDE Configuration. \u2022 Firmware development. \u2022 Results. 1. What is RTC: Introduction to […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,11,12],"tags":[],"class_list":["post-3151","post","type-post","status-publish","format-standard","hentry","category-embedded-systems","category-peripheral-drivers","category-stm32"],"_links":{"self":[{"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=\/wp\/v2\/posts\/3151"}],"collection":[{"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3151"}],"version-history":[{"count":1,"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=\/wp\/v2\/posts\/3151\/revisions"}],"predecessor-version":[{"id":3158,"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=\/wp\/v2\/posts\/3151\/revisions\/3158"}],"wp:attachment":[{"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3151"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3151"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.embeddedexpert.io\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3151"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}