-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Filesystem broken after re-flash #412
Comments
I have this issue too! |
I think this is the same issue as #327. I just got 6 nodemcu dev boards (the black ones) from Seeed and they all have this issue. Someone on the seeed product comments thinks it's a bug in the flash tool. |
Hi all, if you erased factory firmware, please see https://github.com/nodemcu/nodemcu-devkit-v1.0 |
I describe here how you can use the espressif tool from Mac: http://blog.squix.ch/2015/05/esp8266-flashing-nodemcu-v10-on-mac-os.html |
@squix78 ESP-12-E uses DIO mode, but both esptool and our flasher not support this mode yet, only espressif's flash tool support. We are studing how espressif's flash tool works and writing a tool really can run on MAC OS. |
@vowstar: have a look here: https://github.com/themadinventor/esptool/blob/master/esptool.py |
@squix78 have DIO keywords not means supported DIO. More things to do. |
Same issue here. Very frustrating |
Just to add more info, every file.open will return nil. |
New nodemcu-flasher is released. |
So I flashed the latest firmware to the NodeMCU v2 from Seed studio. (0.9.6-dev_20150406) But now when I try to write a file on Esplorer fails with a bunch of errors
Output is like this:
And when i manually enter
print(file.open("test", "w+"))
I getnil
as the output.Despite the fact that the Node has been reflashed many times on many different settings the following files still appear from before the node was flashed for the first time:
The NodeMCU has been reflashed with:
every combination of Flash speed and Flash size.
I have run
file.format()
but nothing changedThe text was updated successfully, but these errors were encountered: