Fatal error: waiting for packet content

[DreamingRaven]

The Setup

OS: Windows 8.1
Using: Arduino IDE (Compilation and Uploading)
Sketch: Example "WiFiClient"
Board: "ESP32 Dev Module" (ESP-WROOM-32, ESP32D0WDQ6))
Flash Frequency: "80MHz"
Upload Speed: "115200"
Core Debug: "None"
Port: "COM5" (although will change)
Board Status in IDE:

ESP32 Module Soldered and Wired on:

USB to TTL Wiring:
Black-Ground
Red-3.3V
Yellow -TXD pin on adapter (USB-2-TTL), RXD pin on ESP32
Blue -RXD pin on adapter, TXD pin on ESP32

The Error

Sequence of Events: Compile>Upload Start>Wait for "Connecting">Put ESP32 into Bootloader Manually>Wait>Error

"A fatal error occured: timed out waiting for packet content"

Attempted and Failed Solutions

In each attempted solution, settings were reverted back to those in "The Setup" section, and were not changed unless specified in numbered bullet point.

1. Set Upload Speed to 921600.
2. Set Flash Frequency to 40MHz.
3. Using a Different USB to TTL adapter.
4. Using a Different Sketch.
   Edit:
5. 3.3v to EN pin.
6. Using esptool directly.
7. Uncompressed upload.
8. Holding down 1O0 during power on to keep ESP in boot-loader.
9. Changing flash modes QIO DIO etc.
10. "Strapping" IO12 to ground.
11. 1k resistor between 3V3 and IO12.
12. 330uf 25V capacitor between 3V3 and GND.

Query

I cannot find the specific documentation on this error message, so that I could properly debug the problem. Since it gets past the packet header stage, I assume everything prior is working. Should I be doing something differently? What could be causing this problem?

Success

For whatever reason, the first ESP was not working, maybe due to poor soldering/ heat damage, or a plethora of other reasons, but upon getting a second ESP (different breakout board from different manufacturer) it worked almost immediately. Now I just need to ensure it doesn't brownout and the sketches work properly, and everything should be solved.

[copercini]

It's your first upload?
try set Upload Speed to 115200 for the first time

When it appears "Connecting......._____...." try press and hold the IO0 button for 2 or 3 seconds (just necessary on the first upload)

Also: Nice board setup and issue report!

[DreamingRaven]

Yeah its my first time with ESP32 and flashing it like this, although in the past ive used ESP8266 Feather, but that was so streamlined for stuff like this. Now i have the horror of finding EN, since i soldered the labels between the breakout and vero board XD
Edit:
Thank you for the compliments!
Also I just realised what you meant, yes its the first flash of this particular ESP32

[copercini]

I checked your adapter board on google and it have an internal VCC to EN connection, so no worry about it

[DreamingRaven]

Il try the EN pin anyway in a sec.

[DreamingRaven]

My quick test with 3.3v on EN did not work, but I need to double check i have the right pin since i cant see the labels.

[DreamingRaven]

Just checked, and yeah it was the right pin. Im going to make sure this new connection is providing a voltage diff, before I continue.
Edit: it is, 2.6/2.7v across gnd & EN
Also on repeating the test I got the following,
At the moment I reset the board and held down IO0, to manually put it into bootload as I have several times before. Probably a one off, but documenting it anyway.
Even later Edit: Yeah definitely a one off.

[DreamingRaven]

Also was looking through espressif/esptool and found espressif/esptool#213 still looking through the issues over there for anything similar, havent found one that is after compression stage.

[DreamingRaven]

I think the next best possible approach is to create the Binaries and use esptool directly, and hopefully this will be more verbose than the Arduino IDE. Now to read about that usage.

[lonerzzz]

@DreamingRaven Are there any updates to this issue? Is there still some information you need or can we close this?

[DreamingRaven]

No luck as yet, still getting the same error as previously, and ive been slowly trying esptool.py directly where I can.

[DreamingRaven]

I've also been using an oscilloscope and multimeter to verify that the power is not the problem. Which it does not appear to be.

[DreamingRaven]

I have been slowly attempting different things, I'm just praying it is not a manufacturing defect because that would be a pain to diagnose. Otherwise the chip seems to be communicating fine, stub uploads and runs, its just after compression, it times out "waiting for packet content". :/

[DreamingRaven]

Suppressing compression using esptool leads to the same result above.

[DreamingRaven]

Ok so now i'm just gonna go through the gotchas in https://nodemcu.readthedocs.io/en/master/en/flash/ and eliminate anything that fits. Can anyone see anything im doing wrong so far?

[me-no-dev]

Make sure GPIO12 is pulled LOW. I have the feeling yours is not and its trying to boot the flash at 1.8V