Skip to content

fix: in configForLowPower(), begin() should be call unconditionnally #68

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 24, 2022

Conversation

ABOSTM
Copy link
Contributor

@ABOSTM ABOSTM commented Jun 13, 2022

fix: in configForLowPower(), begin() should be call unconditionnally

The fact RTC is already configured or not,
is handled by begin() itself.
Fixes stm32duino/STM32LowPower#71

Signed-off-by: Alexandre Bourdiol [email protected]

The fact RTC is already configured or not,
is handled by begin() itself.
Fixes stm32duino/STM32LowPower#71

Signed-off-by: Alexandre Bourdiol <[email protected]>
* RTC_initClock() must be called after reset of backup domain
* NVIC interrupt enable is done within RTC_StartAlarm()
  to avoid cases where alarm is pending but never cleared by ISR handler
* STM32RTC::begin() should get format parameter instead of period
* If timer is not already set, configure an arbitrary time for Lowpower usage

Signed-off-by: Alexandre Bourdiol <[email protected]>
Copy link
Member

@fpistm fpistm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@fpistm fpistm linked an issue Jun 16, 2022 that may be closed by this pull request
@fpistm fpistm merged commit 86ab4b7 into stm32duino:main Jun 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

There is a bug about alarm interrupt in V1.3 Examples of STM32LowPower for STM32WLE5CCU6
2 participants