Skip to content

Firmware page: download mode and port-finding, the GIGA's ROMFS image, where each build keeps its files - #255

Merged
bdbarnett merged 1 commit into
firmware-page-stagedfrom
firmware-page-usb-giga-fs
Nov 18, 2026
Merged

bdbarnett merged 1 commit into
firmware-page-stagedfrom
firmware-page-usb-giga-fs

Conversation

@bdbarnett

@bdbarnett bdbarnett commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

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 -v from 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-files zip 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_ports IDs come from the boards on my bench).

…e GIGA's ROMFS image, where each build keeps its files
@bdbarnett
bdbarnett merged commit 9f5c0d4 into firmware-page-staged Nov 18, 2026
1 check passed
@bdbarnett
bdbarnett deleted the firmware-page-usb-giga-fs branch November 18, 2026 04:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant