ESP32 "Brownout detector was triggered"
The chip measured its supply voltage falling below a safe level and reset itself. The problem is in the power supply, and it shows up most when WiFi starts.
E (412) BOD: Brownout detector was triggered ets Jun 8 2016 00:22:57 rst:0xf (RTCWDT_BROWN_OUT_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
If the voltage drops fast, only part of the message makes it to the console, or none of it, and the next boot shows the brownout reset reason.
Why it happens
The ESP32 draws short current peaks of several hundred milliamps when its radio transmits, most of all when WiFi connects. If the supply cannot deliver them, the voltage at the chip dips and the brownout detector resets it, often in a loop: boot, connect, dip, reset.
Fix the supply
- A better USB cable and port. Long, thin cables and USB hubs are the most common cause on the desk.
- A capacitor close to the module: a bulk capacitor (tens to hundreds of microfarads) between 3.3 V and GND next to the module carries the peaks.
- A regulator that can deliver the current, with its input not sagging either. Some cheap boards use regulators that are at their limit.
- On batteries: a battery near empty, or long thin wires to it.
Turning the detector off (CONFIG_ESP_BROWNOUT_DET) does not fix anything: the chip keeps running on a voltage where flash reads and the radio can fail, and the failures get harder to explain.
A device that browns out only at a customer's site, on their power supply, shows up in Pinscope as restarts with the brownout reason, per device: health monitoring.
Related errors: rst:0x… reset reasons · Task watchdog got triggered · Interrupt wdt timeout · Cache disabled but cached memory region accessed. All ESP32 errors: the list. Messages and causes from ESP-IDF's panic handler and Espressif's Fatal Errors guide.
More
- Remote access to an ESP32 without TLS: what it measured and what it costs
- Reaching an ESP32 web server from outside its network
- Updating ESP32 firmware over the internet, with rollback
- Guru Meditation Error: decoding the backtrace, and crashes from the field
- Remote logging: ESP_LOG without a serial cable
- Heap and stack monitoring in the field
- An ESP32 behind CGNAT, 4G or Starlink
- TLS memory usage on the ESP32, and how to reduce it
- Sharing an ESP32 sensor page with anyone, without port forwarding
- ArduinoOTA over the internet, with a rollback
- ESP32 remote access compared: port forwarding, ngrok, Cloudflare Tunnel, Tailscale
- esp_http_server slow? The 250 ms delay and the fix
- Before the first ESP32 ships: a field support checklist
- ESP32 exception decoder: a Guru Meditation backtrace to lines, in the browser