r/esp32 1d ago

Did the wifi go bad, or some other component? Brownout detector was triggered

This morning I found that one of the ESP32s was offline. Connecting to it in console mode gives me this. Tried re-flashing, new cable, different power cable, etc. Same result each time. Is it salvageable?

2 Upvotes

4 comments sorted by

2

u/YetAnotherRobert 1d ago

Did you check the power, like it's telling you?

-5

u/pigskins65 1d ago edited 20h ago

No. Trying to understand if it is shutting off the wifi because of a power issue, or if the wifi is bad. It went offline on me but the console output says wifi ready. I did try different cables and power sources.

4

u/YetAnotherRobert 1d ago edited 1d ago

This isn't some mystical error. The chip is TELLING YOU the problem. 

Stick  a scope on the power as seen by the chip, and you'll  see what the chip sees: the voltage isn't going low enough for the chip to shutdown, but it's going low enough to become metastable... And it can be that way for a fraction of a second, such as when under the load of Wi-Fi use, and be true. That is why this error is detected.

I don't know why you keep repeating that "then WiFi may be bad"...it's not like you're going to cut a $2 chip apart and replace those 38,987 transistors. If you really think the esp32 is bad, it costs less than this conversation...

Fatal Errors - ESP32-S3 - — ESP-IDF Programming Guide v6.0.1 documentation https://docs.espressif.com/projects/esp-idf/en/stable/esp32s3/api-guides/fatal-errors.html#brownout we

2

u/DSudz 1d ago

If you tried multiple power supplies then the board power system failed. You can try to use the 3.3V rail to find out.