A fatal error occurred: Timed out waiting for packet content on custom PCB

[ryanc550]

Hello! I'm currently testing a custom PCB with the ESP32-WROOM-32D module. After trying to upload code to it using the Arduino IDE and an FTDI breakout, I get this error:

esptool.py v2.6
Serial port COM7
Connecting........_____....._
Chip is ESP32D0WDQ5 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
MAC: 34: ab:95:8d:c3:ec
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 512000
Changed.
Configuring flash size...
Warning: Could not auto-detect Flash size (FlashID=0xffffff, SizeID=0xff), defaulting to 4MB
Compressed 8192 bytes to 47...

A fatal error occurred: Timed out waiting for packet content
A fatal error occurred: Timed out waiting for packet content

It seems to be communicating because it identifies the chip correctly, but then it breaks. Does anyone know how to resolve this? I have attached the ESP32 part of the schematic to this post in case this is useful. Thank you for any help!

[ESP_Sprite]

Something's wrong with communication with the flash chip. Check pin 17-22 on the module, see if those aren't accidentally bridged or shorted to something.

[ryanc550]

Thank you for the quick response! I checked pins 17-22 with a multimeter and with magnification, and those pins don't seem to be shorted together or to anything. I also made sure GPIO2 (pin 24) was connected to ground since that seemed to work for other people with the same problem, but that did not solve mine

[ryanc550]

I just wanted to update that it works properly now. If anyone else has the same problem, try setting the Flash Mode to DIO in Tools > Flash Mode

[ESP_Sprite]

FYI, that still indicates something is wrong on pin 17 or 18... DIO doesn't use these pins, while QIO does. If this workaround works for you and you're happy with the reduced speed, there's no harm in continuing to use this, but a Wroom module should be able to do QIO no problems.