Page 1 of 1
[CLOSED]"Brownout detector was triggered" failure on my ESP32
Posted: Sat Jun 27, 2020 5:37 pm
by Python Schlange
Hello,
I tried to upload my code, everything worked but when I opened the Serial Monitor, it showed me that Issue:
Brownout detector was triggered
ets Jun 8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:1216
ho 0 tail 12 room 4
load:0x40078000,len:9720
ho 0 tail 12 room 4
load:0x40080400,len:6352
entry 0x400806b8
PS: I tried to search a topic, but I just got a blank page so I started a new topic.
Re: "Brownout detector was triggered" failure on my ESP32
Posted: Sat Jun 27, 2020 5:50 pm
by lbernstone
Your USB port is not providing enough power. Try another port, or else you will need an external power source (perhaps a powered USB hub).
Re: "Brownout detector was triggered" failure on my ESP32
Posted: Sat Jun 27, 2020 5:52 pm
by ESP_Sprite
Also, suspect your USB cable. There are some with extremely thin conductors out there.
Re: "Brownout detector was triggered" failure on my ESP32
Posted: Sat Jun 27, 2020 5:57 pm
by Python Schlange
Sorry for the whole topic, just realized I had got the wrong Uploadspeed (921600)
.
Changed it to 115200 and everything is working
Re: [CLOSED]"Brownout detector was triggered" failure on my ESP32
Posted: Sat Jun 27, 2020 6:16 pm
by ESP_krzychb
Hi Python Schlange,
Upload speed should not be the issue. This message is reported when voltage supplied to the chip gets too low. A spike below the brownout voltage (I believe default is 2.44 V) is enough to trigger this error. If you see this message again try replacing power supply, USB cable, install capacitor on power supply terminals of your module, etc.
Also refer to
https://github.com/nkolban/esp32-snippets/issues/168 for related discussion.
Re: [CLOSED]"Brownout detector was triggered" failure on my ESP32
Posted: Wed Mar 22, 2023 4:35 am
by Arav24
Im having the same issue, Does this problem impact NVS storage?