MicroPythonOS – An Android-like OS for microcontrollers
(micropythonos.com)119 points by alefnula 4 days ago
119 points by alefnula 4 days ago
Serious recommendation: I would not have R. Kelly anywhere on your project page.
If you’re trying to give a 30 second elevator pitch about what your project does, you should not have a name be a guy spending 30+ years in prison for child sexual abuse.
Ooooops, I didn't notice it on a first quick look. Yeah, I'm with you.
As an alternative: MicroHydra [0]
Also, if you hate the REPL app, bug me to fix it.
Hidden project members, masked domain info and offshore hosting designed to avoid dcma. No thanks.
A great playground for learning embedded systems, even if not ideal for every production use case.
Those tech bros should just...stop.
SBC is already cheap enough that you can throwaway without caring anything. Stop bloating MCU with....useless stuff.
If anyone suggest me "Python in mcu" professionally, i would never be able to trust them again.
We aren't in the 1980's any longer, most of these systems are way more powerful than a typical 16 bit home computer, and incrediblly as it sounds, those 16 bit home computers still had better tooling than most MCUs have nowadays.
Anything that brings MCU tooling into the 21st century is very much welcomed.
The advantage of micropython is that you don't have to deal with all the poorly maintained toolchains and UART and flashing and whatnot; for a novice working on their own, that stuff is a nearly insurmountable barrier. That the syntax is Python doesn't make a whole lot of difference.
I agree though, probably shouldn't be the first choice for a professional application.
It's actually a great first choice for a professional application, in that you can get a prototype up and running much faster than a native SDK, iterate quickly, and try things out on a repl. In fact, it's used in industrial settings, including in medical devices and energy distribution.
MicroPython's a bytecode interpreter so, other than the existing Python ecosystem being a huge boon (popularity being a form of strength), you could get many of the same benefits and more from wasm
If we forget about the pain that most WASM toolchains happen to be.
MicroPython, like most BASIC interpreters in 8 bit days, also allows for inline Assembly.
As for running bytecode on MCU that is as old as MCU themselves, wasm doesn't bring anything to table.
I work on the micros that aren’t plugged I to a grid. So solar and batteries and the like. In that world, power consumption is everything. Interrupts and aggressive sleeping of your processor are you biggest tool.
Does anyone have any experience with current draw of typical pieces of “firmware” using this? I see that it’s on the larger side of what feels like micro, BUT tomorrows micro has been growing heaps over yesterdays micros for a long time, so I can ignore that.