PAGES
← all tools
◆ Hacking Hardware

bladeRF

2025.10 open-source

Free plan: not checked yet · Open source: yes

A USB 3.0 Superspeed Software Defined Radio.

What you can do now

Checking Plays…

Summary

bladeRF is an open-source software-defined radio platform, covering the firmware, FPGA HDL, and host libraries needed to program and interact with bladeRF hardware over USB 3. It is operated through the bladeRF-cli command-line utility, which lists attached devices, reports firmware and FPGA versions, and flashes new firmware images, with the underlying libbladeRF library available for building custom tools on top. This suits hardware hackers and RF researchers who need direct control over signal transmission and reception rather than a packaged analysis application, and it includes bladeRF-fsk, a CPFSK modem utility for chat or file transfer between two bladeRF units at 250 kbps. It sits in the SDRSDRSoftware-defined radio: hardware that captures raw radio-frequency signals and shifts signal processing into software, letting a single device tune any frequency or protocol a program implements. hacking-hardware category alongside general-purpose radio platforms rather than any single named competitor, and having launched in 2013, it remains the active source repository behind the Nuand bladeRF hardware line.

A USB 3.0 Superspeed Software Defined Radio.

How bladeRF helps

What bladeRF hardware is actually plugged into this machine right now?

lists every attached bladeRF board it can detect over USB, so a unit that isn't enumerating shows up as missing rather than silently ignored

Is this board running firmware and FPGA images that match what I think I flashed?

reports the firmware and FPGA version actually loaded on the device, which is how a stale or mismatched image gets caught before a signal test blames the wrong layer

Can two bladeRF units exchange a file or a chat message over the air right now, without building anything?

runs a CPFSK modem link between two boards at a fixed 250 kbps raw rate, giving a working transmit/receive path to confirm before writing custom signal code

How do I get a bricked or half-flashed board back to a working state?

boots the device into the FX3 recovery mode so a firmware image can be reloaded after an interrupted upgrade

What do I build against if I want my own signal-processing tool instead of a packaged app?

exposes the same host library the command-line utility is built on, so custom tools talk to the hardware directly rather than through a fixed set of features

all 11 features, with the evidence for each →

Languages

Not documented

Features

11 capabilities · 3 backed by code, an API document or a real run

Built from bladeRF's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What bladeRF offers you

  • Command-line interface2
All capabilities 11 capabilities
bladeRF SDR platform support shipped Provides the full software stack for the bladeRF software-defined radio platform, spanning FX3 firmware, Cyclone IV FPGA HDL, and host-side libraries and utilities. 14 releases · 1 other source · first seen Jul 2015

release 14 total

  • FPGA bitstream v0.16.0 2025.10 · Oct 2025 · source · release history
  • SC16Q11 packed format support in libbladeRF (improved bandwidth efficiency) 2025.10 · Oct 2025 · source · release history
  • Add 8bit format mode support in libbladeRF 2023.02 · Feb 2023 · source · release history
  • Adds AD936x overclocking feature to libbladeRF 2023.02 · Feb 2023 · source · release history
  • Adds hardware support for the bladeRF 2.0 micro xA5 board in the FPGA bitstream v0.14.0 2021.10 · Feb 2023 · source · release history
  • Enabled indication of packet cores presence in FPGA via bladeRF-cli 2021.02 · Feb 2021 · source · release history

docs

  • Source repository for the bladeRF SDR platform, including FX3 firmware, Cyclone IV FPGA HDL, and host libraries and utilities.
RF transmission and reception verified Enables direct control over RF signal generation and capture via CLI commands. 4 releases · 5 other sources · first seen Mar 2018

Also counts toward: Command-line interface

release

  • Added BLADERF_FORMAT_PACKET_META format to libbladeRF for exchanging variable length packets with the HDL 2021.02 · Feb 2021 · source · release history
  • Added RFIC parameters for burst waveforms 2021.02 · Feb 2021 · source · release history
  • Add tuning_mode setting in bladeRF-cli 2019.07 · Jul 2019 · source · release history
  • Add RFIC fitler selection in bladeRF-cli 2019.07 · Jul 2019 · source · release history

