Choose a USB port to detect your board. Nothing is flashed automatically.
No USB port selectedBoard and role are detected after connecting.
Not connected
Firmware
Step 2: Installation
Radio & MediaMesh settings · optional

Editable builds can carry factory defaults. Other builds receive settings over USB after startup verification. MediaMesh settings are applied after flashing.

Load a build to choose primary radio and MediaMesh settings. No radio is accessed by this check.

Waiting for an image and a selected USB port.

Firmware details

Step 3 offers a backup by default. Select Skip backup to go straight to step 4; firmware and device checks run automatically before confirmation.
Step 4 asks once for supported expansion + final firmware, then completes both automatically. A new USB interface may still need step 1.

Update preserves settings. Erase & new install deletes them.

Keymind Cascade is selected by default. Matching hardware and firmware are selected after connecting.

Loaded imageNo image loaded

Common settings

Connect the radio’s application USB port to change settings.

USB logging

On may switch Companion USB from binary to text mode.

Wi-Fi

Changes may restart Wi-Fi or need a reboot.

Wi-Fi network

Leave blank to keep the saved password.

These buttons keep passwords out of the console.

Serial console & operation log

Commands and output stay in this tab.

Mesh Firmware workbench ready.
No hardware operations have been performed.
Pet tracking

Connect a RAK WisMesh Tag running the combined Keymind Cascade Sensor or USB tracker Companion firmware. Choose its USB port to read or change the collar.

Pet tracking guide

Home boundary

Use one point for a circle, two opposite corners for a box, or 3 to 9 points around a polygon.

Return-home tune

Enter up to eight notes separated by commas. Use 0 Hz for a rest. Playback repeats outside the boundary and stops on return.

Hike mode

Either owner phone can keep the collar nearby. When both disconnect, the collar waits before switching to lost mode.

Owner phones

Choose a slot and enroll. On the phone, connect to Pet Collar in nRF Connect for Mobile, accept pairing, and write the six digits as text to the characteristic whose UUID starts with CAA50002. Keep the app connected for the hike.

MeshCore radio and tracking

Set the collar and owner radio to the same frequency, bandwidth, spreading factor and coding rate. Pause tracking before changing these settings.

Choose the collar's USB port, then read its settings.
Reader books

Advanced options & troubleshooting
Connection & automatic setup

Connection method is selected automatically after the running node is identified.

After you choose a port, read-only detection selects matching hardware and firmware choices. It never flashes a device. Turn off Automatic setup to choose everything manually.

The browser still requires you to choose a port after reconnecting. Ambiguous hardware or connection methods remain manual.

USB reconnect trouble · virtual machines & older firmware

If the bootloader port disappears, pause VMs configured for USB auto-capture, or disable that radio's automatic VM passthrough before retrying. A VM may claim the newly enumerated ROM/DFU device; do not assume it will be returned after 30 seconds. The page cannot reclaim USB from a VM or restart a Windows driver. Re-select the same radio after the host regains it.

Some older ESP32 TinyUSB firmware stalls during bootloader entry on a direct Windows root USB port. A USB hub or another port routed through an internal hub can help. No administrator CLI command is part of the browser workflow. Never interrupt an active partition-migration bridge merely because it temporarily disappears.

Full Companion text mode

Use only for a running Full Companion in text mode. Binary handoff may turn USB logging off. nRF52 flashing uses its serial DFU port, not a mounted drive.

Partition migration artifacts · optional/offline

Required migration files download automatically for supported current releases. These file choices are only for offline use or a failed automatic download. Choose the original ZIP—do not unzip it or copy its folders onto the radio.

If the release host blocks browser downloads, select the matching ZIP here. Never substitute a Wi-Fi-only bridge.

Verification, retry & migration controls
Interrupted ESP32 write

A retry keeps the exact image and chip MAC, needs a new port selection, and never resets automatically. Discarding its retry record does not undo on-device writes or clear a pending partition migration.

Board bootloader · our latest stable OTAFIX

Recommendations use our latest stable release's exact-board manifest. Select matching hardware or an explicit artifact. nRF52 uses the serial DFU ZIP, never a mounted drive. Recovery builds remain separate.

