Upload doesn't work anymore ! ESP too hot to touch ! Is it broken ?

[GeorgeFlorian1]

Hello !

Earlier today I tried using the ESP Wroom-32 with a P5 SMD 2727 LED Display and the following library:
https://github.com/NeoCat/ESP32-P3RGB64x32MatrixPanel

I've soldered the wires for that default constructor and tried uploading some codes to the ESP32.
Now, the board looked like this:
https://i.postimg.cc/tR6mRKZQ/20190329-164451.jpg

I've attached a power supply to it and used 2 LLC to shift the 3V3 accepted by the ESP32 to 5V needed for the LED Display to work.

https://i.postimg.cc/VkCHqbsd/20190401-135241.jpg

The RED (PIN 1) wire from the HUB75 is on R1 (IO25).

These are the specs of my power supply:

https://i.postimg.cc/prt2vnW7/20190401-145102.jpg

Here's the schematic to the whole board:
https://i.postimg.cc/PxXHWhh6/Schematic ... 160858.png

VCC = 5V

I noticed that I couldn't upload any code to the ESP32, because the boot button seemed like it did not work, so I took off the ESP from the board and uploaded the code than put it back in and noticed a bizarre behavior:

If the ESP32 is half-way inside (like this), the screen is white if I insert it all the way it get's red.

If I reset the ESP, the display will be off, and the Serial Monitor will output:

Code: Select all

rst:0x10 (RTCWDT_RTC_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371 
ets Jun  8 2016 00:22:57

repeating itself without stopping.

This began to make me think of the GPIO 12 that is a bootstrapping pin, but I thought if the guy that made the library used GPIO 12 than I can use it to.
https://github.com/espressif/arduino-esp32/issues/2626

The ESP ran around 1h with that error, which I think was actually the ESP resetting every second, made it go so hot that I couldn't touch it. I disconnected it at let it cool off only to realize that I can't upload code to it anymore.

I am now trying to upload code to the ESP, by having it connected to the PC via a USB Cable and keeping boot button pressed, but nothing happens.
Also it keeps getting very hot because the previous code is still making it reset itself.

Is there a way to check if the GPIO 12 is LOW or HIGH ?

Is the ESP broken ?

[idahowalker]

My guess is that the ESP32 is dead. How, I've no idea.

I had a collection of 7805's that would last a day or two then do some whacked out cht. I found ESP32's blow as quick as fuses. Since then I keep 1 ESP32 and one WROVER-B around as a spare.

[GeorgeFlorian1]

My guess is that the ESP32 is dead. How, I've no idea.

I had a collection of 7805's that would last a day or two then do some whacked out cht. I found ESP32's blow as quick as fuses. Since then I keep 1 ESP32 and one WROVER-B around as a spare.

Every ESP32 burns fast ? Is there any ESP32 that is more durable ?

I've tried erasing the flash using the esptool.py, but it couldn't connect to the ESP.

This is the command: esptool.py erase_flash

And this is the output:

Code: Select all

esptool.py v2.6
Found 2 serial ports
Serial port /dev/ttyUSB0
Connecting........_____....._____....._____....._____....._____....._____....._____
/dev/ttyUSB0 failed to connect: Failed to connect to Espressif device: Timed out waiting for packet header
Serial port /dev/ttyS0
Connecting........_____....._____....._____....._____....._____....._____....._____
/dev/ttyS0 failed to connect: Failed to connect to Espressif device: Timed out waiting for packet header

A fatal error occurred: All of the 2 available serial ports could not connect to a Espressif device.

[ESP_Sprite]

If you hook up the power supply of the ESP32 up to too high a voltage, it'll possibly blow indeed. The power supply specs in the data sheet are there for a reason. If you nicely keep within those specs, the ESP32s are durable as anything; we wouldn't sell the amount we would if they'd just went 'pop!' at random. Your power supply is a 5V one (and a quite hefty one at that), can I ask to which pin on the ESP32 board you connected it?

[GeorgeFlorian1]

If you hook up the power supply of the ESP32 up to too high a voltage, it'll possibly blow indeed. The power supply specs in the data sheet are there for a reason. If you nicely keep within those specs, the ESP32s are durable as anything; we wouldn't sell the amount we would if they'd just went 'pop!' at random. Your power supply is a 5V one (and a quite hefty one at that), can I ask to which pin on the ESP32 board you connected it?

It was connected to VIN.

Here's the schematic:
https://i.postimg.cc/PxXHWhh6/Schematic ... 160858.png

VCC = 5V

[ESP_Sprite]

Schematic checks out, from that I see no reason why your ESP32 acts weird...

[GeorgeFlorian1]

Schematic checks out, from that I see no reason why your ESP32 acts weird...

A user on github suggested to measure the voltage regulator that's on the ESP.

https://i.postimg.cc/ZnxrcQMb/esp-pin.jpg

From pin 1 to 2, there are 3.25V and from 1 to 3 there are 4.35V, both values measured when the ESP is connected to the PC using a USB Cable.

The new ESP32 arrived today and it has the same measured values of the Voltage Regulator as the old ESP. So I don't think either Voltage Regulators are broken.

I've measured the EN and BOOT buttons on both the Wroom-32 DevKitV1 and the new ESP that I just got, Wrover-B DevKitV4.

The measurements were done while the ESPs were connected to the PC using a USB Cable.

On the Wroom-32 DevKitV1:

- BOOT Button not pressed: 1.24V. Pressed: 0V
- EN Button not pressed: 3.3V. Pressed: 0V;

On the Wrover-B DevKitV4:

- BOOT Button not pressed: 3.3V . Pressed: 0V
- EN Button not pressed: 3.3V. Pressed: 0V;