command line

example

  • Select a specific RFIC filter profile via the CLI. bladeRF-cli -s "rfic_filter <profile_name>" 2019.07 · Jul 2019 · source
Device discovery and inspection verified Lists connected bladeRF devices and displays device information and firmware/FPGA version details. 3 releases · 4 other sources · first seen Jul 2015

release

  • Enabled indication of packet cores presence in FPGA via bladeRF-cli 2021.02 · Feb 2021 · source · release history
  • bladeRF-cli supports opening devices via partial serial numbers using the -d "*:serial=<partial>" argument 2015.07 · Jul 2015 · source · release history
  • libbladeRF: bladerf_open() and bladerf_open_with_devinfo() now match devices by a subset of their serial number, enabling wildcard selection in the CLI 2015.07 · Jul 2015 · source · release history

command line

example

  • Open a specific bladeRF device when multiple are connected by matching the first few characters of the serial number. bladeRF-cli -i -d "*:serial=f12ce" 2015.07 · Jul 2015 · source
  • List detected bladeRF devices bladeRF-cli -p
  • Show device info and version bladeRF-cli -e info -e version
Firmware flashing verified Writes new firmware images to the bladeRF device's flash memory. 3 releases · 2 other sources · first seen Mar 2018

release

command line

example

  • Flash new firmware to device bladeRF-cli -f <firmware_file>
Protocol-specific FPGA architecture shipped Introduces specialized digital signal processing pipelines for standard radio protocols. 2 releases · first seen Jun 2016

release

  • Added RFIC parameters for burst waveforms 2021.02 · Feb 2021 · source · release history
  • FPGA introduces ADSB top-level architecture for out-of-tree core (requires https://github.com/nuand/bladeRF-adsb) 2016.06 · Jun 2016 · source · release history
RF power measurement shipped Allows users to measure RF power via a dedicated CLI utility. 1 release · first seen Oct 2025

release

  • bladeRF-power utility for RF power measurements via CLI 2025.10 · Oct 2025 · source · release history
Backend capability introspection shipped Allows querying the software backend for available handle and locking capabilities. 1 release · first seen Feb 2021

release

  • Added support for querying the backend for handle and lock capabilities 2021.02 · Feb 2021 · source · release history
Packet generation shipped Provides example utilities for generating and transmitting variable-length packets to the host. 1 release · first seen Feb 2021

release

  • Added packet_generator example for sending packets to the host 2021.02 · Feb 2021 · source · release history
MIMO support shipped Allows simultaneous multi-channel transmission and reception using multiple blades. 1 release · first seen Sep 2018

Also counts toward: Command-line interface

release

  • Support for MIMO RX and TX using channel= parameter on rx/tx config in bladeRF-cli 2018.08 · Sep 2018 · source · release history
Hardware trigger synchronization shipped Enables precise timing coordination between multiple devices via hardware pins. 1 release · first seen Jun 2016

release

  • FPGA bitstream adds synchronization trigger using J71 header pin 4 2016.06 · Jun 2016 · source · release history
Loopback testing support shipped Provides example configurations for verifying RF signal integrity through loopback paths. 1 release · first seen Jun 2016

release

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for bladeRF, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail bladeRF puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

8 entries

  1. October 20251
  2. February 20232
  3. February 20211
  4. July 20191
  5. September 20181
  6. June 20161
  7. July 20151
    Show

    8 entries

    Project health

    Issue, contributor and maintainer activity in Nuand/bladeRF, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 2 −3 vs prior 12 months
    2. Maintainers 1 +0 joined · −2 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 93% of issues opened, last 12 months
    5. Median time to close 2.2 years first maintainer reply 62 days
    6. Open backlog 114 of 695 issues ever filed
    1. Issues opened / month 2 · 0 communitymaintainers
    2. Open backlog 114
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars not measured
    Issue themes, last 12 months
    • other 100%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    Saved in this browser. Sign in to sync your tools.