Before the first flash: an ESP32 bring-up checklist
Separate power, boot configuration, and serial communication before changing firmware.
Identify the actual device
ESP32 is a family name. Start with the exact chip or module, the board schematic, and the matching Espressif documentation. Pin assignments and boot behavior should not be copied from a different family member. The hardware references below cover the original ESP32; use the corresponding guide for an ESP32-S3 or another variant.
Check power and boot conditions
Espressif’s original ESP32 design guide recommends a 3.3 V supply capable of at least 500 mA when using a single supply. Treat that as a device-specific design recommendation, not a rating for every development board’s input connector. Check the module rail and enable signal during startup. External circuits on strapping pins can also change the selected boot mode.
Reduce the test
If flashing fails, temporarily remove application peripherals and establish a repeatable reset and download sequence. Confirm the serial interface and retain the complete tool error and boot log. A successful download followed by an application failure is a different observation from a device that never enters the download loader.
Keep a bench record
Record the board revision, supply arrangement, USB interface, selected target, and the smallest firmware that reproduces the problem. Change one variable at a time. This makes the next test useful instead of merely different.
Primary references
Read these alongside the exact device documentation. The workflow above is an editorial synthesis, not a report of a completed hardware test.