search

espressif / esptool

Espressif SoC serial bootloader utility
https://docs.espressif.com/projects/esptool
GNU General Public License v2.0
5.61k stars 1.39k forks source link

Unable to connect to ESP32-WROVER chip #524

Closed tslater2006 closed 4 years ago

tslater2006 commented 4 years ago

Operating system

Windows 10

Python version

3.6

What Chip

ESP32-WROVER

What development board or other hardware is the chip attached to

IoT Device with exposed pads for UART communication

Is anything else attached to the development board, except for the serial flasher connections?

There are various connections on the chip. I'm unable to document them all but I do know I2C is in use

Are you running esptool.py from an IDE such as Arduino or Eclipse?

Windows command prompt

Full esptool.py command line that was run:

esptool.py -p COM4 --before no_reset -b 115200 --trace read_mac

Full output from esptool.py

C:\Users\Timothy>esptool.py -p COM4 --before no_reset -b 115200 --trace read_mac esptool.py v3.0-dev Serial port COM4 Connecting...TRACE +0.000 command op=0x08 data len=36 wait_response=1 timeout=0.100 data= 0707122055555555 5555555555555555 | ... UUUUUUUUUUUU 5555555555555555 5555555555555555 | UUUUUUUUUUUUUUUU 55555555 | UUUU TRACE +0.001 Write 46 bytes: c000082400000000 0007071220555555 | ...$........ UUU 5555555555555555 5555555555555555 | UUUUUUUUUUUUUUUU 5555555555555555 5555555555c0 | UUUUUUUUUUUUU. TRACE +0.013 Read 1 bytes: c0 TRACE +0.000 Read 45 bytes: 0008240000000000 0707122055555555 | ..$........ UUUU 5555555555555555 5555555555555555 | UUUUUUUUUUUUUUUU 5555555555555555 55555555c0 | UUUUUUUUUUUU. TRACE +0.001 Received full packet: 0008240000000000 0707122055555555 | ..$........ UUUU 5555555555555555 5555555555555555 | UUUUUUUUUUUUUUUU 5555555555555555 55555555 | UUUUUUUUUUUU TRACE +0.117 Timed out waiting for packet header .TRACE +0.064 command op=0x08 data len=36 wait_response=1 timeout=0.100 data= 0707122055555555 5555555555555555 | ... UUUUUUUUUUUU 5555555555555555 5555555555555555 | UUUUUUUUUUUUUUUU 55555555 | UUUU TRACE +0.003 Write 46 bytes: c000082400000000 0007071220555555 | ...$........ UUU 5555555555555555 5555555555555555 | UUUUUUUUUUUUUUUU 5555555555555555 5555555555c0 | UUUUUUUUUUUUU. TRACE +0.006 Read 1 bytes: c0 TRACE +0.001 Read 17 bytes: 0008240000000000 0707122055555555 | ..$........ UUUU 55 | U TRACE +0.015 Read 1 bytes: 55 TRACE +0.001 Read 27 bytes: 5555555555555555 5555555555555555 | UUUUUUUUUUUUUUUU 5555555555555555 5555c0 | UUUUUUUUUU. TRACE +0.005 Received full packet: 0008240000000000 0707122055555555 | ..$........ UUUU 5555555555555555 5555555555555555 | UUUUUUUUUUUUUUUU 5555555555555555 55555555 | UUUUUUUUUUUU TRACE +0.113 Timed out waiting for packet header

Do you have any other information from investigating this?

I only have TXD0 and RXD0 connected to my UART to USB adapter. The above trace just repeats over and over, I can see esptool sending a frame and receiving a frame and then it immediately reports a timeout.

Based on testing with some additional trace messages that the response never gets a status that is 1 and so it is falling into the "continue" statement: image

I've also confirmed that op_ret and op are identical in the unpacked struct

Is there any other information you can think of which will help us reproduce this problem?

The IoT device I'm trying to talk to is pretty hard to source so I don't know if it'll be reproducable. Sort of hoping that trace gives a hint though. I'd be happy to provide any additional information I can.

tslater2006 commented 4 years ago

I didn't have GND connected from the chip to my UART adapter... everything is working great now.