LIBRARYFlashing firmware.

Flashing is how your compiled program gets into the microcontroller. The ESP32 enters its bootloader over USB, a tool sends the binary across, the tool writes it into flash, and the next reset runs it. That load-and-go loop is the same every time you hit upload, and understanding it turns most flashing problems from mysteries into checklists.

From source to binary

Your code compiles to a binary image: the exact bytes the chip will execute. Flashing writes that image to a fixed address in the ESP32's flash memory, where it survives power-off. On the next reset, the tiny bootloader baked into the chip's ROM finds the image, loads it, and jumps into it. Change your code, recompile, reflash, and the loop repeats.

The bootloader and esptool

To accept a new image the chip must be in download mode, set by the boot strapping pin from the last lesson. Then esptool, Espressif's flashing tool, talks to the ROM bootloader over USB or a serial UART and streams the binary in. The ESP32-S3 has native USB built into the chip, so it can be flashed straight over a USB-C cable with no separate USB-to-serial part in the path at all.

Addresses, partitions, and erasing

Flash is divided into partitions: the second-stage bootloader, a partition table that maps the rest, your application, and often a data area for stored settings. Each lives at its own address, which is why a flash command usually lists several files with offsets. Erasing flash wipes all of it back to blank, which clears a bad image or stale stored data so you can start from a known-clean chip.