-
Notifications
You must be signed in to change notification settings - Fork 111
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
Using this tool to burn MicroPython firmware on ESP8266 always fails #120
Comments
Can you provide more detail what issue are you facing with esptool-js @drbdrb ? |
It's like this, I use: https://espressif.github.io/esptool-js/ The tool always fails to burn the official firmware of micropython for ESP8266, and the chip cannot function properly after burning! However, using the esptool. py tool to burn the same official firmware for micropython can still run normally. The burning addresses are all: 0x0000, and the firmware is the same. You can download from this address: https://www.micropython.org/resources/firmware/esp8266_generic-20231005-v1.21.0.bin I found that when using the esptool. py tool, I need to set the The chip is ESP8266EX, Burn write baud rate: 115200, Location: 0x0000 I recorded a video and sent it to your @brianignacio5 email. Please check and help me see what caused this error? |
What did the author do recently? This project hasn't been updated for almost two months? Is there any hope of solving the problem I mentioned above? |
@drbdrb esptool.py |
I use https://espressif.github.io/esptool-js/ to burn MicroPython firmware, version
[v1.21.0 (2023-10-05) .bin](http://www.micropython.org/resources/firmware /ESP8266_GENERIC-20231005-v1.21.0.bin),
the programming can work normally, but the chip cannot run normally after burning. So far, I have also tried to use esptool.py to burn this firmware. Using esptool.py to burn the same firmware is It can run normally, but burning using esptool.js tool does not work. Hope the author can solve this problem?
The text was updated successfully, but these errors were encountered: