NTP updates #404
Merged
NTP updates #404
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
if rtcSyncd is false - i.e. the user has changed the time zone. The firmware will stop responding to NTP requests until the RTC is synced again.
This was referenced Jul 5, 2024
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.
Resolves #371
NTP mode is now working nicely on EVK Ethernet. Tested with NTP on Raspberry Pi.
I struggled with
ntpServer->parsePacket();andntpServer->available()for a while. It wasn't capturing the Raspberry Pi NTP requests. The solution was to callntpServer->clear();after each check. This ensures the internalrx_bufferis deleted correctly. Without thisparsePacketreturns 0 and won't receive the next packet.