Temporary R_ recovery bridge · advanced

Choose the currently installed bootloader profile, not the physical target board. Recovery retains that identity and relaxes board guards. Install the normal bootloader next; never leave recovery installed.

Detection can select a unique reviewed DFU USB hint or an exact supplied identity. Shared identities need manual selection.

Download recovery bundle ↗

A DFU match identifies an installed bootloader hint, never the physical board or its bootloader version. For a RAK4631 showing GAT562BOOT, match gat562 first, then choose the normal RAK4631 bootloader manually. Both the bundle and selected inner ZIP are hash-checked. Flashing still needs separate recovery, board and wipe acknowledgements.

Image details, download & hash override
OPERATION—
IMAGE SIZE—
Prepare update downloads and validates the selected image.
Download firmware ↗
Public release metadata. Firmware bytes are validated separately.
Backup & startup preferences
Backup & restore

Export settings without flashing, or restore to the same board or deliberately move to another.

Backup interface override - normally automatic

Save and verify node settings, then use Import JSON to restore them. Each backup lists any values not captured. Firmware/bootloader images, stored messages and runtime logs are not included. Keep the JSON private; backup requires the application port, not ROM/DFU.

Ripple standalone backup

Keep Ripple running normally. Back up Ripple reads and verifies its private identity over built-in ESP32-S3 USB, then restarts the device normally. Use desktop Chrome or Edge. If direct USB is unavailable, select the Ripple folder from its SD card.

USB captures the verified key and firmware information. Adding SD files also preserves original contacts, channels and preferences as files. Maps and recorded tracks are excluded. Files stay on your computer. Restore the identity over USB to a MeshCore companion or Wadamesh, or download a Wadamesh identity file for its on-device Import settings.

Wadamesh settings backup

Select the running device's application USB port, then back up its identity, channels, contacts, radio, position, BLE PIN and other supported mesh settings. Import this JSON to restore over USB with readback checks.

For display, keyboard, Wi-Fi and other preferences unavailable over USB, add the original meshcomod folder from SD, or an exported prefs folder from internal storage. Download saved files and copy them back while the device is off, using the same device and storage layout. Maps, message history, tracks, logs and oversized files are excluded. Backups stay on your computer and contain secrets.

The Wadamesh settings download works with its on-device Import settings: identity, name, radio, position, channels and contacts. Keep the browser backup for USB restore of contact routes, repeat, path hash, BLE PIN, telemetry and other captured settings.

Preview status & browser limitations

Hardware preview · One Heltec V4.3 OLED bench radio completed a Chrome application update, TinyUSB handoff, MD5 readback and application startup verification. Other boards, nRF52 flashing, erase/new installs, partition migration and browser crash/reload recovery remain unverified. Use a recoverable bench device first.

Direct on this page

ESP32 write-only updates, merged installs, explicit-offset components, chip/MAC/security checks and target MD5 readback; legacy Adafruit nRF52 application/bootloader/SoftDevice serial DFU ZIPs (no drive needed); UF2 copying for other supported boards; MeshCore companion backup/restore and script JSON import; supported CommonCLI settings backup/restore through serial commands; reviewed ESP32/C3/S3 USB partition migration.

Requires your permission

Use desktop Chrome or Edge with Web Serial. Port selection, reconnects and downloads remain explicit. CH340 and other UART bridges use the OS serial driver; the page cannot install it or change Raspberry Pi USB speed. Firmware hosts may require Download → local file because of CORS.

Explicit limitations

No unreviewed partition migrations or arbitrary commands from imported JSON. Unparseable and unavailable settings are reported, not replayed. Settings backups exclude firmware/bootloader images, stored messages and runtime logs; other uncaptured values are listed for each backup. A completed transfer is not proof of application startup.

Runtime: esptool-js 0.7.0 · Pyodide 0.29.3 (on demand) · Licenses and source attribution ↗

EXPLICIT AUTHORIZATION

Confirm operation

JSON backup has been downloaded

Flashing firmware

Starting firmware transfer…

Keep this tab open. Do not unplug the radio or turn off power.

100% means the transfer finished. Application startup is verified separately.

Flashing console