Repository navigation
Firmware page: download mode and port-finding, the GIGA's ROMFS image, where each build keeps its files - #255
Merged
Conversation
…e GIGA's ROMFS image, where each build keeps its files
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.
Three things a newcomer trips on, found flashing a T-HMI from this page.
Native USB. The page told you how to enter download mode only for the T-Embed S3 and the LCD-7's native port, and said the COM number can change without saying how to find the new one. Every ESP32 board now has a download-mode step: for boards whose only USB port is the chip's own (T-Embed, T-HMI and the other octal and quad S3 boards, Qualia, T-Watch, P4X-EYE) it says to do it before writing; for boards with a UART port it says to use that, and to do the same for the native one. It gives the BOOT and RESET sequence (and the unplug-hold-plug variant), how to see the port change (
python -m serial.tools.list_ports -vfrom the esptool venv: 303A:1001 in download mode, 303A:4001 running; Device Manager on Windows,ls /dev/ttyACM*on Linux,ls /dev/cu.usbmodem*on macOS), and that a native-USB board can stay in download mode afterwards: press RESET or add--after watchdog-reset.GIGA. The steps and file table left out the ROMFS image that the Release notes say to write with every update. The steps now write the Wi-Fi image, then the ROMFS image, then the main firmware, as the notes do, and the table lists the ROMFS image and the
romfs-fileszip with their sha256.Filesystem. Each build now shows where it keeps its files and says that a board that ran a build with the filesystem elsewhere comes up empty, so copy files off first. The page can't know what your board ran before, so it says what this set does and what to do about a difference.
I served the page over the staged-rehearsal-20261118 firmware.json (16 builds) and asserted the text of every build with Playwright. The check failed for the ESP boards before the change (no download-mode and port text, no filesystem note) and passes on all 16 after it, with no page errors. Not tested: the Install button, and the new commands on a board (the
list_portsIDs come from the boards on my bench).