Repository navigation
Show firmware update progress and results on the controller screen - #134
Open
zjwhitehead wants to merge 1 commit into
Open
zjwhitehead wants to merge 1 commit into
zjwhitehead wants to merge 1 commit into
Conversation
This branch has not been deployed
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.
Firmware updates started from Android or iOS previously left the normal flight screen visible. This adds a full-screen update flow with preparation, progress based on bytes successfully written, verification, automatic restart, and readable failure states. After reboot, a brief completion screen shows the running firmware version.
The existing BLE UUIDs, command/sector formats, and acknowledgments are preserved. Screen updates stay in the UI task, progress redraws are limited to 4 Hz, and button gestures are consumed during the update/result screen. A persisted target-slot receipt distinguishes successful startup from rollback.
Screenshots
Rendered from the production LVGL screen at the device's 160 × 128 resolution, enlarged for review.
Light and dark themes, including error states
Validation
Need help on this PR? Tag
@codesmith-botwith what you need.