Could not open file 'boot.py' could not open file 'main.py' for reading #2255
Comments
|
What issue is being reported here? |
|
Failure to expand the filesystem or set itself correctly. Or am I missing something? If the esp has more than 1Mb flash, it should On Saturday, 23 July 2016, Paul Sokolovsky notifications@github.com wrote:
Martín Lombana / Creative Director MOBILE: +34 633 63 02 35 |
So, where's failure? Info provided by you doesn't show anything even remotely resembling a failure.
You apparently write the above with some unspoken assumptions, but these assumptions aren't clear to other people, e.g. me. Try to make them explicit. |
|
Hello pfalcon, I am sorry if I was not clear enough, or specific enough. I followed all the installation process in the esp-01, as stated in the documentation in a esp8266-01. When I try to use any function in that setup that involves the filesystem, I just get errors. But the board has 1MB memory and is propertly flashed. Like for instance or this ( wich outputs that, and then seems to reboots the serial connection and the esp8266 (as you see in the serial output specified here, it tries again to read the main.py and boot.py):
load 0x40100000, len 30816, room 16 If i then run again the same command, it can not allocate the memory: '''
I apologize if I was not specific enough. Because of the above tests I think the filesystem doesn't expand correctly although it has the room for it and the board was flashed with the corresponding flag. Or you still think I am missing something completely? (which can be the case, I don't say the contrary) Thanks, |
|
I just flashed esp8266-2016-07-23-v1.8.2-40-g0d22177.bin, and it works. esp8266-2016-07-23-v1.8.2-39-g2dd21d9 didn't work. So chances are there was indeed an induced bug in that version, as I said, based on empiric testing. If I flash that one, it doesn't work. If I flash the newly released esp8266-2016-07-23-v1.8.2-40-g0d22177.bin, it works. ( Or, it is a miracle. ) |
Well, your original description didn't include that info, and that of course clarifies it.
It likely is - there were no changes which could explain that. Please confirm that you got those binaries from http://micropython.org/download/#esp8266 . Also, if you can, please attach esp8266-2016-07-23-v1.8.2-39-g2dd21d9.bin here - as it's gone from download page, I can't test it myself. Otherwise, here's what's currently known about such issues: http://forum.micropython.org/viewtopic.php?f=16&t=1908 (last question of the FAQ as of now). Please keep us posted if you face similar issue with a newer daily build again (and keep esp8266-2016-07-23-v1.8.2-40-g0d22177.bin handy, to use it as a known-working reference). |
|
Hello Again, I see, you are right. I should have included that example in the first place for clarity's sake. I just found other users with the same problem in the forum: https://forum.micropython.org/viewtopic.php?p=12285#p12285 I provided an alternative and possible solution, because from time to time my esptool fails when flashing and keeps stopping at 99%, so it might be related (but I am unsure, because I can't reproduce it now with the new version). Here is the bins that you asked for, if you can try them out in a ESP8266-01 with 1MB flash: |
I just successfully flashed the latest version esp8266-2016-07-23-v1.8.2-39-g2dd21d9 to an ESP-01 (Black) with 1MB of Flash memory, with:
But it seems the filesystem never got expanded, therefore it never reads boot.py and main.py.
Serial output:
However, I do have 1MB and it seems propertly configured:
Output from diag_port:
The text was updated successfully, but these errors were encountered: