4 ms·
The penalty for using linux & micropython in an embedded platform is enormous: power and performance with both will be inferior to a baremetal or RToS solution
by sbf501 4y ago
The penalty for using linux & micropython in an embedded platform is enormous: power and performance with both will be inferior to a baremetal or RToS solution and C.
As an embedded developer, you are far better off learning how to use the BSPs for the major embedded semi vendors, such as NXP, STMicro, and Renesas. No one is going to ship a battery powered IoT product that runs linux (and make money).
- tverbeure 4y agoMicroPython is totally fine for initial prototyping or for slow embedded control. Here's a good example of a project of mine where I used MicroPython: https://twitter.com/tom_verbeure/status/1536127568931217408 https://twitter.com/tom_verbeure/status/1536127568931217408. I needed a way to quickly drive a bunch LEDs but I didn't want to dive into C yet. Too about 20min to install MicroPython on the RP2040 (no clue why you're bringing up Linux) and get my LEDs going. Perfect! In a later phase, I'll convert to C, once MicroPython runs out of steam. For a lot of slow control projects, that will never be necessary.
- yellowapple 4y agoThe Pico doesn't run Linux. It does optionally run MicroPython or CircuitPython (I recently used the latter w/ a Pico for a friend's cosplay blaster pistol), but the C/C++ SDK is baremetal.