-
Notifications
You must be signed in to change notification settings - Fork 240
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
Current defmt version is broken #581
Comments
Possible fixes for the mentioned issues: |
do any of the two prs fix the issue? |
Those are two different issues, both with their own fix. Depending on what you want to do, one might be sufficient. Eg. if you update your firmware to use the most recent defmt version, you don't need support for the older one. So the fix for the reset handler issue in probe-run would be sufficient. |
Since we've already had unintended dependency breakage, best make it
to ensure that nothing else new and broken gets pulled in |
Good point. It doesn't matter for the dependency in question, as probe-run does depend on an exact version of defmt-decoder. But of course a similar breakage could happen with some other dependency. I added the flag. |
If anyone wants to help and test the Handle reset vector PR in order to be approved and merged faster, please consider commenting in the PR after testing with the changes:
|
Fixes for both mentioned issues have been released. |
If you run into the following error, it is caused by a breaking change of the
defmt
crate in version 0.3.5:Unfortunately, the latest version of
probe-run
is also broken, an update would cause this error:So for now, the best workaround is to stay with older versions of
probe-run
anddefmt
.Run:
And add this to your
Cargo.toml
(Version 0.3.3 would be better if it wasn't yanked for some reason. 😞)
The text was updated successfully, but these errors were encountered: