jimparis / esptool-ftdi Goto Github PK

Esptool 4.0 was released and after the update the esptool-ftdi stopped working. I tried some workarounds like being the open pool requests or importing esptool instead of running it as an external tool.

I think I advanced a couple of steps but the esp32 is still not correctly reset to bootloader mode. Any chance you have a look at it? Otherwise I will take a look but it might need some time till I get to it.

As a newbie to VSCODE and ESP32 programming, I 'boy this is crazy that I have swap jumpers' on my board in order to program it. After a bit of digging, I came across this package, which I believe provides the exact workaround that I was looking for (original reference: https://www.esp32.com/viewtopic.php?t=6113).

I hate to bother you with this: I have spent some time trying to figure out how to change the VSCODE tool chain path with little luck. Do you have any pointers as to where I should start looking?

Hello,

First of all can I say a huge thank you for creating this piece of software. It is an absolute life saver as it has allowed me to connect my custom ESP32 board with my Tag Connect cable (https://www.tag-connect.com/product/tc2030-ftdi-ttl-232r-usb-to-tc2030-serial-cable).

I am able to successfully able to finish flashing the board, using the following command:
./esptool-ftdi.py esptool.py --baud 115200 write_flash --flash_mode qio --flash_size 4MB 0x1000 AQ_Board.ino.esp32.bin
However upon starting the board, in the serial monitor I am only able to see repeating logs:

12:31:04.730 -> rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
12:31:04.767 -> configsip: 0, SPIWP:0xee
12:31:04.767 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
12:31:04.767 -> mode:QIO, clock div:2
12:31:04.767 -> load:0x3f400020,len:161780
12:31:05.095 -> ets Jun  8 2016 00:22:57

This is area is not my expertise, so I am unable to work out whether this is an issue with the software or most likely my own user error. Are you able to offer any advice?

Kind regards, Ryan

@jimparis
Hi Jim, I think this may be a solution I have been looking for !
I am pretty hands off with the low level detail of the build infrastructure, and the setup I have is all based around the usage of idf.py
Do you know how I would integrate with that flow ?

Thx
Lee

Hello!
Great tool, does exactly what I need.

Could you please specify which license it is distributed under?

I seem to be running into trouble trying to wrap the latest esptool.py script with esptool-ftdi.py

I'm using the master branch of this repo. RTS/CTS on an FTDI230XQ to an ESP32 (ESP32-D2WD)

I can intermittently erase flash, but any attempts at writing flash ends with the following error:

raceback (most recent call last):
  File "/home/aalbino/.local/bin/esptool-ftdi.py", line 276, in <module>
    esptool.main()
  File "/home/aalbino/.local/bin/esptool.py", line 2695, in main
    detect_flash_size(esp, args)
  File "/home/aalbino/.local/bin/esptool.py", line 2074, in detect_flash_size
    flash_id = esp.flash_id()
  File "/home/aalbino/.local/bin/esptool.py", line 567, in flash_id
    return self.run_spiflash_command(SPIFLASH_RDID, b"", 24)
  File "/home/aalbino/.local/bin/esptool.py", line 839, in run_spiflash_command
    wait_done()
  File "/home/aalbino/.local/bin/esptool.py", line 836, in wait_done
    if (self.read_reg(SPI_CMD_REG) & SPI_CMD_USR) == 0:
  File "/home/aalbino/.local/bin/esptool.py", line 475, in read_reg
    val, data = self.command(self.ESP_READ_REG, struct.pack('<I', addr))
  File "/home/aalbino/.local/bin/esptool.py", line 332, in command
    p = self.read()
  File "/home/aalbino/.local/bin/esptool.py", line 277, in read
    return next(self._slip_reader)
  File "/home/aalbino/.local/bin/esptool.py", line 1890, in slip_reader
    raise FatalError('Invalid head of packet (0x%s)' % hexify(b))
esptool.FatalError: Invalid head of packet (0x46)