feat: USB companion firmware flasher (dashboard + esptool)#85
Open
iceice400 wants to merge 1 commit into
Open
Conversation
|
Sweet! Can't wait for this one! No more climbing on the roof to upgrade the firmware on a USB MeshCore companion. |
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.
Summary
.bin, confirm viaDangerousModal, runesptoolwith live log stream on authenticated WebSocketPart of Master PR Roadmap #14 (FR3 Field Operations). PRs 15–16 (remote ADMIN config) follow after merge.
Risks / notes
0x10000— verify for your board firmware layoutTest plan
python -m unittest tests.test_firmware_flasher -v(6 tests, pass).binon RAK7248 + Heltec MeshCore companionfirmware_flashwith duration and exit codeAI-assisted
PR description and implementation assisted by Claude. Code reviewed against Meshpoint patterns (
DangerousModal,timed_action,_gate_ws_or_close).