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
Comments
I just tested it myself on a node that's not possible to flash using the web flasher:
|
I added a breakpoint to where the exception was caught: |
Can you post what you see on Chrome's Developer console? |
Is that all the console shows? No log messages? |
Yep that's all. |
It's empty, even with Verbose enabled. Do i need to do anything to have more debug output like @TD-er above? |
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) |
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 this should be fixed in 3.4.2, live now in the docs. Can you try it? |
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. |
Works now, thank you! |
@degraafm76 yes, after the update it works for cp2102 and ch340 |
I see, but not for ESP8266EX modules. |
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:The text was updated successfully, but these errors were encountered: