-
Notifications
You must be signed in to change notification settings - Fork 12
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
Provisioning sketch #453
Draft
chrysn
wants to merge
19
commits into
future-proof-iot:main
Choose a base branch
from
chrysn-pull-requests:provisioning
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Provisioning sketch #453
Conversation
This file contains 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
… accessor This makes the defmt dependency of riot-rs-embassy-common unconditional to allow enfocing it in a trait. The "convenience" wrapper riot_rs::identity::device_identity is added because a simple single method call would otherwise not only require users to dig into ::arch, but also to import a trait form -common (which they may not even depend on).
The riot_rs module can not be in scope here, so intradoc links are not possible.
…general accessor See-Also: future-proof-iot#444 (comment)
Previously, the type was just a never-instanciated-even-though-you-could type to put things into a trait. Now it *is* the return type, opening up for further evolution through provided methods.
Co-authored-by: ROMemories <152802150+ROMemories@users.noreply.github.com>
Contributes-To: future-proof-iot#446
The latest commit uses the --config-file option to probe-rs -- that has been merged, but will require installation from git. Pausing activity here until device-id (#444) is done; maybe by that time, a |
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.
Description
Building on #444, this is a first demo of how the device ID could be used to do something with it outside the system.
Aligned with the latest plans for #446, this collects some data at startup time (once storage is available: after having generated a private/public key pair), and reports them. For applications with defmt, the only way I found to pick up data from the output was to use
cargo embed
, which can tee the reassembled defmt texts to a TCP socket. (I generally think that cargo-embed is something we should look into: It also allows neat things such a having stdout / defmt (even simultaneously for those so inclined) while also having GDB through probe-rs).Issues/PRs references
Open Questions
Change checklist