How g3gg0/esp32_flasher works
This browser-first ESP32 toolkit lets users inspect or edit firmware images, or connect to hardware to read and flash device memory. The viewer workflow loads an image or connects live, parses boot and partition metadata, and exposes binary/NVS/FAT views and editing tools; the flasher workflow synchronizes with the bootloader and transfers flash data. The parser also supplies a lazy sparse-image cache for efficient reads and writes. Feature-level links rely on README statements where source excerpts do not show the UI wiring.
Main entry points: flasher.js Bootloader protocol · esp32-viewer.html Firmware viewer · esp32-parser.js Image parser · flasher.html Flasher interface
Components 12
Firmware inspection
- Firmware viewer
esp32-viewer.html
Image parsing and editing
- Image parser
esp32-parser.js - Sparse image cache
esp32-parser.js - NVS and filesystem
esp32-parser.js
Device flashing
- Flasher interface
flasher.html - Chip profiles
chips.js - Bootloader protocol
flasher.js
Device transport
- Serial adapter
flasher.js - WebUSB transport
flasher.js
Other components
- Engineer
- Firmware image
- ESP32 device
Connections 13
- Engineer → Firmware viewer: opens
README.md - Engineer → Flasher interface: opens
README.md - Engineer → Firmware image: loads
README.md - Firmware viewer → Image parser: parses image
README.md - Firmware viewer → Sparse image cache: edits cached data
README.md - Image parser → Sparse image cache: reads through
esp32-parser.js - Image parser → NVS and filesystem: parses partitions
esp32-parser.js - Flasher interface → Bootloader protocol: controls flashing
README.md - Bootloader protocol → Chip profiles: uses profiles
flasher.js - Bootloader protocol → Serial adapter: communicates via
flasher.js - Bootloader protocol → WebUSB transport: communicates via
README.md - Serial adapter → ESP32 device: transfers flash
README.md - WebUSB transport → ESP32 device: transfers flash
README.md