Initialize external RTC after power loss#3003
Open
axhoff wants to merge 1 commit into
Open
Conversation
axhoff
marked this pull request as ready for review
July 20, 2026 14:16
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Root cause
AutoDiscoverRTCClockselected a PCF8563 after successful I2C initialization without checking its voltage-low/lost-power flag. On the XIAO expansion board without an RTC backup battery, a hard power loss could therefore leave untrustworthy clock contents (for example, a date in 2042). The companion's existing backward-time guard would then correctly reject the lower current time, leaving the node stuck on the invalid future timestamp.Scope
lostPower()state and follows the same discovery pathValidation
pio test -e native— 15/15 tests passedpio run -e Xiao_S3_WIO_companion_radio_ble— passedgit diff --check— passedFixes #2996