Single-board computer (SBC)
A complete general-purpose computer on one board, running a general-purpose operating system: Linux, sometimes Windows. The upper end of the embedded-systems spectrum, where you get a filesystem, a package manager, and everything else that assumes gigabytes and mains-adjacent power.
The category and its shape
awesome-iot's hardware section is thick with them — Raspberry Pi, BeagleBoard, ODROID, OLinuXino, HummingBoard, Dragonboard, UDOO — and nearly all are ARM. The Raspberry Pi set the template (credit-card footprint, GPIO header, cheap, Linux) and the rest are variations: industrial temperature ranges, different SoC vendors, Arduino coprocessors bolted on.
UP WCL is the other move: x86 in the same form factor. It costs watts (~30–36 W against a Pi's handful) and buys binary compatibility with software an industrial customer already runs — which is the whole argument for putting an Intel part in a maker-sized board.
The NPU line
Edge AI has become a standard spec row rather than a differentiator. UP WCL lists 15–17 TOPS of
NPU beside 9–21 TOPS of GPU compute in a 30 W envelope. Treat those numbers carefully: TOPS is
peak arithmetic throughput, not achieved performance on any model, and nothing in a spec sheet says
what memory bandwidth or quantization it assumed. What actually happens when a model is served on
such a board is ../llm-inference-wiki's subject; the board is this one's.
Where the line with an MCU sits
Not size — both are credit-card-ish — but software and power. An SBC boots an OS; an MCU runs firmware. That difference is worth three orders of magnitude of power consumption and decides whether a device can run on batteries for a year or needs a wall socket. Boards like UDOO that put both on one PCB exist precisely because the two ends do different jobs.
Paired with an MCU, the split is legible
Added 2026-08-15. wifisense-pi uses both ends of the spectrum in one build and the reason for each is plain. The ESP32-S3 captures the radio channel at 100 Hz — a fixed-rate job with a deadline, no filesystem wanted. The Raspberry Pi 4 does everything downstream: NumPy and SciPy filtering, a SQLite archive, a FastAPI server with WebSockets, and a browser dashboard. It costs about 20% of one core, and a 2 GB board is enough.
That is the MCU↔SBC line drawn by what the software needs rather than by size or price. Every task on the Pi's side of it wants a package manager and a scientific Python stack; nothing on the ESP32's side does. The same board also runs the whole thing from a container image or a systemd unit, which is the other half of "boots an OS" — a device you administer like a small server.
Related
embedded-systems · microcontroller · up-wcl-wildcat-lake-sbc · awesome-iot · wifisense-pi · wifi-sensing · synthesis