Field Guide · hardware

Also known as: Radxa, Rock 5

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 →

Radxa is a Chinese maker of Rockchip-based single-board computers — its Rock 5 series (RK3588) is the fastest SBC class covered here, and often offers faster I/O than a similarly priced Raspberry Pi.1 Radxa’s boards are also documented on this site under the Rock Pi name, the line’s original branding.

Radxa RK3588 Rasp. Pi Pi 4 PCIe lane — wide, fast microSD — narrow, slow NVMe SSD microSD card
Radxa's edge is I/O: an NVMe SSD on a PCIe lane moves data far faster than the microSD card a stock Pi of the same price relies on.

Check price on Amazon →

Key takeaways The fastest board here — enthusiast multi-SDR host. The Radxa Rock 5B (RK3588, ~$150) brings PCIe/NVMe storage and 8 fast cores, ideal for a GopherTrunk node that runs a multi-SDR pool and records raw IQ or keeps a big call archive — NVMe sustains writes a Pi’s microSD can’t. GopherTrunk runs on it as a pure-Go ARM64 binary; Radxa’s images are decent but trail Raspberry Pi OS. For a simple single-system build, a Raspberry Pi is cheaper and the default pick. No SBC decodes AES encryption. See best SBC for GopherTrunk.

Overview

Radxa builds its computers around Rockchip SoCs — the powerful RK3588 drives the higher-end Rock 5 boards — and frequently adds features the Pi lacks at the same price: an NVMe slot, faster Ethernet, or more RAM. The NVMe slot is the headline: instead of running the whole system off a microSD card, a Rock 5 can boot and store data on a proper solid-state drive over PCIe, which transforms any workload that reads or writes a lot of data — exactly what a capture-and-archive GopherTrunk node does.

Boards run Linux or Android and keep a Pi-style GPIO header, so much of the Pi accessory ecosystem carries over mechanically. As with most Pi alternatives, software polish trails the Raspberry Pi — vendor images and community depth are not quite at Pi levels — but Radxa’s are generally among the better-supported of the alternatives.

The Rock 5 lineup

Board SoC Rough role Notable
Rock 5B / 5B+ RK3588 (8-core) Flagship PCIe 3.0 NVMe, up to 16–32 GB RAM, 8K, 2.5 GbE
Rock 5C RK3588S2 (8-core) Value flagship Compact, PCIe, HDMI 8K
Rock 3 / 4 series RK3566 / RK3399 Mid-range Cheaper, still Pi-class or better

The Rock 5B is the one to reach for as a GopherTrunk host: its RK3588 has the most real-time DSP headroom of any board here, and its PCIe/NVMe storage is the reason to pick it over a Pi.

Running GopherTrunk on a Rock 5B

  • Architecture — the RK3588 is ARM64 (aarch64), so the standard static linux/arm64 GopherTrunk binary from the downloads page runs directly, no vendor toolchain required.
  • CPU — the full 8-core RK3588 (4× Cortex-A76 up to 2.4 GHz + 4× Cortex-A55) has the most headroom here: comfortably a wideband, multi-SDR pool with many demodulators running at once, not just a single channel.
  • RAM — 4 GB up to 16/32 GB, ample for large recording buffers, the web console, and following many systems concurrently.
  • USB — multiple USB 3.0 ports (plus USB-C) carry several SDR dongles with bandwidth to spare for wideband Airspy capture; a powered hub keeps a bank of dongles stable.
  • Storage — the headline: an M.2 NVMe slot on PCIe means continuous IQ recording and a growing call database run on a proper SSD, sustaining write throughput a microSD card can’t and won’t wear out under constant writes.
  • Power / thermals — the RK3588 runs hot under sustained decode load, so a heatsink and fan are essential for a 24/7 node; power draw stays modest for the performance.
  • OS / networking — any 64-bit Linux with an RK3588 image (Armbian, Radxa’s Debian/Ubuntu, DietPi); support is good but trails Raspberry Pi OS. 2.5 GbE (and gigabit) plus optional Wi-Fi let a headless node move recorded IQ and serve the web console without bottlenecking.

Bottom line: a Rock 5B comfortably runs a wideband, multi-site SDR pool with fast NVMe recording — the enthusiast build when both decode count and storage throughput matter.

Where to buy

The Radxa Rock 5B is the enthusiast pick — the fastest board here, with PCIe/NVMe for a multi-SDR GopherTrunk node that records raw IQ or archives calls. If you don’t need that speed or storage, a Raspberry Pi is cheaper, simpler, and the default recommendation. For the full walkthrough of this board see Rock Pi, and to compare alternatives — Khadas, PINE64, Orange Pi, ODROID — see best single-board computer for GopherTrunk.

Check price on Amazon →

As an Amazon Associate, GopherTrunk earns from qualifying purchases — at no extra cost to you. It never changes what we recommend.

Sources

  1. Radxa — Wikipedia, on Radxa and its Rock single-board computers. 

Frequently asked questions

Can I run GopherTrunk on a Radxa Rock 5B?

Yes. GopherTrunk is pure Go and cross-compiles to ARM64, so it runs on any Linux SBC with a USB port — no vendor toolchain. The RK3588 Rock 5B is the fastest board covered here, and its PCIe/NVMe storage suits an enthusiast multi-SDR node that records raw IQ or keeps a large call archive.

What's the difference between 'Radxa' and 'Rock Pi'?

Same company. Radxa is the maker; Rock Pi (and the newer Rock 5 series) is its main single-board-computer line. You’ll see both names on listings — the current flagship is the Rock 5B, and the RK3588 inside it is what makes it the top performer here.

Why pick a Radxa Rock 5B over a Raspberry Pi for GopherTrunk?

For I/O and speed: native NVMe over PCIe sustains the write throughput a busy capture-and-archive node generates, where a Pi’s microSD is slow and wears out. The extra cores and RAM give more room for decoding many channels. For a simple single-system node, a Raspberry Pi is cheaper, better documented, and the default recommendation.

Does a faster Radxa board decode encrypted channels?

No. No SBC changes the encryption wall — GopherTrunk cannot decode AES-protected traffic on any host. Faster hardware only lets you decode and store more unencrypted channels at once.

See also