TOOLS / ADVANCED USB FLASHING
Universal ESP flasher.
Your firmware. Your addresses. ESP32-family and ESP8266 targets supported by esptool-js 0.6.0—not every board or future chip is guaranteed.
MeshAutoResponder default login
Usernameadmin
PasswordESP32MESH
For initial setup, join Wi-Fi MeshAutoResponder-Setup using ESP32MESH, then open http://192.168.4.1/wifi in your browser.
These defaults are for the MAR device dashboard, not this flasher website. If you changed the web password, use your saved password. Change the default after setup.
1. Connect your board
Checking browser…
Use a USB data cable and close other serial tools. Connecting resets the board into its bootloader and temporarily stops its application. No flash is erased by connecting.
No device connected.
2. Add firmware files
Add bootloader, partition table, boot_app0, application, filesystem, or one merged BIN. Use the exact addresses supplied by the firmware publisher; they differ between chips and builds. Do not select both a merged image and its component files.
Files stay in your browser and are not uploaded. Maximum 16 files / 32 MB total. Addresses must be 4 KB aligned; overlapping erase sectors are rejected.
Flash capacity is detected automatically. Overrides affect recognized image headers at chip-specific boot offsets, not arbitrary data. Choose only values supported by your board.
Writing still erases the sectors occupied by each file. Wrong addresses or files can overwrite Wi-Fi credentials, calibration data or firmware. Back up first. For MAR settings-preserving updates, use its device portal.
No files written.
Operation log
Ready.
Help and limitations
This is a general-purpose flasher, not a firmware compatibility checker. It detects the chip and capacity but cannot verify your board wiring, firmware purpose, PSRAM configuration, or all security-fuse states. Do not use it on secure-boot/encrypted production devices. It does not burn eFuses.
If auto-connect fails, follow your board’s bootloader procedure (often hold BOOT, tap RESET, release BOOT). Try 115200 baud. After a failed flash, do not assume the old firmware remains usable; reconnect and reinstall the correct files. Never disconnect during erase or write.
Every image is checksum-verified against flash after writing; checksum success is not proof the application boots. Press RESET if automatic reset fails. No automatic retry or standalone erase is performed.