
你目前是否正在为一款常见的单板计算机(SBC)设计项目,并希望其他人也会来搭建你的项目?我们通常会刊登这类项目。不过事实证明,如今 SBC 的供货已经成了一个问题——我想教你如何选择 SBC 替代方案,主要是用来替代 Raspberry Pi 板卡。
我们以前也经历过 SBC 短缺,但 2026 年把之前的情况都比下去了,而且看起来哪怕再过几个月也不会停止。内存价格飙升彻底烧穿了单板计算机供货的供给侧,我还怀疑民用 SBC 被用于俄罗斯无人机也产生了明显影响。
不那么常见的 SBC 也总会带来自身优势。如果你不满意 Pi Zero 只配 512MB 内存,你总可以买一块 Orange Pi 或 Radxa 板卡,花更少的钱得到 2GB 或 4GB。现在更有动力去探索市面方案了!
今年,SBC 的价格和供货都大幅上涨,甚至连 Zero 2W 的库存也蒸发了。就我个人而言,我不得不更快地让一些项目变得更具灵活性。现在,我有一些经验可以分享!
我正在设计与测试一个掌上型项目,目标是支持大量不同的 SBC。第一分支旨在支持 Pi Zero 兼容板,但我很快也会分叉出一个 Compute Module 兼容版本。总的来说,看起来我即将发布的 Zero 兼容产品最多可以兼容多达十款不同的 SBC,我想分享我是怎么做到的。
无论你是在找类似 Compute Module 的方案、Pi Zero 形态的设备,还是只是一块带 GPIO 排针并且有一定 CPU 性能的大板子。你可能会觉得去翻一翻某些“SBC list 2026”是个好主意,这方面你当然有一半是对的。去看那些列表吧,一眼看过去大概就有五份不错的。不过我为你准备的是另一种列表。
前往 Armbian 和 DietPi 的下载页面,那里列出了受支持的板卡,然后浏览图片。这或许是最好的板卡软件支持指标,而软件支持又会决定这块板子对你来说有多可行。你也可以进一步查看评测,但一般来说,只要 Armbian 或 DietPi 支持你的板子,就不存在根本性的使用障碍。
顺便说一下,如果你看的是某款热门 SBC,你往往会发现它有更便宜的替代方案!例如 Banana Pi 板卡最近似乎贵得离谱——Banana Pi M4(H618 SoC)售价高达让人咋舌的 100EUR 以上,而 CPU 与内存配置相当的 Orange Pi Zero 2W 只要 50EUR 甚至更低就能买到。
大多数人需要 WiFi,有时需要以太网,肯定要 USB,多数要 HDMI,可能需要一些 I2C,也可能需要 SPI 或 UART。在绝大多数 SBC 上你基本都能得到这些接口。如果你想要不局限于这些,有时就得更费力地去找。下面是接口情况的概括。
Raspberry Pi 的 40-pin 排针引脚定义已经成为 SBC 领域不成文的标准。你基本可以保证在物理引脚 2/3 以及 27/28 上有 I2C,在引脚 8/10 上有 UART,在引脚 19/21/23/24 上有 SPI。多数板子在引脚 26 上有 CS1,如果没有的话,你也可以用 DeviceTree overlay 把它设置为软件 CS 引脚。
如果你只需要 GPIO,那你确实很幸运。Linux 在将 GPIO 代码统一到同一框架下做了大量工作,新的 libgpiod 接口尤其有帮助。Raspberry Pi 板卡有一点特殊,因为它在各代之间使用“干净”且不可更改的 GPIO 编号,但大多数地方你都能搞清楚编号方式。
真正搞砸这一点的板子很少——我只知道 Radxa Zero v1.5 这一款,由于 Amlogic S905Y2 的 GPIO 严重短缺,它的 GPIO 排针上直接出现 NC 和重复引脚。不过它也是唯一的具备充足且便宜的 4GB 选项的板子。有得必有失。
我还发现,相当多的板子也会把 I2S 引脚放在 Pi 的 I2S 引脚位置上,乍一看似乎不一致。不过,你可能只需要很少的跳线就能让你的 I2S HAT 重新工作。你不能指望在同一些引脚上还有 PWM,但非 Pi 的 SoC 通常会有充足的 PWM 可用。
你确实会失去一些定制能力。别指望用同样的引脚定义直接从 GPIO 排针驱动并行 RGB 显示屏——那是 RPi 那一套。不过很多 SoC 也确实会暴露一个并行 RGB 接口。同样也别指望不先确认就直接从 GPIO 驱动 WS2812 LED。GPS PPS 支持通常存在,但往往需要一些驱动层面的折腾。
你想确保你能从某块 SBC 获得特定接口?可用的软件也会帮到你。检查该 CPU 的基础 DeviceTree 文件是否提到了那个接口,运气好的话,Armbian 仓库里甚至会有一个用于启用该接口的 DeviceTree overlay——如果没有,也很好修。顺便说明,由于很多 SBC 使用市面上常见的 SoC,有时你未必能找到在你具体板子上测试过的 overlay,但来自不同板子、相同 SoC 的 overlay 通常也能正常工作。
当然,并非一切都围绕底层接口。除了最弱的芯片,你基本可以保证有 HDMI,而非千兆以太网则很少见。至于 USB,通常是 USB2,但 USB3 也越来越常见。PCIe 依然少见,但随着 Raspberry Pi 确立了在 FFC 连接器上使用 PCIe 的标准,你会看到更多这类设计,也会看到更多测试。别指望到处都能从 NVMe SSD 实现完美无瑕的 PCIe 启动,但许多 PCIe 设备常常能正常工作——从 NVMe 存储、WiFi 卡,到额外的网卡和其他冷门的 PCIe 小玩意儿。
注意!板载 WiFi 芯片可能会比较麻烦,尤其是通过 SDIO 连接的那些。当然,用 USB-WiFi dongle 也能绕过。摄像头接口也可能时好时坏。有些厂商如 Radxa 会提供经过测试、兼容其板子的 CSI 摄像头模块,而另一些则给你一个 CSI 排针并指望你自己去搞定。DSI 接口也往往类似——不过如果你愿意动手,就能以低位分辨率的价格和低功耗换来一块高分辨率屏幕。
就物理兼容性而言,你能找到的共通点可能比你想的更多。在 2020 年代初 Compute Module 供货紧张时,中国厂商看到了实现兼容所需的东西其实很少,于是推出了一大批大部分兼容的 Compute Module 替代板,用于各种常见接口就足够的应用。直到今天,如果你需要 Compute Module 兼容但不在乎 RPi 的定制接口,你相对容易就能找到一块,插到原本为 Pi CM4 或 CM5 设计的板子上时,基础功能通常也能工作。一些定制连接器会不同,但这些连接器只承载那些无法纳入 CM4/CM5 引脚定义的额外接口。
不过 Compute Module 兼容板有一个很大的问题——由于它们毫无疑问偏 prosumer 定位,最近的价格跳涨远高于偏消费级的板子,如今已经徘徊在 200EUR 左右,而且库存也更低。部分原因在于 Compute Module 兼容板通常不像其他 SBC 那样在内存容量上“抠门”;我还怀疑俄罗斯无人机厂商似乎收购了大量旧的闲置库存用于无人机也无助于缓解——因为我总能在无人机拆解里看到一堆 SBC 模块。
那 DeviceTree snippets 呢?只要你的设备能运行主线(mainline)或主线邻近的软件,这也不成问题。对我自己的“一次适配多块板子”项目,我写了一个小模板脚本,为不同平台生成不同引脚编号的 DeviceTree snippets。我也在为 Hackaday 写一套 DeviceTree 教程系列,可能已经发布也可能很快发布——敬请关注!
SBC 短缺确实很糟,但它拦不住你,而且在你探索时甚至能找到性能更强的 SBC。我们可能不再有 luxury 只针对一款特定 SBC 进行设计,但在市场上为其他板子预留空间并非不可能。即使不是为了那些想运行我们项目的人,至少也为了我们自己——当我们试着真的去买那些我们为其设计了软件和硬件的板子时。
你把项目迁移到其他 SBC 上的经历如何?我很想在评论区听到更多,不管负面还是正面,各种都行——因为随着时间推移,这条路会越来越多人一起走。
本文来源:https://hackaday.com/2026/11/05/i-think-we-should-see-other-sbcs/
若有版权问题,请来信告知:13951431913#139.com 或在右方提交评论。
Are you currently designing a project for a common single-board computer (SBC), and do you expect other people to build your project, too? We routinely feature projects that do exactly this. Well, turns out SBC availability is a problem now – and I’d like to teach you how to pick SBC alternatives, mostly to the Raspberry Pi boards.
We had SBC shortages before, but 2026 has beat them all, and it doesn’t look like it’ll stop within even a few months. RAM prices have incinerated the supply side of single-board computer availability, and I suspect that consumer SBC use in Russian drones had a noticeable impact, too.
Less-utilized SBCs always brought their own advantages to the table. If you didn’t like that the Pi Zero came with only 512MB of RAM, you could always buy an Orange Pi or a Radxa board with 2GB or 4GB for a meager increase in price. Now, there’s even more of a motivation to explore what’s on offer!
This year, SBC prices and availability have both jumped up tremendously, and even the Zero 2W stocks have evaporated. Me, I had to make a few of my projects way more flexible way quicker. Now, I have some experience to share!
I’m in the middle of designing and testing a palmtop project aiming to support tons of different SBCs. The first branch of it aims to support Pi Zero-compatibles, but I’ll be forking it into a Compute Module-compatible version soon, too. All in all, it looks like I’ll be able to make my upcoming Zero-compatible release compatible with as many as ten different SBCs, and I want to share how I am getting there.
Whether you are looking for something Computer Module-esque, a Pi Zero-looking device, or just a big board with a GPIO header and some CPU oomph. You might think looking through some “SBC list 2026” is a great idea, and in part, you’re certainly right. Go read those, there’s like, five good lists at a glance. I do have a different kind of list for you, though.
Go to Armbian and DietPi download pages where supported boards are listed, and look through the pictures. This is perhaps the best indicator for a board’s software support, which in turn decides how viable a board is to you. You can further check for reviews too, but as a rule, if Armbian or DietPi support your board, there’s no fundamental roadblocks to using it.
By the way, if you’re looking at a specific popular SBC, you’ll often find that it has cheaper alternatives! For instance, Banana Pi boards seem incredibly overpriced as of late – the Banana Pi M4 (H618 SoC) goes for eyewatering 100EUR+, while the CPU-equivalent RAM-equivalent Orange Pi Zero 2W can be found for 50EUR or even less.
Most people need WiFi, sometimes Ethernet, certainly USB, mostly HDMI, maybe some I2C, maybe SPI or UART. You’ll certainly get all of these on the vast majority of SBCs. If you’re looking beyond these, you’ll sometimes have to look harder. Here’s a summary of the interface situation.
The Raspberry Pi 40-pin header pinout has become an unspoken standard in the SBC space. You’re basically guaranteed I2C on physical pins 2/3 as well as 27/28, UART on pins 8/10, and SPI on pins 19/21/23/24. Most boards have a CS1 on pin 26, and where they don’t, you can add it as a software CS pin with a DeviceTree overlay.
If you just need GPIOs, you’re certainly in luck. Linux has done tremendous work with unifying GPIO code under the same umbrella, and the new libgpiod interfaces help in particular. Raspberry Pi boards are a bit of an outlier with their “clean” and unchangeable GPIO numbering between generations, but you’ll figure out the numbering most anywhere.
There’s very few boards that screw this up – Radxa Zero v1.5 is the only one I know, having outright NC and duplicated pins on the GPIO header due to the Amlogic S905Y2 having a critical GPIO shortage. It’s the only board with an abundant and cheap 4GB option, though. You win some, you lose some.

