Universal Zynq/AD9363 firmware builder
Universal firmware builder designed to unlock the full potential of your PlutoSDR/clone.
Built entirely for the SDR enthusiast community—bringing new features, wider frequency ranges, and massive performance boosts to your existing device.
Quick addition of new board (already 10 boards supported)
wg-quick config — no SSH/CLI needed.This firmware is developed entirely in my free time. Maintaining multiple boards, buying hardware for testing, and adding features takes significant time and resources. If tezuka supercharges your SDR experience, please consider supporting the project! No funds? You can still support by starring the repository or helping improve the documentation!
| Device Platform | Architecture | SD card | Gbe | DATV | USB Type | GPIO | Trusted vendors |
|---|---|---|---|---|---|---|---|
| PlutoSDR | 7010 | micro | digikey mouser | ||||
| PlutoPlus | 7010 | micro | OpenSdrLab | ||||
| Antsdr E200 | 7020 | usb-c | CrowdSupply | ||||
| Antsdr E310 | 7020 | usb-c | Microphase | ||||
| Fishball/PlutoSky | 7010 | usb-c | OpenSDRLab obsolete -> 7020 OpenSDRLab with box | ||||
| Fishball/PlutoSky | 7020 | usb-c | OpenSDRLab OpenSDRLab with box | ||||
| SignalSDRPro | 7020 | usb-3 | CrowdSupply | ||||
| LibreSDR/ZynqSDR | 7020 | usb-c | OpenSDRLab | ||||
| PlutoSky R2 | 7020 | usb-c | OpenSDRLab | ||||
| Pluto Nano | 7010 | usb-c | AliExpress HamGeek ? | ||||
| PCIe SDR 7010 | 7010 | Via PCIe | usb-c | OpenSDRLab | |||
| OpenSDRLab 7010 Mini | 7010 | usb-c | OpenSDRLab |
CRITICAL: DO NOT use the standard frm flashing method. To prevent bricking, always boot via SD card mode unless you know what you are doing.
sdimg folder onto the root of the SD Card.Only for original PlutoSDR (No SD Slot): Follow the official ADI flashing procedure using the pluto.frm file.
Once booted, the firmware exposes a USB drive containing config.txt. Modify this file to tweak your settings (based on standard ADI customization parameters).
Enjoy extra features out-of-the-box with custom-tailored software branches:
Connect your board to a remote WireGuard server for secure remote access, configured entirely from the Dashboard — no SSH/CLI needed:
wg-quick-style config ([Interface]/[Peer] blocks, private key included) into the text box and click Save & apply.AllowedIPs your config specifies — a scoped value gives split-tunnel access to just that network, while 0.0.0.0/0 routes all device traffic through the tunnel.Security note: the pasted config is sent once and never redisplayed or echoed back over MQTT. That said, the Dashboard's default MQTT channel (port 9001) is unauthenticated on the local network by design, same as every other Dashboard control — treat the WireGuard private key like any other credential on an open network segment, and avoid exposing the device's management interface to untrusted networks.
Onboard PSD spectral-shape matching — identifies signal types (OFDM, FSK, chirp, CW, etc.) live and overlays a label on the spectrum, right on the device, no host-side processing required:
tools/classifier_templates/, including a script to bootstrap templates directly from a live device — no GNU Radio/TorchSig install required for a first test) and pushed to the device the same way a WireGuard config is: base64 over MQTT (cmd/classifier/templates), which replaces the starter set permanently.This is spectral-shape matching (magnitude/PSD correlation), not true cyclostationary SCF — it separates signal types well but won't reliably distinguish modulation order within a family (e.g. BPSK vs. QPSK). It reuses the same live FFT feed the Spectrum and Radio Astronomy pages already consume (maia-httpd's /waterfall), so it adds no new consumer of the ADC and never competes with IQ Tape or the Signal Generator.
The same page also shows a band plan — a color-coded strip under the spectrum marking known allocations (broadcast, cellular, aviation, maritime, etc.), independent of whether the classifier has actually matched anything there. Click a swatch (or a row in the editable table below it) to tune to that frequency. Entries are stored on the device (/mnt/jffs2/bandplan.json, seeded from a starting reference table) and edited directly from the Dashboard — add, edit, or remove entries and hit Save.
# Install mandatory dependencies
sudo apt install pkg-config libssl-dev libclang-dev jq
# Clone the repository & pull Buildroot
git clone [https://github.com/F5OEO/tezuka_fw](https://github.com/F5OEO/tezuka_fw)
cd tezuka_fw
./getbuildroot.sh
# Build a single board (each board gets its own output directory):
./build.sh fishball
# Build multiple boards:
./build.sh pluto plutoplus fishball
# Build all boards:
./build.sh all
# Build with parallel jobs and clean output first:
./build.sh -j8 -c fishballOr build manually using Buildroot directly:
source sourceme.first
cd buildroot
make pluto_maiasdr_defconfig && makeFor a list all supported boards run:
./build.sh -hBuildroot does not allow whitespaces in the PATH environment variable. On WSL several paths with whitespaces are added. The following script can be used to remove any path with whitespaces. It also deletes any leftover ':' at the end:
export PATH=$(echo $PATH | tr ':' '\n' | grep -v ' ' | tr '\n' ':' | sed 's/:$//')If you encounter errors related to CMAKE policy version, it's because newer versions of CMAKE (3.27+) have stricter policy requirements. Setting CMAKE_POLICY_VERSION_MINIMUM=3.5 tells CMAKE to use policies from version 3.5 or newer, which helps maintain compatibility with older build scripts and dependencies that may not be fully compatible with the latest CMAKE policies. This is particularly important when building packages that haven't been updated to support newer CMAKE versions.
Run the build with:
CMAKE_POLICY_VERSION_MINIMUM=3.5 makeAll materials are in buildroot/output/images
No open issues yet, or sync has not completed.