Issue with STM32Cube generating HAL_RTCEx_SetWakeUpTimer_IT in MX_RTC_Init. Configuration issue or bug?

[Chasqui]

Dear ST community, I am new developing firmware for stm32s. I am trying to enable the interrupt for RTC wakeup for a nucleoL476RG board using STM32CubeIDE 1.7.0 (which is using STM32CubeMX 6.3.0-RC5). I am selecting WakeUp: Internal WakeUp. I am also enabling RTC wake-up interrupt through EXTI line 20 and selecting Generate IRQ handler and Call HAL handler.

However, the  HAL_RTCEx_SetWakeUpTimer_IT call is not been created in MX_RTC_Init. Interestingly,  the alternate HAL_RTCEx_SetWakeUpTimer does get generated if I select Internal WakeUp but without enabling the interrupt.

Am I missing something in my configuration or is there a bug in STM32Cube? Help would be appreciated!

[Imen.D · Accepted solution]

Hello @Chasqui​ and welcome to the Community 🙂

Thanks to have reported this issue.

You are right the MX_RTC_Init () is missing HAL_RTCEx_SetWakeUpTimer_IT () with STM32CubeMX version 6.3.0.

Our team are working to resolve this issue in the coming releases of STM32CubeMX.

(Internal Ticket 111366: this is an internal tracking number and is not accessible or usable by customers)

Meanwhile, you can use the STM32CubeMX version 6.2.1 as the HAL_RTCEx_SetWakeUpTimer_IT () is correctly generated in MX_RTC_Init () with this previous release.

Thank you for your contribution and your patience while we work to fix this issue.

When your question is answered, please close this topic by choosing Select as Best.

Imen