-
• #2
Google: Brownout detector was triggered site:espruino.com
-
• #3
I know about those posts, but did you read my post? I have not had any power problem with this board running Micropython and regular Arduino code with the OLED Screen fully on and while connected to a WiFi Access Point. Meanwhile, with Espruino, I flash the firmware, without any of my code running, no displays, no wireless connections, it triggers the brownout detector. Is Espruino really that power-hungry? Just running the Espruino console requires more power than running a bunch of Micropython code, a display, and wifi at the same time?
-
• #4
I guess this is because Espruino for ESP32 checks and activates WiFi during boot.
-
• #5
Default ap and station is active - afaik.
-
• #6
Some dev boards us a too small ldo.
-
• #7
Is it possible to disable wifi at boot? And what does espruino do differently that causes wifi to use so much power that it triggers the brownout detector? As I said before, I have used this same setup before with Arduino and Micropython and never had problems with power, even with a high load as I mentioned in my previous reply.
-
• #8
Part 1
Part 2
Part 3
I'm trying to use Espruino on the ESP32 Heltec WiFI Kit 32 Board. But after flashing the board, the board keeps restarting, saying brownout detector was triggered.
Usually when I plug the board in the console would show up and work, but after a few seconds, the brownout detector would get triggered and start boot looping.
Here is a snippet of the serial console output:
The thing is I never had this problem before. Previously, I was using Micropython and was able to run the OLED display and connect to a wifi network simultaneously with no power problems. What could be causing this?