Added time keeping for NRF52 across resets#2704
Open
IoTThinks wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
Hi all,
This is to keep time for NRF52 especially NRF52 repeaters across reboot and reset.
So we can still receive adverts after reset due to reboot or software faults.
I "cut" 8 bytes from RAM to make persistent RAM to store 2 uint32_t for time keeping.
This will have same behaviour as this PR for ESP32: #1896
Test cases:
The default time is 1 Mar 2026 as same as #1896.
I have tested repeaters and BLE companions fine for RAK4631, Heltec T114, Heltec T096 and Xiao NRF52.
I added boards/nrf52840_s140_v6.ld for some of my comon built NRF52 boards too.
Please help to do more tests with your NRF52 boards.