Exception: Failed to connect to ESP32: Timed out waiting for packet header

[chrisq]

Trying to upgrade the firmware I get the error in the topic.

The lopy is placed in the expansion board, led at the same end as usb.
G23 and GND are connected.
I have read/write access to the usb-serial device it presents itself as.

Any ideas?

[abilio]

Hi @chrisq, can you confirm the LED blinking if you turn the board on without the wire?

[chrisq]

@abilio Thank you for the quick reply.
Yes, the led is blinking blue about every 4 seconds without the wire.

[abilio]

@chrisq Do you have the jumpers in the expansion board?

[chrisq]

In case it's useful:

[ 8032.623635] usb 2-2: new full-speed USB device number 20 using xhci_hcd
[ 8032.807496] ftdi_sio 2-2:1.0: FTDI USB Serial Device converter detected
[ 8032.807536] usb 2-2: Detected FT-X
[ 8032.807724] usb 2-2: FTDI USB Serial Device converter now attached to ttyUSB0

 chrisq@berber   ~  lsusb
Bus 002 Device 020: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)

 chrisq@berber   ~  groups
adm disk uucp log rfkill video audio floppy input power users docker chrisq

 chrisq@berber   ~  ls -la /dev/ttyUSB0
crw-rw---- 1 root uucp 188, 0 Oct 31 15:29 /dev/ttyUSB0

lsusb -vvv

  bcdUSB               2.00
  bDeviceClass            0
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x0403 Future Technology Devices International, Ltd
  idProduct          0x6015 Bridge(I2C/SPI/UART/FIFO)
  bcdDevice           10.00
  iManufacturer           1
  iProduct                2
  iSerial                 3
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower               90mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              2
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0

[chrisq]

@abilio Yes

[chrisq]

@abilio The lopy shows up when scanning for wifi ap's (unless there's someone else in the office who also got one :) ).

[Xykon]

Can you check with a terminal program that you get this output when you reset the board while the G23/GND wire is connected?

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

Can you post the full output from the updater when you run it manually?

bin/updater.py -f firmware/lopy_0.9.1.b1_868.bin -p /dev/ttyUSB0

Make sure to use the correct file for your region (868/915).

[chrisq]

@Xykon Thank you for the reply!

Below is the result.
I did just notice, however, that my expansion board did not come with a jumper on the "TX" pins, while in the picture docs.pycom.io it seems to be there. Could that be the issue?

python2 bin/updater.py -f firmware/lopy_0.9.1.b1_868.bin -p /dev/ttyUSB0
Namespace(file='firmware/lopy_0.9.1.b1_868.bin', port='/dev/ttyUSB0')
Connecting...
Exception: Failed to connect to ESP32: Timed out waiting for packet header, on line 75

[abilio]

Yes @chrisq, we've just found that was the cause for another user (see here). Can you place a jumper on TX and retry. If you don't have spare jumpers, you can take out the one that says BAT and use it to test.

[chrisq]

@abilio Mystery solved!
A paperclip worked as well, and I now found the original jumper lodged in a corner of the bubble bag.
Thanks for all the help, I think I'm good to go now :)

[abilio]

@chrisq, good to know you pulled a Macgyver and it worked :) . I'm proceeding to to close this thread now as it was solved.