Slow Process Of Replacing Raspberry Pi 3
While there are upsides in consolidating hardware to a single vendor, there are risks of supply chain hell that we’ve seen with the Pi 4 and it makes more sense to look at options.
With the Pi 4 still being a mess, it makes more sense to look at the best Pi-style I/O with the most out of the box compatibility with most hats.
-NanoPi M4V2: Not really my first pick since it costs $80 USD, however it uses the Rockchip 3399 which is a dual-core A72 at 2Ghz with a Quad Core Cortex-A53 at 1.5Ghz and for the most part is the closest you’ll get to a Pi 4 level of performance with a mixed core solution in a credit card sized board. Only reason I put it at the top of the list is the number of Linux distros supported.
-Banana Pi BPI-M5: Amlogic S905X3 quad-core Cortex-A55, having four USB 3.0 ports like the NanoPi M4V2 makes this the ideal choice. Prices vary between $85-99 so the NanoPi M4V2 sits at the top of the list as the better value.
-StarFive VisionFive 2: A quad-core RISC-V at 1.5Ghz looks good which is an improvement from the original dual-core, price points are decent since there is a 2GB, 4GB & 8GB model options… the only headache is Ubuntu seems to be the only supported OS for a mainstream support OS, while it does list Fedora & Debian were added recently I’m not expecting much on the Fedora side. Since some projects of mine that run on a Pi 3B aren’t that CPU demanding, RISC-V wouldn’t have the scale of risk with trying to run something that expects a Pi 4 A72 level of performance.
Wearable Computer 3.0, High Performance Mobility
With all the effort put into a Pi-style I/O breakout for x86/x64 using a laptop’s built-in smartcard reader slot connector, it opened the door towards “High Performance Mobility” than continuing the “Spudnik Wearable Computer 2.0”. While the Rock64 wasn’t bad, having to use a Bluetooth module for medical/biosensor duty pushed the power usage limits and using multiple input interfaces kept going into low power errors. A work-around on Rock64 was use the 2nd battery pack power port to power a USB hub which required extra cable management–Rock64 isn’t alone in the USB port power issue, USB-C powered Celeron J4125 Mini PCs hit this wall frequently.
Input devices lead to interesting discoveries of what works or doesn’t work. Muscle sensor experiment worked better to accessing OS/UI menus with gestures… experimented with “force levels”(slow vs fast movement) and it made the virtual mouse pointer fly around the screen or scroll too slow/fast in menus. Re-purpose a phone touchscreen as an input device had its own issues, text input lag varied due to trying to tune the digitizer for a PalmOS style Graffiti. If anyone has used laptops long enough you may have used many trackpad makers, for laughs got an Alps trackpad to work via USB and figured out you can do “alt-modes” to simulate a keyboard input via PalmOS style Graffiti. The only downside when it came to language support the more characters/complex input, performance of the CPU starts to make a difference… note to self “don’t go into IKEA level of combining a bunch of words together to get a funny or unique German word/term”.
Keeping the UI clean and only displaying important info makes it look clean, the concept is have a sidebar that displays health/biosensor data at all times similar to KDE/Windows 7 style widgets. On a bare minimal it would perform very good with a 720p based display glasses.
As far as hardware testing considering the Celeron N4020 only weakness was input lag creeping up, I’m sure a mobile Pentium Silver/Gold would strike the balance of multi-core performance to watt ratio.