Repository navigation
Allow USB recovery boot without charging an unsafe battery - #366
Draft
TobiasRoeddiger wants to merge 1 commit into
Draft
TobiasRoeddiger wants to merge 1 commit into
TobiasRoeddiger wants to merge 1 commit into
Conversation
✅ Unit tests passed6 passed, 0 failed/error, 0 skipped — view workflow run
Download the |
Compiler warningsThe extended-warning build completed successfully. Application compiler warningsShow warnings |
|
Build output available: |
CodeChecker static analysis✅ No non-style issues found. |
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
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.
A battery rejected by the normal power manager can leave the application waiting before USB starts, making USB diagnosis and reflashing unavailable. Add an automatic USB-only recovery boot to the 2.3.0 FOTA configuration (release branch
2.2.10).Validation: full NCS 3.4.1 FOTA and non-FOTA builds passed. All 12 control-logic tests passed on the host with AddressSanitizer/UndefinedBehaviorSanitizer, including gauge/GPIO failures, threshold boundaries, USB removal and latched inhibition. The tests are also registered in the existing Unity/Twister suite.
Draft pending hardware validation: USB image listing/upload, unplug/replug, CD and battery-current measurements, and operation across the PMIC watchdog interval. No device was flashed. Charge inhibition begins in the application, not before MCUboot; the battery is not physically isolated. This cannot retroactively recover an old firmware that never starts USB. Details and the read-only
mcumgr image listcommand are indocs/usb-battery-recovery.md.