OSError 19 (ENODEV)

[QuAzI]

Thanks, now listdir() and os.statvfs works.

[raszga]

Hi,
Just a suggestion :
I did have some unhappy experiences trying to use the esptool under Debian 8 so now days I'm using the windows (7) version of the nodemcu flasher to l flash the ESP8266-12. (nodeMCU firmware programmer)
Hope this helps.

[wavesailor]

Thanks @raszga
That worked for me!!


[quote="raszga"]Thanks fort the response, I suspected some connection.
Now here is interesting, over the "faulty " part I ran from network module ( I loaded the last stable version from 09092016):
**************************************************************
import network
ap = network.WLAN(network.AP_IF) # create access-point interface
ap.active(True) # activate the interface
ap.config(essid='ESP-AP') # set the ESSID of the access point
***************************************************************

Ok this made the boot.py to appear under ListDir ad even further
**************************************************************
WebREPL daemon started on ws://192.168.4.1:8266
WebREPL daemon started on ws://0.0.0.0:8266
Started webrepl in setup mode
could not open file 'main.py' for reading

MicroPython v1.8.4-10-gbc28ac8 on 2016-09-09; ESP module with ESP8266
Type "help()" for more information.
>>> import os;os.listdir('')
['boot.py']
----------------------------
boot.py
----------------------------
>>>
*******************************************************************

Even more interesting the AP which is created is : MicroPython-e06659 with micropythoN password...
(I don't know how I remembered something about the password which I read somewhere)

*************************************************************************************

Hope this helps... it is confusing though....

CR[/quote]

[chenhting]

The dreadful error 19
OSError: [Errno 19] ENODEV
was cause by the earlier error
OSError: can't set AP config

What happened was that MicroPython flashed on ESP8266 did not activate AP, and AP config failed. Do the following to activate AP:
import network
ap=network.WLAN(network.AP_IF)
ap.active(True)

After AP is active, reset ESP8266, and MicroPython will load successfully.

Good luck!

Ting.

[hybotics]

If you're looking for a hint how to try to get passed it, it is to erase entire flash and to program it again - that's universal first step to try for any kind of "I flashed and see issues" problem, please see here: https://github.com/micropython/micropyt ... structions

I am also getting the ENODEV error. I have factory reset my v1.1 PyBoard, and restored everything that was on the file system. I am still getting the ENODEV error. I believe I may have messed something up the last time I flashed the PyBoard, because I did not use the "-d 483" switch. My PyBoard shows up as four different dfu capable devices when I do "dfu-util --list."

Is my PyBoard permanently gone? I can still access it via the serial console, and it still shows up as "PYBFLASH." I just can not get past the ENODEV error.

8-Dale

[pythoncoder]

...My PyBoard shows up as four different dfu capable devices when I do "dfu-util --list."...

It should do: see the docs.

If you're having trouble flashing a Pyboard I suggest you create a new topic in the right (Pyboard) subforum giving exact details of how you're doing it and what occurs. Please include details of your OS, the type of Pyboard you have and the exact firmware build you're trying to flash.

Hint: a common cause of failure is flashing the wrong build e.g. Pyboard firmware on a Pyboard Lite.