sbc

Raspberry Pi this morning launched the Pi 500 and a new 15.6" Pi Monitor, for $90 and $100, respectively.

They're also selling a Pi 500 Kit, complete with a Power Supply, Mouse, and micro HDMI to HDMI cable, for $120. This is the first time Raspberry Pi is selling a complete package, where every part of a desktop computer could be Pi-branded—and makes me wonder if uniting all these parts into one could result in an eventual Pi Laptop...

Before we get too deep, no, the Pi 500 does not include a built-in M.2 slot. Sort-of.

Recently Joshua Riek posted he's dropping off from GitHub. If you haven't heard of him, he's one of the few reasons working with Linux on Rockchip SBCs is so much easier today than it was just a few years ago.

His Ubuntu Rockchip distribution is built for Ubuntu 22 and 24, and they've been maybe the most popular and stable way to run Ubuntu on Rockchip devices.

So popular, in fact, that manufacturers who use Rockchip, like Turing Pi, build their own official images on top of Joshua's.

Now, if you're reminded of XKCD #2347, yeah, I am too.

If anyone asks why I prefer to work with Raspberry Pis when I want to tinker on a random project, consider:

I just spent the past hour with a brand new ArmSoM Sige7 board (see my debugging notes in my sbc-reviews repo). This SBC has been on the market for months, with glowing reviews all the way back in May...

At first glance, especially from the top, the Radxa X4 is your typical Arm SBC:

But you'll quickly notice the lack of an SoC—that's on the bottom. Looking more closely, what's a Raspberry Pi chip doing on top?! First, let's flip over the board to investigate. There's the SoC: definitely not Arm inside, this thing's an Intel N100:

I have all my benchmarks and notes bringing up this board stored in my sbc-reviews GitHub repository: Radxa X4 - geerlingguy's sbc-reviews, and I also summarized everything in a video on YouTube, which you can watch inline (or skip past and read this blog post instead):

Ansible runs on Python, and Python runs on... well pretty much everything. Including newer RISC-V machines.

But Ansible has a lot of dependencies, and some of these dependencies have caused frustration from time to time on x86 and Arm (so having issues with a dependency is just a way of life when you enter dependency hell)... but in this case, for the past few months, I've never had luck installing Ansible from PyPI (Python's Package Index) on any RISC-V system, using pip install ansible.

I prefer installing this way (rather than compiling from source or from system packages) because it generally gets the latest version of Ansible, with an easy upgrade/downgrade path. It's also easy to add ansible to a Python requirements.txt file and install it alongside other package dependencies.

Regardless, the cryptography library, which requires a Rust compiler to build if the package is not already built for a particular system, has made it difficult to install Ansible from pip:

LattePanda's been building Intel-based SBCs for almost a decade, but until now, they've never attempted to unite an Intel x86 chip with the popular SoM-style form factor Raspberry Pi's dominated with their Compute Module boards.

This year they've introduced the LattePanda Mu, a SoM that marries an Intel N100 SoC with a new edge connector standard they've designed, using a DDR4 SODIMM form factor.

Right now they offer two carrier boards: a lite version with basic interfaces and a couple 2230-size M.2 slots for SSDs and wireless, and a full evaluation carrier that breaks out every hardware interface in a Mini ITX-sized motherboard.

For years, SBCs that aren't Raspberry Pis experimented with eMMC and M.2 storage interfaces. While the Raspberry Pi went from full-size SD card in the first generation to microSD in every generation following (Compute Modules excluded), other vendors like Radxa, Orange Pi, Banana Pi, etc. have been all over the place.

Still, most of the time a fallback microSD card slot remains.

But microSD cards—even the fastest UHS-II/A2/V90/etc. ones that advertise hundreds of MB/sec—are laggards when it comes to any kind of SBC workflow.

The two main reasons they're used are cost and size. They're tiny, and they don't cost much, especially if you don't shell out for industrial-rated microSD cards.

tl;dr: Sipeed sent a Lichee Console 4A to test. It has a T-Head TH1520 4-core RISC-V CPU that's on par with 2-3 generations-old Arm SBC CPUs, and is in a fun but impractical netbook/cyberdeck form factor. Here's my video on the Lichee Console 4A, and here's all my test data on GitHub.

Last year I tested the StarFive VisionFive 2 and Milk-V Mars CM—both machines ran the JH7110, a 4-core RISC-V SoC that was slower than a Pi 3.

Sipeed introduced the Lichee Pi 4A line of computers, offering a slightly newer T-Head TH1520 SoC, which is also 4-core, but uses faster C910 cores than the JH7110.

Raspberry Pi is looking into an IPO (Initial Public Offering).

But wait, Raspberry Pi's a non-profit! They can't do that? And who would want stock in Raspberry Pi anyway? Their core market hates them—they abandoned hobbyists and makers years ago!

And there are like tons of clones and competitors, nobody even needs Raspberry Pi? Plus, aren't they crazy-expensive? It's like a hundred bucks now, and that's if you can even find one to buy!

Well, hold on a second... there are a lotta misconceptions out there. In this post, I'll walk through what's actually happening, and also through things I see online.

This blog post is a lightly-edited transcript of a video on my YouTube channel, which you can watch below:

I'm in the unique position of owning a collection of Raspberry Pi Compute Modules 4 (CM4).

I also own at least one of every production CM4 clone in existence.

This sets up a quandary: if I have the real thing, what motivation do I have to care about the clones?

There are hundreds of CM4 carrier boards that do everything from restoring retro game consoles to monitoring remote oil rigs in highly-explosive environments.

Since launch, the CM4 has been difficult—and since early 2021, impossible—to acquire. The supply constraints are well documented, and I'm sure a few comments will lament the situation. But the CM4 is trickling back to 'in stock' at many suppliers (about how the Pi 4 was a couple months ago).