MicroPython Forum (Archive)

That works for me, on a fresh built firmware. The question is, what is in you boot.py. Mine looks like: # This file is executed on every boot (including wake-boot from deepsleep) import esp esp.osdebug(None) import uos, machine uos.dupterm(machine.UART(0, 115200), 1) import gc #import webrepl #webre...

No. Damien should know.

Look at the repositories of @pythconcoder (e.g. here_ viewtopic.php?f=14&t=5299#p30417) or @mcauser or @dhylands or @deshipu. They have made drivers for many LCD displays.
Or search though this section of the forum: viewforum.php?f=14

There is an OTA variant for ESP8266. Just look into the download section.

Since you mention Bluetooth and WiPy, I assum that you use a WiPy2 or WiPy3 from Pycom with an ESP32 processor.
For that device you have to ask as forum.pycom.io.
Besides that, you may use uasyncio in both variants of MicroPython with slight differences.

I cannot confirm. On Pyboard it is still there. And on the other devices it never existed.

The README.md in ports/esp8266 is sufficient. You only have to follow the instructions literally, not skipping a step or ignoring a word, including the README in the installed esp-idf. About not installing modules: in the esp8266 directory there is a file called mpconfigport.h, which includes define...

There is no need for a specific terminal, just some means to pick up the messages sent by the pyboard through its cdc interface, the same path which told you the error messages.

Which pyboard and which firmware are you using. You get the information py pushing Ctrl-B at the REPL prompt.

First of all, the value of the series resistors is too small. They would transform a range 0-1V into 0-12V. But a fully charged 12V (lead) battery has a voltage of about 14.4 V. Why not take something like 1.5 MOhm. Besides that, you calculation seems OK, assuming that d1 is the value obtained from ...