I’ve found that a surprising amount of boards put I2S pins on the Pi I2S pins , too, though it seems inconsistent at a glance. However, it might be that you need very few jumpers to make your I2S HATs work again. You can’t expect to have PWM on the same pins, but non-Pi SoCs generally have plenty of PWM to spare.
You are definitely losing out on bespoke abilities. Don’t expect to be able to drive parallel RGB displays directly from the GPIO header with the same pinout – that’s an RPi thing. Many SoCs do expose a parallel RGB header, though! Don’t expect to drive WS2812 LEDs directly from GPIOs without checking that it’s possible, either. GPS PPS support tends to be present, but expect needing a bit of driver hackery.
Do you want to make sure you can get specific interfaces from an SBC? The available software will also help you there. Check whether the base DeviceTree file for the CPU mentions that interface, and if you’re lucky, there will even be a DeviceTree overlay for enabling that interface in Armbian repositories – if not, that’s easy to fix. By the way, since many SBCs use commonly available SoCs, it’ll sometimes be that you don’t find an overlay tested on your specific board, but an overlay from a different board with the same SoC should work perfectly fine.
Not everything revolves around the low-level interfaces, of course. You’re basically guaranteed HDMI on all but the weakest chips, and non-Gigabit Ethernet is a rarity. As for USB, expect USB2, but USB3 is more and more common, too. PCIe is still rare, but with the Raspberry Pi setting the standard for PCIe on FFC connectors, you will see more of it, with more testing. Don’t expect flawless PCIe boot from an NVMe SSD everywhere, but many PCIe devices will often work just fine, from NVMe storage and WiFi cards to extra Ethernet cards and other obscure PCIe doohickeys.
Beware! The onboard WiFi chips can be screwy, especially the SDIO-connected ones. It’s nothing that can’t be worked around with a USB-WiFi dongle, of course. The camera interfaces can be a hit and miss, too. Some designers like Radxa offer tested CSI camera modules compatible with their boards, while others give you a CSI header and expect you to figure it out. This is also how DSI interfaces tend to go – but if you roll up your sleeves, you can get yourself a high-res screen for a low-res price and low power consumption.
As far as even physical compatibility goes, you’ll find more common ground than you would suspect. When Compute Modules were in short supply in the beginning of the 2020s, Chinese manufacturers saw how little was needed for compatibility, and whipped up a flurry of mostly compatible Compute Module replacement boards, to be used in all sorts of applications where the common kinds of interfaces suffice. To this day, if you need a Compute Module compatible without the RPi’s bespoke interfaces, you can find one relatively easily, and all the basics will often work when plugged into a Pi CM4 or CM5-intended board. Some bespoke connectors will differ, but those connectors only carry extra interfaces that couldn’t fit into the CM4/CM5 pinouts.
There is one major problem with Compute Module compatibles specifically, though – since they are unquestionably prosumer, their recent jump in price is way higher than for the consumer-friendly boards, now hovering around the 200EUR mark, and their stocks are lower, too. Some of it has to be that Compute Module compatibles don’t skimp on RAM size in the way that other kinds of SBCs often do, and I suspect it didn’t help that Russian drone makers seem to have bought up a whole bunch of old unused stock for use in drones, either, as I keep seeing a bunch of SBC modules in drone teardowns.
What about DeviceTree snippets? As long as your device can run mainline or mainline-adjacent software, that won’t be any sort of problem either. For my own “many boards at once” project, I’ve written a small template script generating DeviceTree snippets with different pin numbers for different platforms. I’m also writing a DeviceTree tutorial series for Hackaday, that’s either released already or soon to be released – stay tuned!
The SBC shortages are genuinely bad, but they can’t stop you, and you can even find more powerful SBCs around as you explore. We might not have the luxury to design for just one specific SBC anymore, but there’s nothing impossible about accounting for other ones on the market. If not for the sake of people wanting to run our projects, then certainly for our own sake as we try to actually buy boards we designed our software and hardware for.
What have been your experiences moving your projects to other SBCs? I’d love to hear more in the comments, negative, positive, all kinds, as this is going to be a journey more and more of us take up with time.