MicroPython Forum (Archive)

Any work on this issue? I am seeing some real performance differences between ESP32 and ESP8266 when responding to MQTT communication. The ESP8266 is snappy, the ESP32 takes 1 to 5 seconds to receive and respond to MQTT traffic initially, speeds up, then slows again. The same happened PicoW, but the...

But I am going to MISS the Snake cartoon!

Nothing specific, just happened to setup a WiFi class that I planned to use across various device types, ESP, Pico, etc., and since I wrote the class testing on Pico first, when I tested the class on ESP, kaboom. This is another of several now, deltas that I have found that is not expected per expec...

ESP UART lacks deinit method, but documentation states it exists? >>> from machine import UART >>> dir (UART) ['__class__', '__name__', 'any', 'read', 'readinto', 'readline', 'write', '__bases__', '__dict__', 'init'] >>> Reference https://docs.micropython.org/en/latest/library/machine.UART.html ... ...

Ok... Have custom Pico and Pico-W images that load, and work as far as I have tested thus far. These custom images don't have the various drivers and modules I wanted to excluded, so that is success! This was all learning/practice for creating a really lean ESP01 1MB firmware image. I will create a ...

Are you asking if you can integrate an ESP module to a Pico with no WiFi for example? Well, if so, it takes a few things: 1) ESP, depending on the how much memory it has, with an Arduino sketch or customized micropython image that is lean and mean enough to support the code. 2) You can use the UART ...

Oh! If I explicitly add it as 0 (disabled) in the mpconfigport.h file in the rp2 tree, or in the board configuration mpconfigboard.h file that will override the anything in the py tree, right?

Yes, unless you clean up, ugly issues. Odd, MICROPY_PY_FRAMEBUF does not exist in rp2 mpconfigport.h I do find it in other ports... /home/crosstoolng/micropython/extmod/modframebuf.c:#if MICROPY_PY_FRAMEBUF /home/crosstoolng/micropython/extmod/modframebuf.c:#endif // MICROPY_PY_FRAMEBUF /home/crosst...

And, I have not figure out how to remove the framebuf module? Only reference I can find to it is in extmod and it has no reference to it in any of the manifest files I have seen? So guess the question is, how to remove it? I would have thought when I removed the displays, it would be excluded but ap...

Ok, I did get the drivers and frozen modules excluded from the standard pico build image. For example, neopixel, dht, onewire excluded. Was not sure why ds18x20 disappeared at first, then I recalled it is 1-wire sensor, and since I removed such from mpconfigport.h, it can't exist, so all good so far...