CubeMX Configuration for a Given MCU Model

An example CubeMX peripheral configuration profile for the RTC Alarm IRQ block is provided below. Depending on the exact microcontroller model utilized, certain options may be unavailable or require supplementary configurations. Should you encounter architecture-specific omissions, consult the official manufacturer reference manual.

H7

General CubeMX Settings

No.	Name	Path	Setting	Description
1	Low Speed Clock	Pinout & Configuration > System Core > RCC > Mode > Low Speed Clock (LSE)	`Crystal/Ceramic Resonator` if an onboard external clock crystal is available. `BYPASS Clock Source` if a reference RTC signal is fed externally into the designated MCU hardware pins.	Selects the baseline input clock source dedicated to the RTC subsystem.
2	Activate Clock Source	Pinout & Configuration > Timers > RTC > Mode > Activate Clock Source	`Enabled`	Activates the core hardware clock path for the RTC peripheral.
3	Activate Calendar	Pinout & Configuration > Timers > RTC > Mode > Activate Calendar	`Enabled`	Enables tracking registers for the internal RTC calendar framework.
4	Internal Alarms	Pinout & Configuration > Timers > RTC > Mode > Alarms A, B or WakeUp	`Internal Alarm A / B / WakeUp`	Enables hardware support for internal RTC alarms. The `internal` routing variant must be selected for Alarm A, Alarm B, and WakeUp triggers.
5	RTC wake-up interrupt through EXTI line	Pinout & Configuration > Timers > RTC > NVIC Settings > RTC wake-up interrupt through EXTI line	`Enabled`	Enables the nested vectored interrupt controller (NVIC) line for the RTC wake-up interrupt routed through the EXTI architecture.
6	RTC alarms (A and B) interrupt through EXTI line	Pinout & Configuration > Timers > RTC > NVIC Settings > RTC alarms (A and B) interrupt through EXTI line	`Enabled`	Enables the nested vectored interrupt controller (NVIC) line for the dual RTC alarms (A and B) routed through the EXTI architecture.
7	RTC Clock Mux	Clock Configuration > RTC Clock Mux	`LSE` or the corresponding alternate hardware source selected in step 1.	Configures the peripheral clock multiplexer routing. This path must map directly to the hardware source established in step 1.
8	Do Not Generate Function Call	Project Manager > Advanced Settings > Generated Function Calls > MX_RTC_Init > Do Not Generate Function Call	`Enabled`	Inhibits the automatic generation of the standard `MX_RTC_Init` routine inside the output application source code.
9	Visibility (Static)	Project Manager > Advanced Settings > Generated Function Calls > MX_RTC_Init > Visibility (Static)	`Disabled`	Disables the static scope visibility modifier constraint for the generated RTC initialization routine within code files.

F4

General CubeMX Settings

No.	Name	Path	Setting	Description
1	Low Speed Clock	Pinout & Configuration > System Core > RCC > Mode > Low Speed Clock (LSE)	`Crystal/Ceramic Resonator` if an onboard external clock crystal is available. `BYPASS Clock Source` if a reference RTC signal is fed externally into the designated MCU hardware pins.	Selects the baseline input clock source dedicated to the RTC subsystem.
2	Activate Clock Source	Pinout & Configuration > Timers > RTC > Mode > Activate Clock Source	`Enabled`	Activates the core hardware clock path for the RTC peripheral.
3	Activate Calendar	Pinout & Configuration > Timers > RTC > Mode > Activate Calendar	`Enabled`	Enables tracking registers for the internal RTC calendar framework.
4	Internal Alarms	Pinout & Configuration > Timers > RTC > Mode > Alarms A, B or WakeUp	`Internal Alarm A / B / WakeUp`	Enables hardware support for internal RTC alarms. The `internal` routing variant must be selected for Alarm A, Alarm B, and WakeUp triggers.
5	RTC wake-up interrupt through EXTI line	Pinout & Configuration > Timers > RTC > NVIC Settings > RTC wake-up interrupt through EXTI line	`Enabled`	Enables the nested vectored interrupt controller (NVIC) line for the RTC wake-up interrupt routed through the EXTI architecture.
6	RTC alarms (A and B) interrupt through EXTI line	Pinout & Configuration > Timers > RTC > NVIC Settings > RTC alarms (A and B) interrupt through EXTI line	`Enabled`	Enables the nested vectored interrupt controller (NVIC) line for the dual RTC alarms (A and B) routed through the EXTI architecture.
7	RTC Clock Mux	Clock Configuration > RTC Clock Mux	`LSE` or the corresponding alternate hardware source selected in step 1.	Configures the peripheral clock multiplexer routing. This path must map directly to the hardware source established in step 1.
8	Do Not Generate Function Call	Project Manager > Advanced Settings > Generated Function Calls > MX_RTC_Init > Do Not Generate Function Call	`Enabled`	Inhibits the automatic generation of the standard `MX_RTC_Init` routine inside the output application source code.
9	Visibility (Static)	Project Manager > Advanced Settings > Generated Function Calls > MX_RTC_Init > Visibility (Static)	`Disabled`	Disables the static scope visibility modifier constraint for the generated RTC initialization routine within code files.

G0

General CubeMX Settings

No.	Name	Path	Setting	Description
1	Low Speed Clock	Pinout & Configuration > System Core > RCC > Mode > Low Speed Clock (LSE)	`Crystal/Ceramic Resonator` if an onboard external clock crystal is available. `BYPASS Clock Source` if a reference RTC signal is fed externally into the designated MCU hardware pins.	Selects the baseline input clock source dedicated to the RTC subsystem.
2	Activate Clock Source	Pinout & Configuration > Timers > RTC > Mode > Activate Clock Source	`Enabled`	Activates the core hardware clock path for the RTC peripheral.
3	Activate Calendar	Pinout & Configuration > Timers > RTC > Mode > Activate Calendar	`Enabled`	Enables tracking registers for the internal RTC calendar framework.
4	Internal Alarms	Pinout & Configuration > Timers > RTC > Mode > Alarms A, B or WakeUp	`Internal Alarm A / B / WakeUp`	Enables hardware support for internal RTC alarms. The `internal` routing variant must be selected for Alarm A, Alarm B, and WakeUp triggers.
5	RTC wake-up interrupt through EXTI line	Pinout & Configuration > Timers > RTC > NVIC Settings > RTC wake-up interrupt through EXTI line	`Enabled`	Enables the nested vectored interrupt controller (NVIC) line for the RTC wake-up interrupt routed through the EXTI architecture.
6	RTC alarms (A and B) interrupt through EXTI line	Pinout & Configuration > Timers > RTC > NVIC Settings > RTC alarms (A and B) interrupt through EXTI line	`Enabled`	Enables the nested vectored interrupt controller (NVIC) line for the dual RTC alarms (A and B) routed through the EXTI architecture.
7	RTC Clock Mux	Clock Configuration > RTC Clock Mux	`LSE` or the corresponding alternate hardware source selected in step 1.	Configures the peripheral clock multiplexer routing. This path must map directly to the hardware source established in step 1.
8	Do Not Generate Function Call	Project Manager > Advanced Settings > Generated Function Calls > MX_RTC_Init > Do Not Generate Function Call	`Enabled`	Inhibits the automatic generation of the standard `MX_RTC_Init` routine inside the output application source code.
9	Visibility (Static)	Project Manager > Advanced Settings > Generated Function Calls > MX_RTC_Init > Visibility (Static)	`Disabled`	Disables the static scope visibility modifier constraint for the generated RTC initialization routine within code files.