Also known as: Raspberry Pi Compute Module, CM4
Reader-supported. GopherTrunk is free, open-source software. Some
hardware links on this page go to Amazon with our Associates tag
(gophertrunk-20); if you buy through them we may earn a small
commission at no extra cost to you. It never changes which gear we recommend, and
the software stays free either way. How GopherTrunk is funded →
A Compute Module is a single-board computer stripped down to a small module — the processor, memory, and storage — without the usual ports, meant to plug into a custom carrier board.1
Key takeaways A module — it needs a carrier board. The Raspberry Pi Compute Module (CM4/CM5, ~$55) is the same silicon as a full Pi but with no ports of its own: it plugs into a carrier board that provides USB, Ethernet, and power. It runs the same pure-Go ARM64 GopherTrunk binary, but it’s aimed at custom, embedded capture nodes built at volume, not everyday setups. For a normal build, a full Raspberry Pi is far simpler and the default recommendation. No SBC decodes AES encryption. Compare on best SBC for GopherTrunk.
Overview
The best-known example is the Raspberry Pi Compute Module (CM4, CM5), but the idea is general: take the system on a chip and memory of a board like the Raspberry Pi and put it on a compact module that breaks all of its signals out to an edge connector. A product designer then lays out a carrier board that routes the GPIO, USB, Ethernet, and power exactly as the product needs, rather than working around a fixed consumer layout.
This separation lets one well-supported compute module serve many different products. The same module drops into a digital-signage player, an industrial gateway, or a camera, and each carrier exposes only the connectors that product uses. It also decouples the two design cadences: the module vendor handles the tricky high-speed SoC-to-memory routing, while your team designs the comparatively simple carrier.
Module vs stock board
| Stock SBC | Compute Module | |
|---|---|---|
| Ports | Fixed, on the board | You choose, on the carrier |
| Shape / size | Fixed | Whatever the product needs |
| Effort to deploy | Plug in and go | Design + build a carrier |
| Best for | Prototypes, hobby, general use | Volume embedded products |
| Extending | HAT on the header | Integrated into the carrier |
Where it fits
A Compute Module is the choice when an embedded system needs the brains of an SBC but its own enclosure, connectors, and shape — a step beyond bolting a HAT onto a stock board. In a GopherTrunk-style product, a Compute Module on a custom carrier could host the SDR front end, timing, and storage in a sealed, antenna-mounted capture node with only the connectors it actually uses. The trade-off is engineering effort: you design, lay out, and manufacture the carrier yourself, which only pays off past a certain volume.
Running GopherTrunk on a Compute Module
A Compute Module is the same silicon as the matching Raspberry Pi, so its GopherTrunk abilities equal that Pi’s — with the crucial caveat that the module has no ports of its own and depends on a carrier board to expose them:
- Architecture — the CM4 and CM5 are ARM64 (aarch64), running the same static
linux/arm64GopherTrunk binary from the downloads page as a full Pi — no vendor toolchain. - CPU — a CM4 carries the Pi 4’s quad Cortex-A72 (1.5 GHz); a CM5 carries the Pi 5’s quad Cortex-A76 (2.4 GHz). Real-time DSP capacity is identical to those boards: a couple of channels on the CM4, comfortable multi-channel work on the CM5.
- RAM — the same options as the matching Pi (up to 8 GB on the CM4, up to 16 GB on the CM5), enough for recording, the web console, and several systems.
- USB — the module breaks USB out to the carrier, so the number and speed (USB 2.0 vs 3.0) of ports for your SDR dongle(s) is whatever the carrier board provides — check that it offers USB 3.0 if you plan on wideband Airspy capture or several dongles.
- Storage — most modules include onboard eMMC (a “Lite” variant uses microSD on the carrier), and the carrier can route PCIe to an NVMe drive for continuous IQ recording and the call database.
- Power / thermals — draw matches the equivalent Pi; a CM5-class module under sustained load wants a heatsink, and cooling is designed into the carrier/enclosure since the module has none.
- OS / networking — runs Raspberry Pi OS (64-bit), the most turnkey Linux for GopherTrunk; Ethernet and Wi-Fi come from the carrier, so a well-chosen carrier gives you the same headless web console access as a stock Pi.
Bottom line: a Compute Module runs exactly the workload of the Pi it’s based on — a couple of SDRs with recording (CM4) up through comfortable multi-channel work (CM5) — once it’s on a carrier board that supplies the USB, storage, and networking it needs.
Where to buy
A Compute Module makes sense only for a custom, embedded GopherTrunk build — remember it’s a module and needs a carrier board to expose USB, Ethernet, and power before you can plug in an SDR. For a normal setup, a full Raspberry Pi is cheaper, needs no carrier, and is the default recommendation — see best single-board computer for GopherTrunk.
As an Amazon Associate, GopherTrunk earns from qualifying purchases — at no extra cost to you. It never changes what we recommend.
Sources
-
Raspberry Pi Compute Module — Wikipedia, on the modular, carrier-board form of the Raspberry Pi. ↩
Frequently asked questions
Can I run GopherTrunk on a Compute Module?
Yes — a CM4/CM5 runs the same Raspberry Pi OS and the same pure-Go ARM64 GopherTrunk binary as a full Pi. The catch is that a Compute Module is just the module: it needs a carrier board to expose USB, Ethernet, and power before you can plug in an SDR. For most builds, a standard Raspberry Pi is far simpler and the default recommendation.
Do I need a carrier board?
Yes. A Compute Module has no ports of its own — it mates through an edge connector into a carrier board that provides USB, Ethernet, GPIO, and power. You either buy an off-the-shelf carrier or design your own, which is the whole reason to choose a module over a stock board.
When is a Compute Module the right choice for GopherTrunk?
Only when you’re building a custom, embedded capture node — a sealed, antenna-mounted product with exactly the connectors it needs — and the engineering effort pays off at volume. For a normal home or hobby setup, a full Raspberry Pi is cheaper and much less work.
Does it decode anything a full Pi can't?
No. A CM4/CM5 is the same silicon as the matching Pi, so it decodes exactly the same signals — and no SBC changes the encryption wall: GopherTrunk cannot decode AES-protected traffic on any host.