This is totally inadequate:
"You might need to change the “port” setting to something else relevant for your PC. You may also need to reduce the baudrate if you get errors when flashing (eg down to 115200). The filename of the firmware should also match the file that you have."
More useful Windows example would be:
"C:\Users\User>esptool.py --port COM3 --baud 115200 write_flash --flash_size=detect 0 C:\Users\User\Downloads\esp8266-20180511-v1.9.4.bin"
Do you really need to erase, write and verify in three steps?
"For best results it is recommended to first erase the entire flash of your device before putting on new MicroPython firmware.
Currently we only support esptool.py to copy across the firmware. You can find this tool here: https://github.com/espressif/esptool/, or install it using pip:"
Better to explain:
Install with nodemcu-flasher tool for windows (the default standard) needs to be included for ESP8266: https://learn.adafruit.com/building-and ... -only-3-18 and full "erase_flash" process explained.platforma wrote: ↑Fri Mar 11, 2016 11:40 amIf you haven't done "erase_flash" with the esptool.py, or what have you. The chip will remember your last AP settings, depending on how you set them up. It is a "feature" of the ESP8266, so you don't have to reconfigure the AP every time you power up, and save some time. So it's no surprise that it still instantiates the AP if you haven't flashed clean
To clarify, Micropython or NodeMCU are not operating systems, rather user applications running in a vendor operating system (the one that comes with the ESP).