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

ESP8266EX Support? #27

Closed
ghtomcat opened this issue Jun 23, 2021 · 20 comments
Closed

ESP8266EX Support? #27

ghtomcat opened this issue Jun 23, 2021 · 20 comments

Comments

@ghtomcat
Copy link

I can successfully flash my ESP32 but not my two NodeMCU (v2 and v3), which use the ESP8266EX Chip.

error: "failed_initialize", details: Error: Unknown Chip

esptool flash_id returns:

Connecting....
Detecting chip type... ESP8266
Chip is ESP8266EX
Features: WiFi
Crystal is 26MHz
MAC: c4:5b:be:60:dc:da
Uploading stub...
Running stub...
Stub running...
Manufacturer: d8
Device: 4016
Detected flash size: 4MB
@TD-er
Copy link

TD-er commented Jun 23, 2021

I just tested it myself on a node that's not possible to flash using the web flasher:

image

esptool.py v3.0
Serial port COM3
Connecting....
Chip is ESP8266EX
Features: WiFi
Crystal is 26MHz
MAC: 2c:3a:e8:39:13:7c
Flash Chip ID: Vendor: 0x20 Device: 0x4016
Flash Chip Real Size: 4096 kB
Flash IDE Size: 4096 kB
Flash IDE Speed: 40 MHz
Flash IDE Mode: DOUT

@TD-er
Copy link

TD-er commented Jun 23, 2021

I added a breakpoint to where the exception was caught:
domexception a framing error has been detected

@conradopoole
Copy link

I can successfully flash my ESP32 but not my two NodeMCU (v2 and v3), which use the ESP8266EX Chip.

error: "failed_initialize", details: Error: Unknown Chip

esptool flash_id returns:

Connecting....
Detecting chip type... ESP8266
Chip is ESP8266EX
Features: WiFi
Crystal is 26MHz
MAC: c4:5b:be:60:dc:da
Uploading stub...
Running stub...
Stub running...
Manufacturer: d8
Device: 4016
Detected flash size: 4MB

Can you post what you see on Chrome's Developer console?

@conradopoole
Copy link

I just tested it myself on a node that's not possible to flash using the web flasher:

image

esptool.py v3.0
Serial port COM3
Connecting....
Chip is ESP8266EX
Features: WiFi
Crystal is 26MHz
MAC: 2c:3a:e8:39:13:7c

Flash Chip ID: Vendor: 0x20 Device: 0x4016
Flash Chip Real Size: 4096 kB
Flash IDE Size: 4096 kB
Flash IDE Speed: 40 MHz
Flash IDE Mode: DOUT

Is that all the console shows? No log messages?

@TD-er
Copy link

TD-er commented Jun 23, 2021

Yep that's all.

@conradopoole
Copy link

Yep that's all.

Can you click on the login levels and enable Verbose?

image

@TD-er
Copy link

TD-er commented Jun 23, 2021

Not much of a difference:
image

@ghtomcat
Copy link
Author

Can you post what you see on Chrome's Developer console?

It's empty, even with Verbose enabled. Do i need to do anything to have more debug output like @TD-er above?

@balloob
Copy link
Member

balloob commented Jun 23, 2021

By default it doesn't log to the console. I've just updated the demo to do so e6a198f. So now open the chrome dev tools prior to flashing.

@ghtomcat
Copy link
Author

By default it doesn't log to the console. I've just updated the demo to do so e6a198f. So now open the chrome dev tools prior to flashing.

Thanks, now i see the following in the console (with the demo)

Bildschirmfoto 2021-06-23 um 19 02 17

@TD-er
Copy link

TD-er commented Jun 23, 2021

image

This attempt I held GPIO-0 down and pressed reset.
The attempt before was the same, without reset + GPIO-0 held.

@balloob
Copy link
Member

balloob commented Jun 23, 2021

The error has been updated by @conradopoole. It should now include the magic value of your chip so we can add it to the detected list. The demo has been updated.

@ghtomcat can you try it again and report the updated error message.

@ghtomcat
Copy link
Author

The error has been updated by @conradopoole. It should now include the magic value of your chip so we can add it to the detected list. The demo has been updated.

start-flash-542f194f.js?module:1 Error: Unknown Chip: 0x-F3EFF

@TD-er
Copy link

TD-er commented Jun 23, 2021

Me too, on one module (with CH340) Unknown Chip: 0x-F3EFF

The unresponsive unit with CP2102 USB to serial:
image

@balloob
Copy link
Member

balloob commented Jun 23, 2021

@ghtomcat this should be fixed in 3.4.2, live now in the docs. Can you try it?

@TD-er
Copy link

TD-er commented Jun 23, 2021

Does work with the node that gave the unknown chip error before.

The "timeout" unit still remains unresponsive, but had not expected it to be fixed by these changes.

@balloob balloob closed this as completed Jun 24, 2021
@ghtomcat
Copy link
Author

@ghtomcat this should be fixed in 3.4.2, live now in the docs. Can you try it?

Works now, thank you!

@degraafm76
Copy link

Me too, on one module (with CH340) Unknown Chip: 0x-F3EFF

The unresponsive unit with CP2102 USB to serial: image

Did you get the CP2102 working? if have the same issue with ESP8266EX modules

@ghtomcat
Copy link
Author

@degraafm76 yes, after the update it works for cp2102 and ch340

@degraafm76
Copy link

@degraafm76 yes, after the update it works for cp2102 and ch340

I see, but not for ESP8266EX modules.

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

No branches or pull requests

5 participants