Installation failed on Chrome@MacOS

[Mashiro69]

When I click the Install esphome.esp_web_tools_example Botton , It shows : Failed to initialize. Try resetting your device or holding the BOOT button while clicking INSTALL.

◎ esptool --port /dev/cu.usbmodem21201 read-mac 
esptool v5.0.2
Connected to ESP32-C3 on /dev/cu.usbmodem21201:
Chip type:          ESP32-C3 (QFN32) (revision v0.3)
Features:           Wi-Fi, BT 5 (LE), Single Core, 160MHz
Crystal frequency:  40MHz
USB mode:           USB-Serial/JTAG
MAC:                60:55:f9:7e:89:a4

Stub flasher running.

MAC:                60:55:f9:7e:89:a4

Hard resetting via RTS pin...

esptool --port /dev/cu.usbmodem21201 erase-flash
esptool v5.0.2
Connected to ESP32-C3 on /dev/cu.usbmodem21201:
Chip type:          ESP32-C3 (QFN32) (revision v0.3)
Features:           Wi-Fi, BT 5 (LE), Single Core, 160MHz
Crystal frequency:  40MHz
USB mode:           USB-Serial/JTAG
MAC:                60:55:f9:7e:89:a4

Stub flasher running.

Flash memory erased successfully in 0.0 seconds.

Hard resetting via RTS pin...

Chrome version: 139.0.7258.67 (arm64)
MacOS version: macOS Tahoe Beta 26.0 (25A5316i)

[screekworkshop]

edge and chrome seems all not work now.

https://espressif.github.io/esptool-js/ break too

edge 139.0.3405.86
chrome 139.0.7258.67
macOS 15.5

It appears that the issue stems from a Chrome update, which has not been installed on the Mac.

[Mashiro69]

Now I use esptool write-flash to instead of its

[screekworkshop]

this workaround work for me:

open -b com.google.Chrome --args --disable-features=SerialSplitDtrAndRts

espressif/esptool-js#206
https://issues.chromium.org/issues/420689824#comment11

[DreyMX]

Hi,

This issue seems to be related to recent changes in Chrome’s (since version 139.0.7258.66) handling of serial port control signals https://issues.chromium.org/issues/437068905.

To work around it in MacOs, try launching Chrome from the terminal with the following flag (make sure all other Chrome instances are closed first):

$ /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --disable-features=SerialSplitDtrAndRts

This worked for me.

[screekworkshop]

Yes, we saw that the proposal has already been upgraded to P0, and it looks like a new version will be released urgently.
If you don’t use an absolute path, you could also consider using the following methods that rely on system identifiers to locate Chrome.

open -b com.google.Chrome --args --disable-features=SerialSplitDtrAndRts

open -a "Google Chrome" --args --disable-features=SerialSplitDtrAndRts

if edge

open -a "Microsoft Edge" --args --disable-features=SerialSplitDtrAndRts

[screekworkshop]

https://chromium.googlesource.com/chromium/src/+log/139.0.7258.67..139.0.7258.128?pretty=fuller&n=10000

It has been fixed in the latest version released on 139.0.7258.128. This behavior is now disabled by default, so no additional parameters are required. Just click “Update” in “About.”

Currently, the traces for this issue are as follows: Chrome version 139.0.7258.67 has a bug that requires manual parameter settings to work, while subsequent and previous versions are normal.