Mohan Deb asked 4 years ago
I was working on a simple debounce test and inadvertently connected the 5V to the ground pin (I think). I may have connected to GPIO12 maybe. Before long I also had the 5V in connected to the 5V from the power source. The board did not power up. So I removed the wires and then things went south.
Now I just get this in the serial monitor.
rst:0x10 (RTCWDT_RTC_RESET),boot:0x1f (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57
Hard reset also does not seem to work.
% esptool.py –chip esp32 –port /dev/tty.usbserial-A50285BI –baud 115200 –before default_reset –after hard_reset erase_flash
esptool.py v2.8
Serial port /dev/tty.usbserial-A50285BI
Connecting…….._____….._____….._____….._____….._____….._____….._____
A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header
Did I fry my board?
How do I pull. pin 12 to low if I have messed that up?
Sara Santos Staff answered 4 years ago
Hi.
If you’ve connected 5V to GND, you’ve fried your board. However, if that was the case it wouldn’t even be found by your computer.
That error means that the ESP32 is not in flashing mode when you try to upload code. When you start seeing those dots, you need to press the on-board BOOT button.
Learn more about that here: https://randomnerdtutorials.com/solved-failed-to-connect-to-esp32-timed-out-waiting-for-packet-header/
Let me know if this helps.
Regards,
Sara
Mohan Deb answered 4 years ago
Thank you very much Sara. I have looked up the issue in detail and tried to recover the problem. It is a hardware issue now. The board is not fried completely but just the reset. I will have to do some hardware solution on this. It is much easier to just buy another board than spend my time fixing it. I can do some hardware fixes but the effort on these are too much to do. 🙂
Sara Santos Staff answered 4 years ago
Hi.
You can try to fix it “just for fun”.
But it would be better to get a new one.
Regards,
Sara