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!
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.
ModBus mit dem Raspberry Pi Pico
Hello #MakerMonday, it's time for #micropython. I built a giant colorful #legoeducation #RaspberryPi4 robot powered by the official @rpimag Build HAT. The battery pack is hidden under the platform. I am such a genius!
#maker #programming #STEM #robotics
For those not following #m68kMicroPython development, a lot has been happening rather quickly in the last couple of weeks!
There's enough support for the Toolbox now that I've been able to re-create the #Macstodon splash/loading screen with it - see below.
Big thanks to @stylus for all his hard work developing the port and making this possible!
#RetroComputing #RetroProgramming #VintageMac #Apple #Mac #MacOS #ClassicMac #68k #Python #MicroPython https://oldbytes.space/@smallsco/114889267494614758
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
It's teacher Tuesday!!
If you're teaching with or learning Raspberry Pi Pico programming using #MicroPython I've just shared five introductory programming activities for BEAPER Pico that you can easily adapt to other circuits!
Check them out: https://github.com/mirobotech/BEAPER-Pico
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.
Lua beats MicroPython for serious embedded devs
https://www.embedded.com/why-lua-beats-micropython-for-serious-embedded-devs
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.
Doing a little iterative code development in micropython on an emulated m68k mac... I might not be so happy with the loading time if a real floppy was involved, but in an emulator it's heckin' snappy.
Clearly I need to tackle the issue that you can't REALLY draw to the same window as the terminal....
Now you can witness one of the first quickdraw calls from MicroPython on mac...
I found a nice way to interact with the S0 counting bus of my three energy meters. Every single used GPIO pin gets it's own interrupt for measuring the time in between last 1->0 change. Every 15 seconds a mqtt broadcast is done to report the average consumption. In addition a one hour and 24 hour sum array is filled too. So no need for PIO operations any more.
#Tinkering #Raspberry #PiPico2W #MicroPython
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"
@cymplecy @lpoolmakefest
and in case you want to use #MicroPython on this thing:
https://pybricks.com/project/technic-42146-powered-up-remote/
#CC2tv #403 Vom `print()` zum #Bit
So spricht dein #Mikrocontroller
Wir zeigen, wie ein einziger #MicroPython-Befehl – `print("Hallo Welt")` – Schicht für Schicht bis zum elektrischen Signal am TX-Pin zerlegt wird. Wir starten in der Hochsprache, werfen einen Blick auf den erzeugten #Bytecode und zeigen, wie die MicroPython-VM ihn in C-Routinen übersetzt. Von dort gelangt der String über den #UART-Treiber als #ARM- #Maschinencode auf den RP2040-Prozessor
Moin! Wieder gibt es eine neue Folge #CC2tv – So spricht dein Mikrocontroller ️
https://youtu.be/gFAGxDAAyNU
Wir zeigen, wie ein einziger #MicroPython-Befehl – `print("Hallo Welt")` – Schicht für Schicht bis zum elektrischen Signal am TX-Pin zerlegt wird.
Wir starten in der Hochsprache, werfen einen Blick auf den erzeugten #Bytecode und zeigen, wie die MicroPython-VM ihn in C-Routinen übersetzt. Von dort gelangt der String über den UART-Treiber als ARM-Maschinencode auf den #RP2040-Prozessor und schließlich als 3,3-Volt-Bits aufs Kabel. #cc2
@xavi
You will always need bus and display drivers for this; either loaded as part of your project, or a #MicroPython firmware with a drivers built-in.
#QSPI is 'Quad SPI', a very fast display bus. The #ESP32 micropython port does not support this natively, so you need a driver for that.
It may get added in the future, See discussion here, etc:
https://github.com/orgs/micropython/discussions/14333#discussioncomment-9219699
You also need a driver for the SH8601 itself (this will use the QSPI bus).
Have a look at this page; which has a pre-compiled, non-lvgl firmware supporting your board + display.
https://github.com/dobodu/Lilygo-Amoled-Micropython
Personally; I think you want to go the #LVGL route anyway; It's more of an ecosystem than just a set of display drivers. You get the tools and libraries to use the display effectively, as well as the hardware support.
Micropython itself does not build in any drivers or features for this sort of display. It has basic framebuffer support but this is intended for tiny OLED's etc. Not large color displays. Indeed, a framebuffer for this display would be 688K in size.. larger than the system RAM.
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