toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

315
active users

#micropython

2 posts2 participants0 posts today

After a week of FA&FO I Found Out that flashing #MicroPython to an #esp32 cam module is an epic fail. Easy enough to find the firmware and use esptool.py to flash it to the board but hooking it up to an IDE was an exercise in futility.

Has anyone in the Fediverse had success doing what I have declared impossible? Success stories and insights appreciated.

Meanwhile, it's back to #Arduino to write the code I want to write, just not with uPython.

I just backed this project on Kickstarter: kickstarter.com/projects/openm

OpenMV LLC makes some incredibly powerful, small-form-factor #IoT cameras perfect for tinkering, prototyping, and making slick projects. I taught my Computer Vision with #AI course using their cameras. I'm excited about this new series: full object detection for a few mW. #EdgeAI #ComputerVision #Arduino #MicroPython #embedded #microcontroller

I realized that light strip I installed some time ago used an ESP8266 microcontroller, so instead of buying and waiting for a new Raspberry Pi for a project, I tried to use that instead. I got MicroPython running on it, and wow, this thing is cool! I was able to connect to the internet, and even run a server on it. Using the GPIO pins to control an LED was simple. Setting up a button was slightly more work since there wasn't a helper class, but fairly easy in the end.

Replied to Stewart Russell

@scruss You can get most of the info in the banner string from sys.implementation - specifically the last part is printed in the sys.implementation string and also available in the MicroPython-specific field sys.implementation._machine

docs.micropython.org/en/latest

This confusing state of affairs is IMO a result of Python also having too many different ways to get very similar bits of platform information. 🙃

docs.micropython.orgsys – system specific functions — MicroPython latest documentation

TIL that getting #MicroPython to return cross-platform CPU type and processor speed is remarkably hard:

* os.uname() isn't available on some platforms (particularly SAMD)

* machine.freq() returns an integer on most platforms, but a tuple on STM32

* platform.platform() doesn't return CPU type

* The banner string (eg: "MicroPython v1.24.1 on 2024-11-29; Seeed Xiao with SAMD21G18A") contains useful info, but can't be read programmatically

Having an introverted few days, and I could be playing fancy new games on a Steam Deck - only instead I'm programming a tiny little game on a BBC micro:bit.

5x5 red LEDs, with brightness adjustable from 0 to 9! Two buttons! Squeaky little speaker, for beepy sound effects and gleefully robotic speech synthesis!

(Game is 'Volcano Escape' - it started off as a simple driving game but, with creative input from the 7-year-old nephew, now has a Proper Setting...)