We have a new release of #MicroPython v1.26 dropped yesterday and has added I2CTarget (aka I2C Slave) and a whole plethora of improvements and refinements.

https://github.com/micropython/micropython/releases/tag/v1.26.0

Also this article https://randomnerdtutorials.com/raspberry-pi-pico-w-bluetooth-low-energy-micropython/ another potential option for getting the data from our #Bluetooth batteries using #micropython on a #pipico2w
They have what looks a good book too https://randomnerdtutorials.com/raspberry-pi-pico-w-micropython-ebook/

ooh interesting. Someone else is working on MicroPython for m68k.

I just discovered https://github.com/yunkya2/micropython-x68k/tree/port-x68k/ports/x68k The documentation is all in Japanese and I haven't plugged it into a translator yet to find out the details except that possibly this version is for Sharp X680x0.

#retroComputing #m68k-micropython #micropython

Fuck me! A PR I opened adding PCNT support to the ESP32 #MicroPython port *four* years ago last week has just been merged!

Which is great news as I've got two projects in flight that are going to need it and I can finally stop maintaining my own fork

Watching the #Micropython test suite running on TinyQV, my Risc-V SoC. An increasing number of tests pass With the #TinyTapeout competition using it, I'm trying to make sure there's no lurking issues!

I have a few of these, well, will have a few more over next week...

https://www.tindie.com/products/revk/esp32-s3-mini-1-n4-r2-dev-board-all-gpios/

I am tweaking the design but all of them do 2A 3.3V power for many peripherals, and ALL the GPIOs for an ESP32-S3-MINI-1-N4-R2, and a single WS2812 LED.

USB-C and DC 5V-17V

They are ideal for anyone wanting to play around with these processors, whether native ESP IDF, #micropython, #arduino, or whatever.

#m68kMicroPython happenings: The "struct-types" branch is coming along. There are now autogenerated bindings for the following parts of the API: modmactypes.c
modqd.c
modtoolboxevent.c
modtoolboxutil.c
modwindowmgr.c

there's probably broken stuff but for instance you can now splat directly onto the screen

>>> scrn = qd.qdGlobals().screenBits
>>> n = scrn.bounds.bottom * scrn.rowBytes
>>> for i in range(n): scrn.baseAddr[i] = i

and types are checked:

>>> qd.FillRect(7, "blue")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: Expected int, got Rect

um well except the error message is backwards

and in upstream #micropython land my exploration found that there were problems with the uctypes module and "REPR_B", so I'm working on fixing that and ensuring it stays fixed via the CI system: https://github.com/micropython/micropython/pull/17688

right at the moment, the micropython PR is failing for some reason that will probably be more obvious to me once I've had another night to recover from jet lag.

Why Lua Beats MicroPython for Serious Embedded Devs

｢ Lua isn’t just compatible with embedded systems; the Lua ANSI C library was designed for them. Its architecture is clean, compact, and deterministic.

MicroPython, on the other hand, is a reimplementation of Python 3. It works well for many embedded use cases, but it inherits assumptions from a desktop-oriented language ｣

https://www.embedded.com/why-lua-beats-micropython-for-serious-embedded-devs

I just published a #micropython #mqtt server and #python client for accessing a remote filesystem on a micropython device by mqtt.

See:

https://github.com/dov/upython-mqtt-file-server

Meanwhile I have used it for uploading photos to my #pimoroni #presto device.

This library solves the "grandma problem" of how to place a photo frame on grandma's mantle piece and push images to it without her interaction.

I am a sucker for opto-electronics, so got this discarded kit (ex CNN's London studio?)

Each button has a 36x24 LCD display and red+green LEDS.

Well-designed hardware: ColdFire (=68k) CPU, plenty of RAM, plenty of FLASH, serial port, ethernet etc.

Firmware ? Not so impressive, but very easy to get rid of:

Anybody can flash new firmware from ethernet: No userid, no password, all you need to know is the IP# and how they botched their CRC-16 implementation.

Now it runs #MicroPython :-)

My latest blog post: Metronalmost

https://mikecoats.com/metronalmost/

This metronome, by design, will never, ever, tick exactly once per second. This infuriating object is designed to thwart the goals of @hackaday's One Hertz Challenge contest.

how it started: "let's try to get started on a set for my #RFFF25 gig"

how it's going: "attempting (and so far failing) to completely rewrite some 2-year-old #MicroPython code on my DIY MIDI to CV interface"

Is there anyone in the room with knowledge about #ESP32 microcontrollers?

I am playing with a #Waveshare development board that has an #AMOLED and a touchscreen, and it says it has built-in #SH8601 display driver and #FT3168 capacitive touch chip, using #QSPI and #I2C communication respectively.

https://www.waveshare.com/product/arduino/boards-kits/esp32-s3-touch-amoled-1.8.htm

It directly works in #Arduino with #C, but I am trying to make it work with #MicroPython.

Before I spend effort trying to compile it with #LVGL, I want to know if I could print a "Hello World" to the screen as is, and while my mind tells me that I need a driver, the sentence "built-in display driver using QSPI" makes me think that I could eventually use the display without code drivers, but I don't know how.

I'd love to see an example, if it's possible, or to be pointed to any resources that I can read in this regard. I am complete newbie.

Re-posts are appreciated.

Thank in advance