MicroPython Forum (Archive)

Hi, I managed to remove ~100KBytes off the ESP32 MicroPython image, which is nice if you want OTA upgrades and a file system that's larger than a megabyte. Also good for 2-MB systems. I did this by removing support for PPP, IPv6, FAT, Ethernet, network loopback, threading, zlib and json. Dropping IP...

You could, however, start a periodic timer that schedules a procedure that feeds your WDT.

Why should micropython boot from the littlefs volume? It looks at the partition, sees that it's FAT, mounts that and is happy.

Yes there are pure-python MQTT brokers, hbmqtt for one. The problem is that it's basically unmaintained, and the fork that *is* maintained is based on anyio which hasn't been ported to micropython (yet, it's somewhere on my list of interesting things to do). Also, you will have moments with iffy net...

Hi, I'd like to share a package that uses a single TCP connection to a ESP32 (tested) / whatever else runs networked MicroPython (untested) device, which carries keepalive and watchdog FUSE and file access commands (FUSE works, the rest is TODO but very simple to add) MQTT messages REPL well … whate...

Well, it connects OK and says "Detecting chip type... ESP32", so I would assume that yes this is the correct port.

I have the same problem. The solution is to use an up-to-date esptool. Version 3.0 works for me. Debian's 2.65 or 2.8 did not.

The default domain is passed to you with DHCP. µPy doesn't seem to handle that. Open an issue …