Timed Out waiting for packet content -- DevKitC

VE3KXA
Posts: 3
Joined: Tue Apr 03, 2018 6:15 pm

Timed Out waiting for packet content -- DevKitC

Postby VE3KXA » Thu Apr 05, 2018 3:30 pm

This issue has been dealt with many times -- but I have two new DevKitC's that I can't download code. Both operate in exactly the same way -- so I am thinking that it is something to do with my setup? My procedure has been to reset the ESP32 with the enable switch, then press "Boot". I then run "make flash" on my Linux command line terminal.

1. Not sure why the flash size can not be detected
2. I don't know what "boot:0x13" means
3. Don't know why I am experiencing a flash read error on both my samples

I am not sure I know what to do next -- any help will be greatly appreciated.

I running the ESP-IDF under linux. Trying to get the "hello_world" example to run:

iot@Mercury:~/esp/hello_world$ make flash
Flashing binaries to serial port /dev/ttyUSB0 (app at offset 0x10000)...
esptool.py v2.3.1
Connecting........_
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Warning: Could not auto-detect Flash size (FlashID=0xffffff, SizeID=0xff), defaulting to 4MB
Flash params set to 0x0220
Compressed 19696 bytes to 11646...

A fatal error occurred: Timed out waiting for packet content
/home/iot/esp/esp-idf/components/esptool_py/Makefile.projbuild:54: recipe for target 'flash' failed
make: *** [flash] Error 2


A terminal program connected to the devKit reports a flash error:

iot@Mercury:~/esp/hello_world$ cat /dev/ttyUSB0
ets Jun 8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

rst:0x10 (RTCWDT_RTC_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))
waiting for download

ESP_Angus
Posts: 2176
Joined: Sun May 08, 2016 4:11 am

Re: Timed Out waiting for packet content -- DevKitC

Postby ESP_Angus » Fri Apr 06, 2018 4:13 am

It looks like they're failing to talk to the flash chip. Is anything connected to the pins of the DevKitCs?

VE3KXA
Posts: 3
Joined: Tue Apr 03, 2018 6:15 pm

Re: Timed Out waiting for packet content -- DevKitC

Postby VE3KXA » Fri Apr 06, 2018 12:30 pm

Doesn't the first part of the preamble ( connecting ... chip ID is .....) indicate that my PC and the chip are communicating? There nothing other than the USB cable from the PC connected to the DevKitC and a power supply connection to the 5V pin and ground.

VE3KXA
Posts: 3
Joined: Tue Apr 03, 2018 6:15 pm

Re: Timed Out waiting for packet content -- DevKitC

Postby VE3KXA » Sat Apr 07, 2018 12:53 am

The log preamble seems to indicate that the tool is communicating with the chip -- I think, I am not sure what the boot error code means though. Can anyone point me to documentation or interpret

Who is online

Users browsing this forum: No registered users and 27 guests