Fatal error: waiting for packet content #491
Comments
|
It's your first upload? 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! |
|
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 |
|
I checked your adapter board on google and it have an internal VCC to EN connection, so no worry about it |
|
Il try the EN pin anyway in a sec. |
|
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. |
|
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. |
|
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. |
|
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. |
|
@DreamingRaven Are there any updates to this issue? Is there still some information you need or can we close this? |
|
No luck as yet, still getting the same error as previously, and ive been slowly trying esptool.py directly where I can. |
|
|
|
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". :/ |
|
|
|
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? |
|
Make sure GPIO12 is pulled LOW. I have the feeling yours is not and its trying to boot the flash at 1.8V |
|
@me-no-dev What makes you say that? What is the significance of IO12? Looking through the data sheet, i see no significant mentions of IO12, it just seems to be a normal IO pin, but im a newcomer to this specific chip, I dont know its ins and outs yet. Il check in a second the Vdif across IO12, its a pain to find the pins due to labels being between module and vero board :/ |
|
If you are looking at the latest datasheet, that is the first row of table
2 in section 2.4, Strapping Pins.
…On Fri, Aug 18, 2017 at 2:50 AM, Raven ***@***.***> wrote:
@me-no-dev <https://github.com/me-no-dev> What makes you say that? What
is the significance of IO12? Looking through the data sheet, i see no
significant mentions of IO12, it just seems to be a normal IO pin, but im a
newcomer to this specific chip, I dont know its ins and outs yet. Il check
in a second the Vdif across IO12 in a moment, its a pain to find the pins
due to labels being between module and vero board :/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#491 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEJceqP_XBSqBUNQEtVs3DOMdA0JSeIjks5sZIt3gaJpZM4ORLwD>
.
|
|
I must be looking at the wrong data sheet. (http://akizukidenshi.com/download/ds/espressifsystems/esp_wroom_32_datasheet_en.pdf) |
|
Yeah just got August 10 2017 datasheet (https://www.espressif.com/sites/default/files/documentation/esp32_datasheet_en.pdf), |
|
Yeah looks like it is high, |
|
Let me just confirm that this is the correct pin. As I am assuming I followed the right trace. I need to find the labels for the breakout board (https://www.amazon.co.uk/gp/product/B06Y1LMJCD/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1) which are a royal pain to find any information about. I am very reluctant to desolder the entire thing off to find the labels on the back |
|
No i had the wrong one the first time, although it is the last pin, the trace actually takes it to the second to last pin, rather than the last pin which i had connected. What i believe currently is IO12, so that others can also see, and correct me if I am mistaken (in red): Edit: after some confusion, the pin is actually on the opposite side (bottom of left hand solder contacts). |
|
I must admit however I am strugling to understand the pinout diagrams in the latest data sheet, as it looks nothing like my current module: Compared to the older data sheet: The problem with the older data sheet is that it puts the TxD and RxD on the other side of the board to which this chinese breakout board has labeled as TxD and RxD. I found a picture of the back of the module when I bought it !!! : The breakout board could be mis-labeled! |
|
Also my apologies to everyone, i'm posting relentlessly so that in the future both I and others can see the mistakes I made, and my (erratic) thought process. |
|
Ok after trace following and relying soley on the modules labels, I have found that this breakout board was not mis labelled, but instead 3.3v and gnd are connected to pins on the opposite side. |
|
@me-no-dev I have "strapped" IO12 to ground (it also appears to be on board level, connected to ground through the white line, but this cant possibly be the case due to a later concern with pulling MTDI low), but there was no change in error message:
There was one odd thing that occurred however, while I manually strapped IO12 the serial port was recieving the following from the ESP32:
Edit: |
|
I don't know where to go now. What is causing this error, timeout; packet content? I'm really excited to make stuff with the ESP32 but its been weeks with minimal progress made trying to solve this issue and its incredibly frustrating. |
|
I have had the same exact issue a couple of days back and it came to be the bootstrapping of pin12 (MTDI) and I mean like 100% the same exact problem. Can you confirm that GPIO12 is low at boot/into-download modes? |
|
Yeah il double check tomorrow, its getting pretty late here. Edit: i'm back, testing now! |
|
Above you show GPIO tied to GND and that is not the right configuration!!! Needs to be tied to VCC |
|
use 1K resistor between IO12 and VCC |
|
To confirm what I am testing, you are saying: I'l test this shortly. |
|
First test, made no change, let me just check that everything is correctly implemented. |
|
Ok so I got a second ESP32 and soldered it (less fancy than last). I used the example ESP32 sketch GetChipID, with no alterations. Compiled and attempted upload. Low and behold, the exact same error message.
|
|
What could this mean, in terms of source of the problem.
Have I missed anything? |
|
I think, it may be best to scrap using arduino and esptool.py all together, and use something else, as the two most likely causes are wrong connections or a tool issue. Since I heuristically assume that between these two a tool based bug, is the most probable (debian, windows 8.1, arduino, esptool.py). |
|
There surely is nothing wrong with Arduino and esptool.py ;) Arduino is on top of IDF and IDF and esptool are the official tools to work on esp32. Something totally hardware is going on |
|
I'm just not sure what more I can try hardware wise. I have read through so much documentation, and followed so many guides, I don't know what other options I have left. |
|
:O |
|
|
|
I just took out the resistor, and it works. |
|
let me just repeat with a different more advanced sketch, to make sure this is not just some weird fluke. |
|
well done ! Did you boot up your module and see it run properly with wifi sketch? |
|
Sorry for the delay, I went away and made some creme brulees. I did but im getting "brownout detector was triggered" in serial console. Which to my understanding means, the resistance in the jumper cables/ breadboard, is too high (or the UART bridge doesn't supply enough). Now to go solve that, but i'm happy that I've finally managed to upload!!!!!! |
|
Maybe il power it from something a little more expandable, so I can put in some quality of life features, like power LED, and battery power etc etc. Kill two birds with one stone. Maybe I should flash it with an OTA sketch first, just in case. But il need to check that ESP32 can update OTA, I may be mis-remembering / watched something outdated that said it couldn't, just need to confirm that. Although I don't see why it wouldn't be able to. |
|
Hi DreamingRaven, I´m seeing the same behavior here... exactly the same one... 2x esp32 with the same problem, after "backs and forwards" the first one back to life (no much explanation how it happened), and after that no problem at all... the second one still not working. What I cant see (and is some kind of strange to me) is that when the problem is present, Testing resistance between 3v3 and GND in too low (much lower than the usual one in the working boards)... Also, when the problem is present and the ESP energized (strong 3,3v soldered and stable), the EN (that is poll UP with a 10K resistor) shows almost no voltage. Apparently, at this state something is happening inside the module or the chip itself (I did not uncover the module to take measures at the chip pins) I don´t care about the this ESP32 itself, but I definitely care about know what is the logic around this (or how to avoid the problem in the future)....
As you previously said: "I'm just not sure what more I can try hardware wise. I have read through so much documentation, and followed so many guides, I don't know what other options I have left." |
|
The issue is similar to: espressif/esp-idf/issues/113 |
|
Additionally, @me-no-dev wrote ... later: "Above you show GPIO tied to GND and that is not the right configuration!!! Needs to be tied to VCC" and "use 1K resistor between IO12 and VCC". Just to clarify, the first one (ie GPIO12 pulled LOW) is the correct one, right? Tks |
|
Hi again,
I have found some flux not cleaned in both boards and ESPs. After cleaning them correctly both start working fine! Note: I do not understand why the module have this behavior but surely is something related to unexpected conductivity between some pins (I could not conclude which of them). |
|
Hey @elucas2uy , sorry for the late response, I think It may actually have been the breakout board I was using, because well.. I don't seem to replicate the failure with my other boards (several now), despite the same configuration. Glad it worked for you in the end. Also happy Halloween! |
|
@elucas2uy, If you need me or if anyone else needs me to list my pin voltages for a working configuration I will. Its just a pain in the rear now that its integrated into other stuff. Although I may do it for my own reference and post it anyway. |
|
I have the MH-ET LIVE (http://mh.nodebb.com/topic/2/mh-et-live-esp32-devkit). Now to figure out why the USB program doesnt work.
|
|
Nice one! I hope it all goes well! If I remember correctly I had issue with my program when I flashed it as well, although I'm afraid I cant remember how I overcame it as it was two years ago now, wow time flies. Good luck! |
|
Might consider pulling up the EN pin with a 10K resistor. Dev board also
uses a .1uf cap to ground.
…On Fri, Jul 26, 2019 at 12:21 PM LouDnl ***@***.***> wrote:
I have the MH-ET LIVE (
http://mh.nodebb.com/topic/2/mh-et-live-esp32-devkit).
It is impossible to program it through USB, haven't figured out why yet.
But your post made me hook up an FT232R to the boards pins as you describe
and low and behold I can program it. Thanks a lot!!
Now to figure out why the USB program doesnt work.
I just took out the resistor, and it works. _
[image: text4619]
<https://user-images.githubusercontent.com/10534713/29820083-1d9f8f5a-8cbb-11e7-938f-fbbdb2ed87e6.png>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#491?email_source=notifications&email_token=AC7Y5YNTCDHKSMVBMJPTJCDQBNFDZA5CNFSM4DSEXQB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD25PUYQ#issuecomment-515570274>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC7Y5YNTOJYIRJCEBNLKVBTQBNFDZANCNFSM4DSEXQBQ>
.
|
|
@DreamingRaven Yeah it took me a while to figure out what was wrong, but it works now. |
|
Connect to GPIO12 to GND save my problem. More info can found: https://github.com/espressif/esptool/wiki/ESP32-Boot-Mode-Selection |
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.
Edit:
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.
The text was updated successfully, but these errors were encountered: