Flash firmware
Connect your radio to get started.
The radio’s USB port changed. Click below and choose the same physical radio.
Firmware downloads automatically. No folders to copy.
Flash another device, or optionally verify the previous radio’s startup.
Restart the radio for backup
Firmware
Custom firmware file or URL
Choose the original BIN, ZIP or UF2 file on this page. Its type and write layout are inspected automatically. Keep ZIP files zipped—no extracting, folders or copying onto the radio.
Unified firmware replaces separate storage and serial-port builds. Ethernet uses full sensors by default. Older files remain available for existing installations.
Step 2.5: Choose a firmware build to continue.
Manual downloads — optional
Not needed to flash on this page. If you choose a ZIP on this page, keep it zipped. Do not drag folders onto the radio.
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.
Community presets from api.meshcore.nz, or enter custom values.
Use settings appropriate for your radio and region. Unsupported settings are rejected by the firmware.
MediaMesh requires radio2 support. Standard presets set crossing to Off; custom MediaMesh lets you choose crossing.
Keep this tab open during flashing. An optional saved copy lets you reload these exact customized bytes if a transfer is interrupted.
Bootloader/component writes can make USB recovery unavailable. This is not an application update. No offset or compatibility is inferred from the filename; confirmation includes the exact address.
No backup will be created. Firmware and device checks still run before the final flash confirmation.
Waiting for an image and a selected USB port.
DFU stopped: what to do next
- Keep power and USB connected. The update may be incomplete; neither the old nor the new firmware is confirmed to start. The flasher sent no further reset or flash after the error; the radio may restart on its own.
- Close other serial terminals and apps using the radio.
- After the transfer has stopped, check the USB connection. If needed, try a known data cable connected directly to the computer.
- If this is a standard RAK4631 with the Adafruit-compatible bootloader, double-press its RESET button to enter bootloader mode. A RAK4631-R or a different installed bootloader may need different steps.
- Choose the same physical radio's DFU USB port. Keep or reselect the exact validated ZIP for the interrupted operation and your board, inspect it again, and review the operation before choosing to retry. This error alone does not call for an erase or bootloader replacement.
Identify the exact interrupted operation and check the radio's state before choosing any reset or retry. For a bootloader or SoftDevice change, do not reset or retry until its state has been assessed; ask for help if unsure.
If an erase or recovery step was already pending, follow the retained recovery instructions for that step. An acknowledged packet does not verify the flash or prove startup.
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.
Common settings
Connect the radio’s application USB port to change settings.
Configure Wadamesh
Choose only the settings you want to change. The radio settings may require a restart; the page does not restart the radio automatically. Check the settings for your region.
Presets fill the primary radio fields only. Other network settings, including path hash size, are not changed.
Community presets from api.meshcore.nz, or enter custom values.
Standard MediaMesh presets set crossing to Off. Choose custom MediaMesh to change crossing.
No settings have been changed.
Channels
Read the pager's channels, then choose one to edit. Channel keys are hidden; leave the key blank to keep it.
A new channel key must be 32 hexadecimal characters. Channel names and keys must match those used by your peers; renaming does not change the key.
Use this for simple ASCII hashtag channel names. For private channels enter the key manually; configure special #r2 channels on the pager.
Removing a channel clears its slot and stored key.
Read channels to get started.
Contacts
Read contacts, then choose one to rename. A later advertisement from the contact may replace this name.
Removing a contact also removes its associated stored data and chat thread.
Add a contact
Read contacts to get started.
Automatically add contacts
Choose which newly heard nodes are added to Contacts.
0 means no limit; 1 means direct only; higher values allow up to one fewer hop than the number entered.
Read auto-add settings to get started.
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.
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.
Read INFO_UF2.TXT · optional, only if a drive is mounted
No mounted drive? Choose Hardware instead. Serial DFU flashing needs no drive.
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.
nRF52 erase & DFU options
The final image is validated before erase. Wipe requires its own acknowledgement, separate from a board override. After erase, select the same physical radio’s DFU serial interface; no mounted drive is used.
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.
Download exact migration artifact ↗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.
Installed bootloader version has not been checked.
Back up first. A bootloader update may require reinstalling the matching application.
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.
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
Prepare update downloads and validates the selected image.Public release metadata. Firmware bytes are validated separately.Backup & startup preferences
Backup & restore
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 ↗