I Think We Should See Other SBCs

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!

Finding Your New SBC Friends

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.

Settling On Interfaces

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.

Lose Some, Win Some, Keep Most

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.

Compute Copycats

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!

Your Project Will Go On

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.

76 thoughts on “I Think We Should See Other SBCs”

  1. The problem with this article is that it doesn’t touch the reason why people still prefers to use Raspberry Pi SBCs over the other ones: software/OS support. There is no match to Raspberry Pi on that aspect.

    1. Bingo, every other board i’ve tried has has tons of weird driver issues or complete lack of support past the initial release. (I’m looking at you OrangePi)

      1. That’s why the one and only suggestion in this article is to look at armbian/dietpi, the projects providing good, ongoing software support and to choose from among the boards they feature.

        It’s like you didn’t read anything and jumped straight down to the comments.

        1. Even with Armbian, you rarely get proper support for e.g. CSI-interface or hardware encoding/decoding or such. I have used Armbian a lot of in the past but I just eventually gave up on even trying to use anything other than Raspberry because of the constant stream of issues.

          And now, with the constant price hikes, I’ve given up on Raspberries as well.

    2. Building your own OS image is not as bad as it sounds, assuming that the mainline kernel kinda supports the chip and the board.

      Of course, it is not as easy as flashing a Pi, but I guess it can be worth the trouble, in this economy – especially if you are doing it for more than one units?

      1. (by the way, what I really believe is that the bootloader – such as UEFI – should be handling this, like in case of the IBM PC compatibles. Some recent ARM SBCs do that – and can run generic Debian ARM images – but most boards still can’t..)

        1. Welcome to ARM.
          I’ve had to deal with device trees in my futile efforts to port Linux to some Android phones I owned, and I didn’t like it that much.

    3. The article clearly addresses the software problem.

      You should never use whatever software comes by default from most SBC manufacturers, and instead use reputable distros like Armbian and DietPi.

      They provide long-term support and work just as well as the Raspberry Pi software ecosystem.

    4. You could build Gentoo on ARM64. That would only take a few months… (actually you’d have to build each update on another computer to speed up the process significantly, which would still be annoying)

    5. I do touch upon the software ecosystem part, but only in passing, mentioning things like improved compatibility and distros. This is because 1) things have improved dramatically since the early days of alternative SBCs, 2) just use Armbian or DietPi and the overwhelming majority of your possible problems will be solved, 3) it’s been discussed to death already, and 4) we don’t really have a choice in that regard nowadays. I work with other SBCs aplenty now, and while I am an advanced users, I encounter very few problems.

    6. It literally does…

      Paragraph 7 starts:
      “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.”

      Boards supported by these projects are >95% as well supported as a Pi one is.

      There MIGHT be some weird edge case with a wonky peripheral that doesn’t work right. But that could also be a hardware bug.

      I have never, not one single time, had a support issue that wasn’t solvable when using Armbian or DietPi, that would have been solvable with Pi’s premium support.

      If someone is deep enough in the weeds to be bringing up hardware accelerated video drivers, or working with an oddball peripheral, then it’s not going to just be LEGO on a Pi either.

      Is that extra support and a warm feeling worth a $100%-$150% markup?
      No.

    1. Rather doubt any of us would want to pay the asking price for such an SBC right now…
      Are you thinking with the usually integral modem etc or without as a bare bones of just the computing elements but with the smartphone design philosophy?

      1. Oh Dear, how I hate the nvidia ecosystem…. They do not support okder devices, just what is currently released. I’m forced to use jetson nano and nvidia agx. They genuinely suck.

        The best move was to migrate over to bananapi m7.

        Gee, I do hate nvidia.

    2. If you are willing to pay several hundred bucks on the module/SBC, I guess there is some Qualcomm / Mediatek module/boards are available and I guess they were at least able to boot Linux kernel.

      I don’t know about display/GPU support because my project did not need that.

    3. hehe it seems like all 3 replies interpretted this as a request for more compute?? when i am just envisioning a CPU that has genuine power save modes, which every cellphone has had for 15+ years.

      1. Not at all, in my case that was largely what I meant by design philosophy once you strip out the usually integral to the silicon radio stuff. With a little bit of the balance between general, graphical compute and specific task accelerators in the silicon usually coupled with comparatively modest RAM compared to the compute potential (on paper anyway). As your computer is likely to have vastly more RAM even when its processor is more smartphone performance level (Which makes sense to me as the way folks use a more real computer does tend to demand more RAM).

        Though I was half expecting you despite you well documented love of power management to be all about the built in radio stuff, as that is rather the core of a smartphone more than power management.

  2. The software support for the Raspberry Pi line is a major factor, but for my personal projects I find that even before the RAM shortage it was hard to find SBCs that met my needs because they all had to little RAM. When the Pi5 8GB variant came out it was the first one that I felt was workable beyond being a toy (since MCUs these days are many orders of magnitude more powerful than my first computer or even my desktop 30 years ago, most projects I go for are fine using an MCU and if they require a real Linux computer I generally want a minimum of 8GB and ideally as much as 64GB of RAM and not many of today’s SBCs populate that much RAM — what I really want is an SBC that accepts one or two SODIMMs).

    There are lots of applications where you don’t need a hell of a lot of compute but the lower latency of having your data in DRAM rather than flash is key.

    1. this is why the one and only suggestion in this article is to look at what armbian/dietpi support.

      there’s your software support.

    2. Really can’t see how you’d ever find the 4 gig Pi’s limited in most sane uses for the processor class – I had an 8 gig Pi 4 running multiple VM’s and doing those light CAD knock up a bracket to suit the moment sort of problems, running a browser media player etc all at once and while the RAM would get very very full with anything even approaching a fast storage drive more likely waiting on the relatively limited processing capabilities still!

      Linux by its nature doesn’t actually need RAM to hog so for the sort of real linux computer loads a Pi is well suited for even the 1gb models are I’d suggest more often than not going to perform pretty comparbly.. You have to be doing really quite weird stuff or working off an insanely slow storage disk to really feel the performance penalties related to that rather than just having by modern standards slow compute.

  3. Those who want something decent usually buy odroid from hardkernel. RPi SBCs are overpriced and underwhelming compared to the alternatives.

  4. Most of those projects people buy SBCs for could’ve been and should’ve been done on something like PIC16F. I wish government enacted some kind of law that made it mandatory to register computers so that if it’s unused for something like a year it would be returned to common pool for people to take and use in their projects.

    1. Most people who are using SBCs for this type of thing are newbies and using a PIC or something similar is significantly more difficult for them.

      That law sound like the most dystopian idea ever.

    2. So close to the end of the year. I’ll add your comment to the pool along with the they don’t need the ram they paid for and other such enlightened statements for the contest at the end of the year.

    3. PIC16F is one of the worst microcontrollers I’ve ever had the displeasure of programming. Every PIC microcontroller should be thrown into a landfill and erased from history. So much errata and broken features. The toolchain is a joke, and the ecosystem is fractured by too many compilers. If you want to learn how to do something, every web search turns up a thousand ways to do it using any compiler but the one you’re using.

      With that out of the way, I’m all for democratic socialism, but what you’re suggesting is much more like if fascism had a lovechild with communism. Registering anything with the government is an open invitation for people armed with guns to show up on your doorstep demanding to take your private property from you. You think that 1 year will be written in stone? Oh, that’s just the first revision of your little law. Soon it gets pulled down to 6 months, then 1 month, then why bother letting anyone purchase a computer anyway? No one keeps them for more than a month at a time, you should just rent them. Oh, then you also have to pay to return them. Wait, that’s too much burden on the corporation. You have to pay to recycle them, and you have to pay the corporation to file the paperwork. Oh, don’t forget the taxes you owe for all the administration the government has to perform.

      Did you forget this is a hacking site? We build computers. Should I have to register something I build myself and etch by hand? Do I have to register every stick of RAM? What if I built those sticks myself from salvaged chips?

      I think the government should be there to help people who need it as their main priority, keep up public infrastructure as their second, then they should stop people from hurting others, aaaaaaand that’s pretty much it.

      Got me going on two fronts today.

    4. anyone who has bought auto components lately has been scammed by other customers who returned their faulty part in the new box. your proposal would require that everyone deal with the same problem.
      There are ways that governments could reduce scarcity, such as requiring collaboration on a small number of architectures, but yours is not one of them.

    5. You’re greatly misunderstanding why people build projects with SBCs. Making your projects fit as small of a footprint as possible is neither desirable nor pleasant for most people. Unless fitting the smallest footprint possible is your definition of fun, it’s something you only do when you’re paid to do it.

      1. eh? even on hackaday a lot of the projects are all about fitting it into an arbitrarily small package, whether you’re measuring size by RAM, number of components, battery draw, or physical volume. size constraints are very common in my few embedded projects. if i didn’t have a size constraint i’d probably use a stale laptop with a pico acting as a USB I/O expander, there would be no need for ’embedded’ except as a bitbang-capable I/O.

        1. We mostly cover things that are outstanding, unique, and haven’t been covered already. We are NOT a representative sample of what people do with single-board computers. Incredibly far from it, even. Most people put some sort of service on their Pi that in all likelihood has nothing to do with GPIOs, and if it does, it could likely be ported to other boards by the devs with very little effort. Additionally – please recognize how incredibly off-base the comment I’m replying to is, and interpret my response in that context, instead of taking it out of context.

      1. This looks pretty sweet, it has gpio, i2c, uart, etc. A little old but still available.

        What features do you guys need added to a phone? Is there actually a gap in the market here? Besides the “phone with gpio built in” gap lol

    1. That’s true, but typically there are no i2c/spi ports available for hacking (the on-board SMBUS doesn’t count!), nor gpios for bit-banging something. And even if you’re lucky and find some pins, you’d better put some ESD protection there, because… :D

      Maybe if there’s a VGA port (if the laptop is old enough?), one could use the DDC as ghetto-I2C?

      Years ago I’ve used for such purpose an USB FTDI board. I2C & SPI transfers were ok-ish, pin manipulations were much slower than direct pin access (due to USB frames timing), but sometimes it’s acceptable.

      1. HDMI ports have I2C DDC pins too. You can also an M.2 slot. An E key slot that’s normally used for WiFi has I2C, UART & SDIO pins, although they aren’t always connected. A much more advanced option would be to make a custom M.2 card with an FPGA on it that connects over PCIe.

      2. raspberry pico on a usb port is the ultimate io expander imo. i don’t think it’s a big problem to get good flexible i/o on an old laptop. latency is good if you can do the low-latency parts on the pico itself, which is usually how i’d want to do it anyways.

      3. The onboard SMBUS absolutely counts, you can do great things with it! Also, HDMI ports carry 5V I2C, too. However, just get a RP2040 board and plug it into a free USB port if you need GPIOs.

        1. I second RP2040 on a spare USB port.

          I also had okaish (speed-wise) results with humble Arduino Nanos and Megas on the USB port. For most IOs that do on/off and maybe 8-bit ladder logic they are quite good enough, and adding solid state relays does the heavy lifting.

          Unrelated, but had pretty good results with a humble standalone NanoPi Neo 2 running off a single 18650 with a headless DietPi OS. While couldn’t compete with, say, Beagle Board, it was budget-priced and in stock, even during Covid.

    2. That isn’t really a full SBC experience, both lacking many features common in SBC but almost unheard of on production computers and for the complete impossibility of replication/replacement of the brains of your project (and while available PCIe lanes are getting better as modern devices often have M.2 slots plural which can solve much of that).

      But if the busted laptop does what you need it is certainly a good option, for many folks the busted computer and a pi pico/arduino type thing connected via USB is going to be good enough. I’d suggest looking at gaming handhelds now though – if you don’t intend to use the laptop keyboard etc the form factors of the PCB and cooling in all the ones I’ve seen teardowns of suggests more useful, and generally more performance in the same volume.

  5. I have 5 RPi’s laying around gathering dust! .
    2 1’s, a 2B, a 3B and a 4B, although I have to physically find that one first. It is on my network, it serves no function anymore but I forgot where it actually is.
    I have 2 5B’s, one of which is a NAS and the other a KODI media player.
    Should I sell the other ones?

      1. man i haven’t quite misplaced a powered-on computer yet but if you saw my workbench i think you would understand how it’s possible :). it’s quite shameful, but basically there’s a spot where i take things apart and put them back together and if something doesn’t go back together then it just gets buried. and when the pile gets too deep i displace it horizontally 2ft and carry on. it’s very bad and i blame my kids (no project is allocated enough time for successful completion and housekeeping is the biggest place for cutting corners)

  6. One of the big reasons the RPi is popular is it’s easy to get by anyone. It’s not the cheapest but anyone anywhere can get it. A lot of the others are limited in distribution so it may be better and cheaper but only if you’re in the US. If you’re anywhere else (say Canada) it can be double or triple the price because shipping and taxes and such. It might even be easier for people to port it to a readily available RPi than buy the harder to get SBC.

      1. Yep Im running i5, i7, i9 SBCs. Dont get me wrong those baby boards are great, theyre ideal for the sort of applications most HaD readers are working on.

  7. The RAM problems are going to hit everyone, so ALL the other SBC makers will increase price in the near future. Some will even stop trading as they will be unable to buy RAM at all. This is not actually a supply problem, there is RAM out there, but it all gone up in price by an order of magnitude. Pi as a large company can afford to buy parts, many smaller companies will not. Looking at their trading numbers, they are still selling a lot of devices.

  8. Thanks for this very good article !

    drone teardowns
    I was expecting a link here, as I’d be curious to see what make a makeshift drone tick nowadays

    I’m also writing a DeviceTree tutorial series for Hackaday, that’s either released already or soon to be released

    Can’t wait to read it!

  9. Anyone worked with Armbian on the Arduino UNO Q SBC? How much of the integrated ML on the MPU and microcontroller integration works? Can you run Arduino App Lab on that OS? If anyone has any projects links that would be awesome, there are lots of namespace collision when searching for information about that board.

  10. All the RAM capacity for 2027 has been presold already. So it will be at least until the AI bubble bursts or 2028 before before we see RAM prices decline.

    And if the bubble does not burst in 2027, ..

Leave a Reply

Please be kind and respectful to help make the comments section excellent. (Comment Policy)

This site uses Akismet to reduce spam. Learn how your comment data is processed.