New *early access* mp-esp8266-firmware-vXY.bin on ESP8266

[Damien]

Just out of curiosity, the 'pyb' module methods of PyBoard and the 'machine' methods of ESP8266 are syntactically different even if referring to same functions. E.g. 'i2c.send()' of PyBoard's pyb vs 'i2c.writeto()' of ESP8266's machine. Is there a specific reason for this?

We are switching over to a new hardware API that should be general enough to cover all the different boards that MicroPython can run on. This new API uses the "machine" module, and the I2C (and SPI, etc) methods are called different things and have different behaviour (to make them more consistent and general). The pyboard also has the "machine" module but does not (yet) implement all of the new API.

[Damien]

I can confirm that with WEMOS D1 mini were no problems... installation, WLAN, ST, AP... everything OK.
Trying NeoPixel got an error.... NameError: name 'NeoPixel' is not defined.
Any advice?

Instead of NeoPixel, use neopixel.NeoPixel.

[Photon Peddler]

Hi, Damien.

I programmed a cheap ESP-01 module from MCM with the binary you sent. It works great!

A question: It seems that MicroPython stores the ESSID and password somewhere, so that the module can reconnect after a reset. Is there a way to erase this information, so that I don't leak the network name and password when loaning the module to someone else?

[platforma]

A question: It seems that MicroPython stores the ESSID and password somewhere, so that the module can reconnect after a reset. Is there a way to erase this information, so that I don't leak the network name and password when loaning the module to someone else?

That's an interesting question, I don't think you will be "leaking" the ssid/pwd. I don't believe this feature exists yet. It is probably possible to erase the whole flash sector where the config is stored in flash using esp.flash_erase(). As for the API, it might be useful to have a call similar to wlan.forget() or wlan.persistent(False) or something rather. Forgetting can be done with SDK:

Code: Select all

wifi_softap_set_config()

and set the config to NULL.

For station mode, there are similar calls in the SDK:

Code: Select all

wifi_station_set_config_current(); // I believe will not store the station config
wifi_station_set_auto_connect(0); // prevent from connecting

I might be wrong with all this though! :)

[deshipu]

The firmware is great and so far runs very well. I had it crash on me when I used os.listdir() right after creating the filesystem (by importing boot_), but I suppose that this is the result of some buffering. I'm especially happy about the I2C functionality, even though it's write only so far, because it allows me to control other boards using micropython.

I have one question, however. I noticed that the modules saved on the internal filesystem are not available until you do "import boot_". That's understandable. However, I also noticed the "could not find module 'boot'" message, even when I have the "boot.py" file created. My guess is that it can't run it precisely because the filesystem is not mounted... So, is there any way of having our own code run on startup now? I'm in a chicken-and-egg situation now, as I would like to put "import boot_" in "boot.py" to have it run on startup, but "boot.py" won't be run without importing "boot_" first...

[profra]

I can confirm that with WEMOS D1 mini were no problems... installation, WLAN, ST, AP... everything OK.
Trying NeoPixel got an error.... NameError: name 'NeoPixel' is not defined.
Any advice?

Instead of NeoPixel, use neopixel.NeoPixel.

Yes , I found it after a while , please correct it on the website...

[thoralt]

So, is there any way of having our own code run on startup now? I'm in a chicken-and-egg situation now, as I would like to put "import boot_" in "boot.py" to have it run on startup, but "boot.py" won't be run without importing "boot_" first...

I second that. Do we have the possibility to run own python code on startup or is this not yet implemented? Does anyone know?

To the developers: Thank you for all the work! This is an awesome project! I couldn't resist throwing in some coins at Kickstarter

Thoralt

[mpymike]

I've been programming a bunch of ESP01s of dubious quality...
A couple of them gave me this boot_ error.

Code: Select all

MicroPython v1.5.2-395-g5f6d12c on 2016-03-08; ESP module with ESP8266
Type "help()" for more information.
>>> import esp
>>> esp.osdebug(None)
>>>
>>>
>>> import boot_
ioctl(1, 0)
ioctl(5, 0)
readblocks(0, 3ffeef60(4096))
readblocks(0, 3ffef150(4096))
ioctl(1, 0)
ioctl(5, 0)
readblocks(0, 3ffef2b0(4096))
ioctl(1, 0)
ioctl(5, 0)
readblocks(0, 3ffef3c0(4096))
FAT filesystem appears to be corrupted. If you had important data there, you
may want to make a flash snapshot to try to recover it. Otherwise, perform
factory reprogramming of MicroPython firmware (completely erase flash, followed
by firmware programming).

FAT filesystem appears to be corrupted. If you had important data there, you
may want to make a flash snapshot to try to recover it. Otherwise, perform
factory reprogramming of MicroPython firmware (completely erase flash, followed
by firmware programming).

...repeats every 5secs...

Sometimes if I reflash it cleans it up, othertimes not.

[mad474]

I've been programming a bunch of ESP01s of dubious quality...
A couple of them gave me this boot_ error.

For 3 out of 3 ESP-01 with Manufacturer: c8, Device: 4013 I can confirm that error on running import boot_.
And 3 out of 3 ESP-01 with Manufacturer: e0, Device: 4014 go through "import boot_" flawlessly.

[mpymike]

How do you find out what the manufacturer and device codes are?