add statime-embassy-net - #873
Open
jordens wants to merge 7 commits into
Open
Conversation
jordens
force-pushed
the
pr/embassy-runner
branch
from
August 20, 2026 14:38
ad52943 to
8860708
Compare
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
2 participants
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.
This adds a statime ordinary-clock runner for embassy plus an example.
It uses the shared fixed-wander servo (#872) and Embassy's generic network clock interface (embassy-rs/embassy#6802). That way e.g. an ESP CPU implementing the embassy clock trait can directly use this runner.
This also keeps the library outside Statime's workspace and the STM32H743 application in
its own standalone workspace. That way (like for the statime-stm32 example) board dependencies, target configuration, linker script, lockfile, and crate patches are contained.
Depends on the Embassy network-clock PR embassy-rs/embassy#6802
Stacks on top of #871 and #872
Close #845
I know I'm targetting a potentially dead horse but it's the most convenient approach currently. Happy to retarget later to whatever shape ntpd-rs ultimately assumes.