-
-
Notifications
You must be signed in to change notification settings - Fork 398
Easier recovery from soft bricked native USB boards #2173
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
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #2173 +/- ##
==========================================
+ Coverage 62.61% 62.64% +0.03%
==========================================
Files 223 223
Lines 19489 19498 +9
==========================================
+ Hits 12203 12215 +12
+ Misses 6200 6198 -2
+ Partials 1086 1085 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
CLI 0.32.2:
CLI from this PR:
|
7e8cc09
to
cbdb3b0
Compare
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)configuration.schema.json
updated if new parameters are added.What kind of change does this PR introduce?
This PR should make it easier to recover from soft-bricked boards with native USB (in cases where the serial port is unavailable because the bootloader has a too-short timeout).
What is the current behavior?
Trying the upload without a port selected would cause the upload to immediately fail, without leaving any room for the user to synchronize with the upload by tapping the reset button. See #1943 for more details.
What is the new behavior?
The upload should wait a reasonable amount of time for the user to tap the reset button and make the bootloader avaiable.
Does this PR introduce a breaking change, and is titled accordingly?
No, in theory...
Other information
Fix #1943