ESP8266 Community Forum

- Tue Oct 04, 2016 3:30 am #56035

Did you try with flash size 4*32m?

esptool.py currently can't use anything beyond 4 megabytes/32 megabits (nor can esptool-ck), the d1 mini pro seems to be the first board with more than 4MB, using 128m there will just return an error.

- Tue Oct 04, 2016 1:59 pm #56062 Looking at the discussion we currently have in https://github.com/nodemcu/nodemcu-firmware/pull/1525 about -fs option vs. autodetection and -correction of flash size, I'd guess that your issue is related. If I'm not completely wrong you face the problem that the firmware is smart enough to detect that your flash is 128 MBits and enforces this size (even though you set esptool.py to 32 MBits).

There once was PR https://github.com/nodemcu/nodemcu-firmware/pull/1367 to add 64m and 128m support which also upgraded the local esptool.py to support 64 & 128m chips. Try to flash with this version if you're feeling adventurous

BUT I'm not aware of positive reports that the current firmware works on 64/128m chips - see my note in https://github.com/nodemcu/nodemcu-firmware/pull/1390.

- Thu Oct 13, 2016 4:53 pm #56480 Latest updates on dev branch polished a couple of things. Most notably, the firmware will handle empty init data on its own, and 16Mbyte modules should work again (though not yet tested due to lack of hardware).

Code: Select allesptool.py --port <serial-port-of-ESP8266> erase_flash
esptool.py --port <serial-port-of-ESP8266> write_flash -fm <mode> 0x00000 <nodemcu-firmware>.bin

- Mon Oct 24, 2016 5:46 pm #57066 Wow, thanks for the update! I'll give it a try as soon as I find time!

Latest updates on dev branch polished a couple of things. Most notably, the firmware will handle empty init data on its own, and 16Mbyte modules should work again (though not yet tested due to lack of hardware).

Code: Select allesptool.py --port <serial-port-of-ESP8266> erase_flash
esptool.py --port <serial-port-of-ESP8266> write_flash -fm <mode> 0x00000 <nodemcu-firmware>.bin