Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'Disable stub if connecting to an unsupported chip' commit breaks flashing on my supported chip (ESPTOOL-258) #635

Habbie opened this issue Jun 20, 2021 · 3 comments


Copy link

Habbie commented Jun 20, 2021

Operating system

Raspberry PI OS 10

Python version


What Chip


What development board or other hardware is the chip attached to

flashing setup can be partially seen at if you're interested, but I don't think it's important for this bug report.

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

microusb for power; GND/RX/TX to the right pins on a Pi3.

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

no, bash.

Full command line that was run:

~/.local/bin/ -p /dev/ttyS0 write_flash 0 ~/esphomeirbridge.bin

Full output from v3.2-dev
Serial port /dev/ttyS0
Failed to get PID of a device on /dev/ttyS0, using standard reset sequence.

Detecting chip type... ESP8266
Chip is ESP8266EX
Features: WiFi
Crystal is 26MHz
MAC: 8c:ce:4e:eb:9e:c3
Traceback (most recent call last):
  File "/home/pi/.local/bin/", line 7, in <module>
    exec(compile(, __file__, 'exec'))
  File "/home/pi/esptool/", line 4613, in <module>
  File "/home/pi/esptool/", line 4606, in _main
  File "/home/pi/esptool/", line 4120, in main
    elif esp.stub_is_disabled:
AttributeError: 'ESP8266StubLoader' object has no attribute 'stub_is_disabled'

Do you have any other information from investigating this?

I suspected 1c9fe70 broke this. I checked out the commit before it,
1ca08af, and then I could flash without trouble.

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

I don't think so.

@github-actions github-actions bot changed the title 'Disable stub if connecting to an unsupported chip' commit breaks flashing on my supported chip 'Disable stub if connecting to an unsupported chip' commit breaks flashing on my supported chip (ESPTOOL-258) Jun 20, 2021
Copy link

Hi @Habbie,
thanks for reporting this and for identifying the source of the issue.

The fix is already in the works!


Copy link

I'm facing the same issue. I'm using a rts/dtr capable pty<->pty bridge between esptool and a usb-uart bridge. The PID error always comes up, whereas the Exception only occasionally occurs, and it generally succeeds in the same way as if esptool directly communicated with the usb-uart. Without the pty<->pty bridge, no PID error occurs at all.

I suspect esptool's timings for rts/dtr are too tight, as it always expects to be directly connected to the target board, hence doesn't tolerate lag/latency when re-/setting the chip. Is it possible to extend esptool so that various timeout values can be passed on the command line? Even the 3 second timeout during flashing is occasionally limiting when flashing over a transparent wifi-bridge, with or without the socket:// option.

Copy link

@moefear85, this issue is completely unrelated to your question. We will continue the conversation in your issue ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

3 participants