ESP32 troubleshooting
ESP32 keeps rebooting in a boot loop
Use serial output, power checks and a minimal sketch to identify repeated ESP32 resets.
Stop if you notice a swollen battery, burning smell, exposed mains wiring or liquid inside powered electronics. Protect important data before resets, firmware changes or recovery work.
Where this problem appears
ESP32 development boards powered by USB or an external regulated supply.
Symptoms to confirm
- The serial monitor repeats the boot message.
- The board resets when Wi-Fi, a motor or a sensor starts.
- A new sketch uploads but never reaches the main loop.
Likely causes
- The USB cable or power supply drops voltage under load.
- A peripheral pulls too much current or disturbs a boot strapping pin.
- The sketch triggers a watchdog, exception or memory failure.
- Flash contents or board settings do not match the hardware.
Work in order
Step-by-step fix
- 1
Disconnect motors, relays and external modules, leaving only USB power.
- 2
Use a known data-capable USB cable and a stable computer port.
- 3
Open the serial monitor at the baud rate shown by the project and capture the full reset reason.
- 4
Upload a minimal blink or serial sketch using the correct board and flash settings.
- 5
Reconnect peripherals one at a time while monitoring the supply voltage.
- 6
Move devices away from boot strapping pins and power high-current loads separately with a shared ground.
- 7
If flash errors continue, erase flash and upload a minimal verified project before restoring the application.
If the main path does not work
- Lower Wi-Fi transmit power only as a diagnostic if resets begin during radio activity.
- Use a powered USB hub or regulated bench supply to test for brownout.
How to reduce repeat failures
Budget current realistically, decouple the supply near the board and log reset reasons during development.
Common questions
Is this safe for a beginner?
Some steps require careful technical judgment. Stop before powered disassembly, battery work or wiring changes if you are not experienced.
How long should the checks take?
The typical diagnostic window is 30-60 minutes, although drying time, updates and intermittent faults can take longer.
What should I record before contacting support?
Record the exact device model, software or firmware version, the full message shown, when the problem began and which steps changed the behavior.
Reader notes
Did this solve the problem?
Share the device model and the step that changed the result. Comments are reviewed before publication.
No published reader notes yet.