I noticed something else:
I am using esptools to flash. I use this command:
Code: Select all
python esptool.py -p /dev/ttyUSB0 --baud 115200 write_flash --flash_size=4m 0 esp8266-2016-07-19-v1.8.2-19-gc3f519a.bin
When it has finished, I return GPIO0 to 'HIGH' and power reset the board. The following output appears, partially corrupted:
Code: Select all
���Performing initial setup
bcn 0
del if1
usl
add if1
#4 ets_task(4020e374, 29, 3fff7060, 10)
dhcp server start:(ip:192.168.4.1,mask:255.255.255.0,gw:192.168.4.1)
bcn 100
Fatal exception�3Fatal exception�0Fatal exception�0Fatal exception�0Fatal exception�0Fatal exception
If at that point I power cycle it again, I get:
Code: Select all
��c쏜�$��$���dsdÃl'�p{l�l��<��{g#���could not open file 'boot.py' for reading
could not open file 'main.py' for reading
#4 ets_task(4010035c, 3, 3fff62f0, 4)
MicroPython v1.8.2-19-gc3f519a on 2016-07-19; ESP module with ESP8266
Type "help()" for more information.
>>>
But I don't see 'Performing initial setup' again whether I power cycle or just use RESET.
So I assume that after flashing with a new bin, Micropython does a few initial setups on the flash - presumably including adding the port_config.py and others - right?
So I guess that if 'performing initial setup' hits fatal exceptions, the file system is not completed...
Any fixes?
Thanks