Blog
ESP32 Firmware and Data: Flash Partitions, Files, and Reading
Firmware, partitions, and the files hiding in your flash: what to flash, where it goes, how to read it back out. The browser simulator mirrors the same layout.
How to Read from ESP32 Flash Partition in C?
Use the esp_partition API: esp_partition_find_first() locates a partition by type and label, esp_partition_read() copies bytes out, and you’re reading flash from C without esptool. Addresses are relative to the partition start, not the flash. Asking how to read esp32 partition table usually means esptool.py read_flash 0x8000 0x1000 pt.bin decoded with gen_esp32part.py.
How to Flash ESP32 Firmware?
Firmware in the strict sense is the app image: esptool.py write_flash 0x10000 firmware.bin. Note 0x10000, not 0x0 — flashing an app at 0x0 is the classic silent-boot-loop mistake, and I’ve made it.
How to Flash BIN File to ESP32?
A .bin is just firmware in a file, so the command is the same write_flash with the offset that matches what the file is: 0x1000 for a bootloader, 0x8000 for a partition table, 0x10000 for an app. Merged factory images from Espressif installers are the exception, starting at 0x0. Wrong offset: boot loop, and the upload reports success.
How to Download a File from a Server ESP32 Arduino?
HTTPClient: http.begin(url), http.GET(), read the body. That’s how to download a file from a server esp32 arduino in ten lines, and the same client does POSTs when you need the reverse — how to send data from esp32 to server. For firmware, use the Update class instead: Update.begin(size) then Update.writeStream(stream) installs a .bin safely. The classic gotcha is TLS: HTTPS needs a root certificate; a missing one looks like a network problem. Plain HTTP mostly works on your LAN.
How to Extract Code from ESP32?
Source, no — machine code, yes. esptool.py read_flash 0x0 0x400000 dump.bin pulls the entire flash, and the same command answers how to read code from esp32: the bytes are there, the readable source isn’t. To identify a firmware image without a board, esptool.py image_info reports chip and flash mode — that’s how to determine esp32 firmware builds.
Does ESP32 Have EEPROM?
No physical EEPROM — it’s emulated in flash. EEPROM.h and the Preferences library both write to the NVS partition, a small key-value area in SPI flash. Practical answer: yes, paid for in flash endurance instead of a dedicated chip. Wondering how to clear eeprom esp32? Preferences.clear() does it in one call.
What lives where on the flash?
Default 4 MB layout: bootloader 0x1000, NVS 0x9000 (Wi-Fi credentials, settings), app 0x10000, data filesystem toward the end. The partition table at 0x8000 is the map — our knowledge base has the full reference by board.
How do I dump the whole flash?
esptool.py read_flash 0x0 0x400000 backup.bin on a 4 MB chip, with --verify to check it came back intact; restore with write_flash at the same offsets. A full dump is the only real safety net before experimental firmware — I keep one before every board I plan to abuse, and it has rescued two of them.
SPIFFS or LittleFS?
LittleFS: faster, survives power loss better, and ships with the Arduino-ESP32 core. SPIFFS is legacy, still fine for static data, and both upload with the same Sketch Data Upload plugin. The official docs are vague about migration, so format the new filesystem on first boot and copy files over.
Can I update firmware over Wi-Fi?
Yes — OTA. The Update class takes the same .bin stream from the server-download answer and writes the OTA partition while the app runs. That’s the practical route to how to access esp32 from anywhere — the device phones home instead of you port-forwarding. app.sensbench.com tests the flow in a browser.
Persist It, Prove It — In Your Browser
Both persistence tiers have runnable examples here: microSD on ESP32 mounts, writes, lists and reads back with full serial output — and the I2C EEPROM test shows the write-verify loop byte by byte. Watch what survives a re-run before you design your real flash layout.