Re:The Raspberry Pi 5 Is No Match for a Tini-Mini-Micro PC
by 05 on Sunday June 16, 2024 @02:50PM
(#40699180)
Yocto works the same way whether it’s Pi or iMX, most of the learning curve has nothing to do with the SoC. So it’s really strange to hear that your Pi workflow is better than anything you’d get with another chip..
Re:The Raspberry Pi 5 Is No Match for a Tini-Mini-Micro PC
by transpute on Sunday June 16, 2024 @03:13PM
(#40699350)
BSP quality is famously variable by board vendor, https://www.youtube.com/watch?v=niH1-NB6W8w
Two products.. leveraged a Yocto-based board support package (BSP); one being in AgTech, and the other being in the veterinary space. These products have followed disparate practices when leveraging the BSP for custom hardware and software.. this talk [described] the two products, how the BSP was customized and used, and the resulting consequences.*
Re:The Raspberry Pi 5 Is No Match for a Tini-Mini-Micro PC
by nottorp on Sunday June 16, 2024 @03:25PM
(#40699424)
But on a Pi you don't have to use Yocto. Raspbian is always faster to develop for.
Source: have worked on both Pi based solutions and custom hardware with yocto.
Re:The Raspberry Pi 5 Is No Match for a Tini-Mini-Micro PC
by 05 on Sunday June 16, 2024 @06:32PM
(#40700667)
Yeah, one is easier and the other is right. Shipping a reproducibly built readonly rootfs image takes longer, but is strictly better than putting 'some' versions of Debian packages on the SD card and calling it a day.
It's the Arduino curse - sure, it's faster to ship Hello World with Arduino but soon you realize all your libraries were built by beginners and use delay() everywhere so you're screwed if you need two peripherals to work at once.
You use Pi for prototypes and one-offs, not where you need to ship something that's actually competitive on BoM.
Re:The Raspberry Pi 5 Is No Match for a Tini-Mini-Micro PC
by ajb on Sunday June 16, 2024 @09:53PM
(#40701653)
These days you can make anything have a readonly rootfs by using overlayfs. Just wipe your overlay partition to do a factory reset.
Re:The Raspberry Pi 5 Is No Match for a Tini-Mini-Micro PC
by nottorp on Monday June 17, 2024 @02:53AM
(#40702938)
> something that's actually competitive on BoM.
Some applications are profitable at only hundreds of devices deployed. In which case, the moment you say "BoM" the hardware bill triples.
If you ship thousands to millions, of course you're right.
Re:The Raspberry Pi 5 Is No Match for a Tini-Mini-Micro PC
by bloggie on Sunday June 16, 2024 @03:33PM
(#40699478)
Not using Yocto simplifies and speeds development extremely, unless you have dedicated staff familiar with Yocto. It’s a big reason to prefer Pi.
Re:The Raspberry Pi 5 Is No Match for a Tini-Mini-Micro PC
by lhl on Monday June 17, 2024 @04:08AM
(#40703364)
No, your memory is spot on. I also eval'd dozens of ARM (and some x86) SBCs for embedded use back in the early/mid-2010s and most of the BSPs were awful. You'd be locked into some ancient several-year old Linux kernels and documentation (and even actual hardware support) was often buggy/incomplete. God help you if you need to customize the boot/spin your own (Yocto was still new then, I assume life is a bit easier now).
Before RPi became really popular and the 4 came out, I used BeagleBoard, PandaBoard, Aria G25, Gumstix, Cubieboard, i.MX devkits, and spun custom boards using Marvell, TI, Freescale (now NXP), and Qualcomm CPUs - I don't remember any of them having as good a BSP or being as easy to develop with as the RPi was five years ago. Maybe my memory is (very) faulty but the experience was leagues worse. PTSD-inducing level of worse. I wasted weeks or months on every major project shaving silicon yaks that should have been handled by the vendor (and is now handled by the RPi community).
The modern i.MX toolchain may now be comparable many years later but I've long since given up on everything else since CM4 came out in 2020.
My understanding is that they lost the sweetheart deal after they pivoted to supporting commercial, right in time for the pandemic supply crunch.