Skip to content

Firmware downloads page (staged, do not merge yet) - #25

Draft
bdbarnett wants to merge 9 commits into
mainfrom
firmware-page-staged
Draft

bdbarnett wants to merge 9 commits into
mainfrom
firmware-page-staged

Conversation

@bdbarnett

Copy link
Copy Markdown
Contributor

The page for flashable OmniPython firmware: a board picker, an Install button (ESP Web Tools, vendored), the generated esptool steps, the erase warning, and the desktop interpreters from the newest pydevices final that carries them.

It is held on this branch so it is not served: the site publishes main. Preview it with python3 -m http.server 8000 from a checkout of this branch and open http://localhost:8000/firmware/. The data is a staged set built from preview pins; merging it puts the page at /firmware/ (still unlinked).

Data is laid out by micropython-pydevices' scripts/stage_firmware_page.py.

… generated steps, desktop interpreters

Not linked from anywhere. The data is the staged set staged-20261020 (preview pins);
firmware/vendor/esp-web-tools is ESP Web Tools 10.4.0 unmodified.
Images print a real version in sys.version (v1.30.0-preview.160...), board builds leave out the desktop-only files, and CircuitPython images carry asyncio. The check step says what the version looks like.
CircuitPython images print 11.0.0-alpha.1 with no -dirty, and the CircuitPython check step now says what the version string starts with.
Pick a .bin or .uf2 you built and the page writes it the way it writes
the release builds. A .bin gets a chip choice, preset from the image
header, and the release manifests' offset: 0x2000 for a merged ESP32-P4
image, 0x0 for the S3 and for any whole-flash image. The page builds an
ESP Web Tools manifest as a Blob URL whose part is a Blob URL of the
file, and hands it to the vendored install button, which resolves blob:
manifests and parts as they are. Chips outside BROWSER_INSTALL, and
browsers without Web Serial, get the esptool steps with the file's name.
An application image is refused, since it would boot-loop at the
bootloader offset. A .uf2 gets the copy-to-drive steps. Both show the
mpftp line for flashing from a terminal.
The page gave every non-ESP board the RP2 UF2 steps, and listed no Wi-Fi image. The GIGA now gets dfu-util steps, Wi-Fi firmware first, as the flash guide has them, with the notes about the Wi-Fi image and the ROMFS libraries.
@bdbarnett
bdbarnett force-pushed the firmware-page-staged branch from 867dbd1 to 8d9b4e1 Compare November 15, 2026 13:53
@bdbarnett

Copy link
Copy Markdown
Contributor Author

Rebased onto current main (it was seven commits ahead and 42 behind) with no conflicts. The merge commits dropped out; the branch is now seven commits on top of main.

I served the branch with a local web server and drove /firmware/ in Playwright's Chromium. Nothing was flashed, and I didn't press Install or open a serial prompt.

What I saw: the page loads with no console or page errors, and the board picker lists 9 boards. Picking a board shows its Install button and steps. In "Install from a file":

  • Choosing the staged P4 .bin reads the chip from the file's header ("for the ESP32-P4, written at 0x2000"), shows the Install button and three steps with the esptool and mpftp commands.
  • The S3 .bin gives "ESP32-S3, written at 0x0" the same way.
  • Overriding the chip to the wrong one says the file was built for the ESP32-S3, not the ESP32.
  • A .uf2 hides Install and shows the bootloader-drive steps plus the mpftp command.
  • A junk .bin says it doesn't look like ESP32 firmware, a .txt says to pick a .bin or .uf2, and clearing the file hides the output again.

The style check passes. Not verified: the actual WebSerial connect and flash, which needs a board and a person at the browser prompt. Left unmerged.

…cuctl (#254)

The page threw on a set built after the pins moved to DEPENDENCIES.lock
(firmware.json has one entry per pin, not UPSTREAM, deps.lock and modules.lock),
so the board list never loaded. The verify line, the ELF and map links and the
flash guide still named micropython-pydevices; the files are attested by, and
the Release lives in, PyDevices/omnipython-builds. The terminal install text
said mpftp, which is mcuctl now.
…e GIGA's ROMFS image, where each build keeps its files (#255)

This branch has not been deployed

No deployments
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