Ettus Knowledge Base - User contributions [en]

Instructions for System Setup and Configuration

2026-10-19T09:27:05Z

SiddhantDhawan:

==Introduction==

This document provides instructions for attendees to setup and configure their laptop or desktop computer system for use with the hands-on exercises and labs for the "USRP Open-Source Toolchain: UHD and GNU Radio" workshop/tutorial.

Note that all of this is optional. You only have to do this if you want to use the USRP in the workshop to do the hands-on exercises and actually use the USRP radio. If you do not want to do this and just watch the instructor's presentation, then you can skip all of this and just come to the workshop.

This document assumes that you are using a USRP B200/B210 radio, although the USRP X300/X310, N300, N310, N320, N321, X410 may be used.

In some sessions the radio will be provided to you; in other sessions you will need to provide your own radio. Check this with the organizer of your session.

Your laptop or desktop computer should be no more than around six or seven years old, with an Intel i5, i7, or i9 CPU or AMD equivalent and at least 4 cores, running at a 3.5 GHz clock speed or higher, with 8 GB memory, and at least one USB 3.0 port (for USRP B200/B210 radios) and one RJ-45 Ethernet port (for other USRP radios). You will need about 30 GB of free disk space for the Linux installation. You will need to have internet access during the entire installation, set-up, and configuration process.

==Step 1: Install Xubuntu 24.04.4==

Install Xubuntu 24.04.4. Note that you may instead install Ubuntu itself, or any other Ubuntu flavor such as Kubuntu, Lubuntu, Cinnamon, MATE, or Linux Mint. However, we recommend using Xubuntu because it is very light-weight, and the user interface is easy-to-use and intuitive, and it runs well on older or resource-constrained hardware. We have only tested with Ubuntu and Xubuntu.

https://ubuntu.com/desktop/flavors

Please install on-the-metal, and not in a Virtual Machine (VM). Please install specifically version 24.04.4.

If you already have an existing Windows or Linux installation on your computer, then you can install Ubuntu or Xubuntu alongside your already-existing operating system, in a dual-boot configuration. The installer will ask you about this, and it supports installing in a dual-boot configuration. However, note that there can be some challenges when dual-booting with Windows 11, and this may not be easy to set up and may not work well.

You can download the ISO images for Xubuntu from the links below. Whichever version you choose: Write the ISO image to a USB 3.0 drive, and boot from it, and install it. The USB drive capacity must be a minimum of 16 GB.

https://xubuntu.org/download/

https://cdimage.ubuntu.com/xubuntu/releases/noble/release/

==Step 2: Installation Settings==

During the Xubuntu installation process, set the username to be "ettus". This is not strictly necessary, but if you do this, then it will make all the commands in the installation instructions and in the exercises work more easily. The hostname does not matter. Do not use any disk encryption. Do not enable any volume management.

==Step 3: Apply Updates==

Once the installation is complete, boot into it, and open a terminal window, and apply updates. Run the commands listed below, in a terminal window.

sudo apt update
sudo apt upgrade

==Step 4: Install Dependencies==

Install the package dependencies for UHD, GNU Radio, and other tools. Run the commands listed below, in a terminal window.

sudo apt-get install openssh-server htop tree lshw meld git libfftw3-bin ncurses-bin libncurses6 libncursesw6 net-tools ethtool aptitude screen hwloc inxi wireshark wireshark-doc wireshark-dev tshark build-essential ntp doxygen gnome-disk-utility cpufrequtils libsndfile1-dev

sudo apt-get install autoconf automake build-essential ccache cmake cpufrequtils doxygen ethtool g++ git inetutils-tools libboost-all-dev libncurses6 libncurses-dev libusb-1.0-0 libusb-1.0-0-dev libusb-dev python3-dev python3-mako python3-numpy python3-requests python3-scipy python3-setuptools python3-ruamel.yaml libfmt9 libfmt-dev libfmt-doc libspdlog1.12 libspdlog-dev

sudo apt-get install git cmake g++ libboost-all-dev libgmp-dev swig python3-numpy python3-mako python3-sphinx python3-lxml doxygen libfftw3-dev libsdl1.2-dev libgsl-dev libqwt-qt5-dev libqt5opengl5-dev python3-pyqt5 liblog4cpp5-dev libzmq3-dev python3-yaml python3-click python3-click-plugins python3-zmq python3-scipy python3-gi python3-gi-cairo gir1.2-gtk-3.0 libcodec2-dev libgsm1-dev libusb-1.0-0 libusb-1.0-0-dev libudev-dev python3-setuptools python3-pygccxml python3-thrift libqwt-qt5-6 libqwt-qt5-dev python3-pyqt5.qwt python3-qwt3d-qt5 libspdlog-dev libspdlog1.12 pybind11-dev python3-cppimport python3-pybind11 python3-pybindgen

==Step 5: Create a folder for GIT repositories==

Create a folder to hold all the GIT repositories. Run the commands listed below, in a terminal window.

mkdir $HOME/git

==Step 6: Create a work area folder==

Create a folder to hold workshop materials and for running exercises. Run the commands listed below, in a terminal window.

mkdir $HOME/workarea

==Step 7: Download the slides and materials==

Download the slides and materials for the workshop from the Ettus Knowledge Base (KB). Run the commands listed below, in a terminal window.

wget -P $HOME/workarea https://kb.ettus.com/images/a/ab/Workshop_GnuRadio_Materials_20171212.tar.gz
wget -P $HOME/workarea https://kb.ettus.com/images/f/fd/Workshop_GnuRadio_Slides_20250802.pdf

==Step 8: Unzip the materials==

Unzip the workshop materials file. Run the commands listed below, in a terminal window.

cd $HOME/workarea
tar zxvf Workshop_GnuRadio_Materials_20171212.tar.gz

==Step 9: Install UHD 4.9==

Install UHD version 4.9, and download all the USRP FPGA image files. Run the commands listed below, in a terminal window.

cd $HOME/git
git clone http://github.com/EttusResearch/uhd.git
cd uhd/host
mkdir build
cd build
git checkout v4.9.0.0
cmake ../
make -j4
sudo make install
sudo ldconfig
sudo uhd_images_downloader

==Step 10: Install VOLK 3.3.0==

Install the VOLK library. This used to be bundled with GNU Radio, but now it's broken out as a separate library. Run the commands listed below, in a terminal window.

cd $HOME/git
git clone --recursive https://github.com/gnuradio/volk.git
cd volk
mkdir build
cd build
git checkout v3.3.0
cmake -DCMAKE_BUILD_TYPE=Release -DPYTHON_EXECUTABLE=/usr/bin/python3 ../
cd ../
git submodule update --init --recursive
ls cpu_features/CMakeLists.txt #it should show cpu_features/CMakeLists.txt
cd build
cmake -DCMAKE_BUILD_TYPE=Release -DPYTHON_EXECUTABLE=/usr/bin/python3 ../
make -j4
sudo make install
sudo ldconfig

==Step 11: Install GNU Radio 3.10.12==

Install GNU Radio version 3.10.12. Run the commands listed below, in a terminal window.

cd $HOME/git
git clone http://github.com/gnuradio/gnuradio.git
cd gnuradio
mkdir build
cd build
git checkout v3.10.12.0
cmake ../
make -j4
sudo make install
sudo ldconfig

==Step 12: Update the Bash RC shell file==

Add the following lines the end of your <code> $HOME/.bashrc </code> file. Use your preferred editor such as the graphical ones Gedit or Mousepad or a console-based text editor such as vi or emacs.

First, open the file using either the text editor.

mousepad $HOME/.bashrc
gedit $HOME/.bashrc
emacs $HOME/.bashrc

Next, add the two lines listed below to the very end of the file:

export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH
export PYTHONPATH=/usr/local/lib/python3.12/dist-packages:/usr/local/lib/python3.12/site-packages:$PYTHONPATH

Then, save the file, exit and close the text editor, exit and close the terminal window, and open a brand-new terminal window. Run the following command to verify that the PYTHONPATH variable is set:

python3 -c "import sys; print(sys.path)" | tr ',' '\n' | grep "\-packages"

and both of the paths above should be listed.

==Step 13: Apply the USB udev rules==

Apply the USB udev rules for the USRP B200/B210. If you are not using a USRP B200/B210, but some other Ethernet-based radio, then you can skip this step, although it is still good to do. Run the commands listed below, in a terminal window.

cd /usr/local/lib/uhd/utils
sudo cp uhd-usrp.rules /etc/udev/rules.d/
sudo udevadm control --reload-rules
sudo udevadm trigger

==Step 14: Install gr-osmosdr==

Install the gr-osmosdr Out-Of-Tree (OOT) module. Run the commands listed below, in a terminal window.

cd $HOME/git
git clone https://github.com/osmocom/gr-osmosdr
cd gr-osmosdr
mkdir build
cd build
cmake ../
make -j4
sudo make install
sudo ldconfig

==Step 15: Install gr-rds==

Install the gr-rds Out-Of-Tree (OOT) module. Run the commands listed below, in a terminal window.

cd $HOME/git
git clone https://github.com/bastibl/gr-rds
cd gr-rds
mkdir build
cd build
git checkout maint-3.10
cmake ../
make -j4
sudo make install
sudo ldconfig

==Step 16: Install GQRX==

Install GQRX. You will also need to install two more package dependencies. Run the commands listed below, in a terminal window.

sudo apt-get install libqt5svg5 libqt5svg5-dev
cd $HOME/git
git clone https://github.com/gqrx-sdr/gqrx
cd gqrx
mkdir build
cd build
git checkout v2.17.7
cmake ../
make -j4
sudo make install
sudo ldconfig

==Step 17: Install gr-paint==

Install gr-paint. Run the commands listed below, in a terminal window.

cd $HOME/git
git clone https://github.com/drmpeg/gr-paint
cd gr-paint
mkdir build
cd build
cmake ../
make -j4
sudo make install
sudo ldconfig

==Test the Installation==

If you did not see any errors in any of the previous steps, then your installation and configuration should now be complete. You can run a few simple and quick tests to verify that your system is running correctly and is ready for the workshop/tutorial.

First, run the commands below, even if you do not have any USRP radio connected to your computer.

uhd_find_devices
uhd_usrp_probe

You should see output similar to what is listed below when there is no USRP device connected.

ettus@lenovo-t480s:~$ uhd_find_devices
[INFO] [UHD] linux; GNU C++ version 13.3.0; Boost_108300; UHD_4.9.0.HEAD-0-g9ec1f582
No UHD Devices Found
ettus@lenovo-t480s:~$ uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 13.3.0; Boost_108300; UHD_4.9.0.HEAD-0-g9ec1f582
Error: LookupError: KeyError: No devices found for ----->
Empty Device Address
ettus@lenovo-t480s:~$

You should see output similar to what is listed below when there is one USRP B200 device connected.

ettus@lenovo-t480s:~$ uhd_find_devices
[INFO] [UHD] linux; GNU C++ version 13.3.0; Boost_108300; UHD_4.9.0.HEAD-0-g9ec1f582
[INFO] [B200] Loading firmware image: /usr/local/share/uhd/images/usrp_b200_fw.hex...
--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
serial: 3304B90
name: 4B200
product: B200
type: b200

ettus@lenovo-t480s:~$ uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 13.3.0; Boost_108300; UHD_4.9.0.HEAD-0-g9ec1f582
[INFO] [B200] Detected Device: B200
[INFO] [B200] Loading FPGA image: /usr/local/share/uhd/images/usrp_b200_fpga.bin...
[INFO] [B200] Operating over USB 3.
[INFO] [B200] Detecting internal GPSDO....
[INFO] [GPS] No GPSDO found
[INFO] [B200] Initialize CODEC control...
[INFO] [B200] Initialize Radio control...
[INFO] [B200] Performing register loopback test...
[INFO] [B200] Register loopback test passed
[INFO] [B200] Setting master clock rate selection to 'automatic'.
[INFO] [B200] Asking for clock rate 16.000000 MHz...
[INFO] [B200] Actually got clock rate 16.000000 MHz.
_____________________________________________________
/
| Device: B-Series Device
| _____________________________________________________
| /
| | Mboard: B200
| | serial: 3304B90
| | name: 4B200
| | product: 1
| | revision: 5
| | FW Version: 8.0
| | FPGA Version: 16.0
| |
| | Time sources: none, internal, external, gpsdo
| | Clock sources: internal, external, gpsdo
| | Sensors: ref_locked
| | _____________________________________________________
| | /
| | | RX DSP: 0
| | |
| | | Freq range: -8.000 to 8.000 MHz
| | _____________________________________________________
| | /
| | | RX Dboard: A
| | | _____________________________________________________
| | | /
| | | | RX Frontend: A
| | | | Name: FE-RX1
| | | | Antennas: TX/RX, RX2
| | | | Sensors: temp, rssi, lo_locked
| | | | Freq range: 50.000 to 6000.000 MHz
| | | | Gain range PGA: 0.0 to 76.0 step 1.0 dB
| | | | Bandwidth range: 200000.0 to 56000000.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | RX Codec: A
| | | | Name: B200 RX dual ADC
| | | | Gain Elements: None
| | _____________________________________________________
| | /
| | | TX DSP: 0
| | |
| | | Freq range: -8.000 to 8.000 MHz
| | _____________________________________________________
| | /
| | | TX Dboard: A
| | | _____________________________________________________
| | | /
| | | | TX Frontend: A
| | | | Name: FE-TX1
| | | | Antennas: TX/RX
| | | | Sensors: temp, lo_locked
| | | | Freq range: 50.000 to 6000.000 MHz
| | | | Gain range PGA: 0.0 to 89.8 step 0.2 dB
| | | | Bandwidth range: 200000.0 to 56000000.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | TX Codec: A
| | | | Name: B200 TX dual DAC
| | | | Gain Elements: None

ettus@lenovo-t480s:~$

Second, you can run the GNU Radio Companion (GRC) tool. Run the commands below, and verify that the GRC window appears.

gnuradio-companion

Third, you can connect the USRP B200/B210 to the computer, and then run the command listed below.

lsusb

You should see the USRP listed in the output, as shown below.

ettus@lenovo-t480s:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 03f0:6a41 HP, Inc HP USB Optical Mouse
Bus 001 Device 005: ID 2500:0020 Ettus Research LLC USRP B210
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. Card Reader
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
ettus@lenovo-t480s:~$

Fourth, you can run the command below, to confirm that GNU Radio is configured correctly, and that you are running the correct version.

ettus@lenovo-t480s:~$ gnuradio-config-info --print-all
/usr/local/
/usr/local/etc
/usr/local/etc/gnuradio/conf.d
/home/ettus/.config/gnuradio
/home/ettus/.local/state/gnuradio
Fri, 09 Jan 2026 14:37:15Z
testing-support;python-support;post-install;doxygen;man-pages;gnuradio-runtime;common-precompiled-headers;gr-ctrlport;gnuradio-companion;JSON/YAML config blocks;gr-blocks;gr-fec;gr-fft;gr-filter;gr-analog;gr-digital;gr-dtv;gr-audio;* alsa;* oss;gr-channels;gr-pdu;gr-qtgui;gr-trellis;gr-uhd;gr-uhd UHD 4.0 RFNoC;gr-utils;gr_modtool;gr_blocktool;gr-video-sdl;gr-vocoder;* codec2;* freedv;* gsm;gr-wavelet;gr-zeromq;gr-network
3.10.12.0
cc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software see the source for copying conditions. There is NO
warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
c++ (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software see the source for copying conditions. There is NO
warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
/usr/bin/cc:::-O3 -DNDEBUG -fvisibility=hidden -Wsign-compare -Wall -Wno-uninitialized -Wignored-qualifiers -Wcast-qual
/usr/bin/c++:::-O3 -DNDEBUG -fvisibility=hidden -Wsign-compare -Wall -Wno-uninitialized -Wignored-qualifiers -Wcast-qual
2.11.1
ettus@lenovo-t480s:~$

==Conclusion==

If the simple tests of the installation listed above worked without any errors, then you are now finished, and you are now ready for the workshop/tutorial.

We look forward to seeing you in the workshop/tutorial.

Instructions for System Setup and Configuration

2026-10-19T09:25:52Z

SiddhantDhawan: cd ../ git submodule update --init --recursive ls cpu_features/CMakeLists.txt #it should show cpu_features_CMakeLists.txt cd build cmake -DCMAKE_BUILD_TYPE=Release -DPYTHON_EXECUTABLE=/usr/bin/python3 ../

==Introduction==

This document provides instructions for attendees to setup and configure their laptop or desktop computer system for use with the hands-on exercises and labs for the "USRP Open-Source Toolchain: UHD and GNU Radio" workshop/tutorial.

Note that all of this is optional. You only have to do this if you want to use the USRP in the workshop to do the hands-on exercises and actually use the USRP radio. If you do not want to do this and just watch the instructor's presentation, then you can skip all of this and just come to the workshop.

This document assumes that you are using a USRP B200/B210 radio, although the USRP X300/X310, N300, N310, N320, N321, X410 may be used.

In some sessions the radio will be provided to you; in other sessions you will need to provide your own radio. Check this with the organizer of your session.

Your laptop or desktop computer should be no more than around six or seven years old, with an Intel i5, i7, or i9 CPU or AMD equivalent and at least 4 cores, running at a 3.5 GHz clock speed or higher, with 8 GB memory, and at least one USB 3.0 port (for USRP B200/B210 radios) and one RJ-45 Ethernet port (for other USRP radios). You will need about 30 GB of free disk space for the Linux installation. You will need to have internet access during the entire installation, set-up, and configuration process.

==Step 1: Install Xubuntu 24.04.4==

Install Xubuntu 24.04.4. Note that you may instead install Ubuntu itself, or any other Ubuntu flavor such as Kubuntu, Lubuntu, Cinnamon, MATE, or Linux Mint. However, we recommend using Xubuntu because it is very light-weight, and the user interface is easy-to-use and intuitive, and it runs well on older or resource-constrained hardware. We have only tested with Ubuntu and Xubuntu.

https://ubuntu.com/desktop/flavors

Please install on-the-metal, and not in a Virtual Machine (VM). Please install specifically version 24.04.4.

If you already have an existing Windows or Linux installation on your computer, then you can install Ubuntu or Xubuntu alongside your already-existing operating system, in a dual-boot configuration. The installer will ask you about this, and it supports installing in a dual-boot configuration. However, note that there can be some challenges when dual-booting with Windows 11, and this may not be easy to set up and may not work well.

You can download the ISO images for Xubuntu from the links below. Whichever version you choose: Write the ISO image to a USB 3.0 drive, and boot from it, and install it. The USB drive capacity must be a minimum of 16 GB.

https://xubuntu.org/download/

https://cdimage.ubuntu.com/xubuntu/releases/noble/release/

==Step 2: Installation Settings==

During the Xubuntu installation process, set the username to be "ettus". This is not strictly necessary, but if you do this, then it will make all the commands in the installation instructions and in the exercises work more easily. The hostname does not matter. Do not use any disk encryption. Do not enable any volume management.

==Step 3: Apply Updates==

Once the installation is complete, boot into it, and open a terminal window, and apply updates. Run the commands listed below, in a terminal window.

sudo apt update
sudo apt upgrade

==Step 4: Install Dependencies==

Install the package dependencies for UHD, GNU Radio, and other tools. Run the commands listed below, in a terminal window.

sudo apt-get install openssh-server htop tree lshw meld git libfftw3-bin ncurses-bin libncurses6 libncursesw6 net-tools ethtool aptitude screen hwloc inxi wireshark wireshark-doc wireshark-dev tshark build-essential ntp doxygen gnome-disk-utility cpufrequtils libsndfile1-dev

sudo apt-get install autoconf automake build-essential ccache cmake cpufrequtils doxygen ethtool g++ git inetutils-tools libboost-all-dev libncurses6 libncurses-dev libusb-1.0-0 libusb-1.0-0-dev libusb-dev python3-dev python3-mako python3-numpy python3-requests python3-scipy python3-setuptools python3-ruamel.yaml libfmt9 libfmt-dev libfmt-doc libspdlog1.12 libspdlog-dev

sudo apt-get install git cmake g++ libboost-all-dev libgmp-dev swig python3-numpy python3-mako python3-sphinx python3-lxml doxygen libfftw3-dev libsdl1.2-dev libgsl-dev libqwt-qt5-dev libqt5opengl5-dev python3-pyqt5 liblog4cpp5-dev libzmq3-dev python3-yaml python3-click python3-click-plugins python3-zmq python3-scipy python3-gi python3-gi-cairo gir1.2-gtk-3.0 libcodec2-dev libgsm1-dev libusb-1.0-0 libusb-1.0-0-dev libudev-dev python3-setuptools python3-pygccxml python3-thrift libqwt-qt5-6 libqwt-qt5-dev python3-pyqt5.qwt python3-qwt3d-qt5 libspdlog-dev libspdlog1.12 pybind11-dev python3-cppimport python3-pybind11 python3-pybindgen

==Step 5: Create a folder for GIT repositories==

Create a folder to hold all the GIT repositories. Run the commands listed below, in a terminal window.

mkdir $HOME/git

==Step 6: Create a work area folder==

Create a folder to hold workshop materials and for running exercises. Run the commands listed below, in a terminal window.

mkdir $HOME/workarea

==Step 7: Download the slides and materials==

Download the slides and materials for the workshop from the Ettus Knowledge Base (KB). Run the commands listed below, in a terminal window.

wget -P $HOME/workarea https://kb.ettus.com/images/a/ab/Workshop_GnuRadio_Materials_20171212.tar.gz
wget -P $HOME/workarea https://kb.ettus.com/images/f/fd/Workshop_GnuRadio_Slides_20250802.pdf

==Step 8: Unzip the materials==

Unzip the workshop materials file. Run the commands listed below, in a terminal window.

cd $HOME/workarea
tar zxvf Workshop_GnuRadio_Materials_20171212.tar.gz

==Step 9: Install UHD 4.9==

Install UHD version 4.9, and download all the USRP FPGA image files. Run the commands listed below, in a terminal window.

cd $HOME/git
git clone http://github.com/EttusResearch/uhd.git
cd uhd/host
mkdir build
cd build
git checkout v4.9.0.0
cmake ../
make -j4
sudo make install
sudo ldconfig
sudo uhd_images_downloader

==Step 10: Install VOLK 3.3.0==

Install the VOLK library. This used to be bundled with GNU Radio, but now it's broken out as a separate library. Run the commands listed below, in a terminal window.

cd $HOME/git
git clone --recursive https://github.com/gnuradio/volk.git
cd volk
mkdir build
cd build
git checkout v3.3.0
cmake -DCMAKE_BUILD_TYPE=Release -DPYTHON_EXECUTABLE=/usr/bin/python3 ../
cd ../
git submodule update --init --recursive
ls cpu_features/CMakeLists.txt #it should show cpu_features_CMakeLists.txt
cd build
cmake -DCMAKE_BUILD_TYPE=Release -DPYTHON_EXECUTABLE=/usr/bin/python3 ../
make -j4
sudo make install
sudo ldconfig

==Step 11: Install GNU Radio 3.10.12==

Install GNU Radio version 3.10.12. Run the commands listed below, in a terminal window.

cd $HOME/git
git clone http://github.com/gnuradio/gnuradio.git
cd gnuradio
mkdir build
cd build
git checkout v3.10.12.0
cmake ../
make -j4
sudo make install
sudo ldconfig

==Step 12: Update the Bash RC shell file==

Add the following lines the end of your <code> $HOME/.bashrc </code> file. Use your preferred editor such as the graphical ones Gedit or Mousepad or a console-based text editor such as vi or emacs.

First, open the file using either the text editor.

mousepad $HOME/.bashrc
gedit $HOME/.bashrc
emacs $HOME/.bashrc

Next, add the two lines listed below to the very end of the file:

export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH
export PYTHONPATH=/usr/local/lib/python3.12/dist-packages:/usr/local/lib/python3.12/site-packages:$PYTHONPATH

Then, save the file, exit and close the text editor, exit and close the terminal window, and open a brand-new terminal window. Run the following command to verify that the PYTHONPATH variable is set:

python3 -c "import sys; print(sys.path)" | tr ',' '\n' | grep "\-packages"

and both of the paths above should be listed.

==Step 13: Apply the USB udev rules==

Apply the USB udev rules for the USRP B200/B210. If you are not using a USRP B200/B210, but some other Ethernet-based radio, then you can skip this step, although it is still good to do. Run the commands listed below, in a terminal window.

cd /usr/local/lib/uhd/utils
sudo cp uhd-usrp.rules /etc/udev/rules.d/
sudo udevadm control --reload-rules
sudo udevadm trigger

==Step 14: Install gr-osmosdr==

Install the gr-osmosdr Out-Of-Tree (OOT) module. Run the commands listed below, in a terminal window.

cd $HOME/git
git clone https://github.com/osmocom/gr-osmosdr
cd gr-osmosdr
mkdir build
cd build
cmake ../
make -j4
sudo make install
sudo ldconfig

==Step 15: Install gr-rds==

Install the gr-rds Out-Of-Tree (OOT) module. Run the commands listed below, in a terminal window.

cd $HOME/git
git clone https://github.com/bastibl/gr-rds
cd gr-rds
mkdir build
cd build
git checkout maint-3.10
cmake ../
make -j4
sudo make install
sudo ldconfig

==Step 16: Install GQRX==

Install GQRX. You will also need to install two more package dependencies. Run the commands listed below, in a terminal window.

sudo apt-get install libqt5svg5 libqt5svg5-dev
cd $HOME/git
git clone https://github.com/gqrx-sdr/gqrx
cd gqrx
mkdir build
cd build
git checkout v2.17.7
cmake ../
make -j4
sudo make install
sudo ldconfig

==Step 17: Install gr-paint==

Install gr-paint. Run the commands listed below, in a terminal window.

cd $HOME/git
git clone https://github.com/drmpeg/gr-paint
cd gr-paint
mkdir build
cd build
cmake ../
make -j4
sudo make install
sudo ldconfig

==Test the Installation==

If you did not see any errors in any of the previous steps, then your installation and configuration should now be complete. You can run a few simple and quick tests to verify that your system is running correctly and is ready for the workshop/tutorial.

First, run the commands below, even if you do not have any USRP radio connected to your computer.

uhd_find_devices
uhd_usrp_probe

You should see output similar to what is listed below when there is no USRP device connected.

ettus@lenovo-t480s:~$ uhd_find_devices
[INFO] [UHD] linux; GNU C++ version 13.3.0; Boost_108300; UHD_4.9.0.HEAD-0-g9ec1f582
No UHD Devices Found
ettus@lenovo-t480s:~$ uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 13.3.0; Boost_108300; UHD_4.9.0.HEAD-0-g9ec1f582
Error: LookupError: KeyError: No devices found for ----->
Empty Device Address
ettus@lenovo-t480s:~$

You should see output similar to what is listed below when there is one USRP B200 device connected.

ettus@lenovo-t480s:~$ uhd_find_devices
[INFO] [UHD] linux; GNU C++ version 13.3.0; Boost_108300; UHD_4.9.0.HEAD-0-g9ec1f582
[INFO] [B200] Loading firmware image: /usr/local/share/uhd/images/usrp_b200_fw.hex...
--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
serial: 3304B90
name: 4B200
product: B200
type: b200

ettus@lenovo-t480s:~$ uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 13.3.0; Boost_108300; UHD_4.9.0.HEAD-0-g9ec1f582
[INFO] [B200] Detected Device: B200
[INFO] [B200] Loading FPGA image: /usr/local/share/uhd/images/usrp_b200_fpga.bin...
[INFO] [B200] Operating over USB 3.
[INFO] [B200] Detecting internal GPSDO....
[INFO] [GPS] No GPSDO found
[INFO] [B200] Initialize CODEC control...
[INFO] [B200] Initialize Radio control...
[INFO] [B200] Performing register loopback test...
[INFO] [B200] Register loopback test passed
[INFO] [B200] Setting master clock rate selection to 'automatic'.
[INFO] [B200] Asking for clock rate 16.000000 MHz...
[INFO] [B200] Actually got clock rate 16.000000 MHz.
_____________________________________________________
/
| Device: B-Series Device
| _____________________________________________________
| /
| | Mboard: B200
| | serial: 3304B90
| | name: 4B200
| | product: 1
| | revision: 5
| | FW Version: 8.0
| | FPGA Version: 16.0
| |
| | Time sources: none, internal, external, gpsdo
| | Clock sources: internal, external, gpsdo
| | Sensors: ref_locked
| | _____________________________________________________
| | /
| | | RX DSP: 0
| | |
| | | Freq range: -8.000 to 8.000 MHz
| | _____________________________________________________
| | /
| | | RX Dboard: A
| | | _____________________________________________________
| | | /
| | | | RX Frontend: A
| | | | Name: FE-RX1
| | | | Antennas: TX/RX, RX2
| | | | Sensors: temp, rssi, lo_locked
| | | | Freq range: 50.000 to 6000.000 MHz
| | | | Gain range PGA: 0.0 to 76.0 step 1.0 dB
| | | | Bandwidth range: 200000.0 to 56000000.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | RX Codec: A
| | | | Name: B200 RX dual ADC
| | | | Gain Elements: None
| | _____________________________________________________
| | /
| | | TX DSP: 0
| | |
| | | Freq range: -8.000 to 8.000 MHz
| | _____________________________________________________
| | /
| | | TX Dboard: A
| | | _____________________________________________________
| | | /
| | | | TX Frontend: A
| | | | Name: FE-TX1
| | | | Antennas: TX/RX
| | | | Sensors: temp, lo_locked
| | | | Freq range: 50.000 to 6000.000 MHz
| | | | Gain range PGA: 0.0 to 89.8 step 0.2 dB
| | | | Bandwidth range: 200000.0 to 56000000.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | TX Codec: A
| | | | Name: B200 TX dual DAC
| | | | Gain Elements: None

ettus@lenovo-t480s:~$

Second, you can run the GNU Radio Companion (GRC) tool. Run the commands below, and verify that the GRC window appears.

gnuradio-companion

Third, you can connect the USRP B200/B210 to the computer, and then run the command listed below.

lsusb

You should see the USRP listed in the output, as shown below.

ettus@lenovo-t480s:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 03f0:6a41 HP, Inc HP USB Optical Mouse
Bus 001 Device 005: ID 2500:0020 Ettus Research LLC USRP B210
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. Card Reader
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
ettus@lenovo-t480s:~$

Fourth, you can run the command below, to confirm that GNU Radio is configured correctly, and that you are running the correct version.

ettus@lenovo-t480s:~$ gnuradio-config-info --print-all
/usr/local/
/usr/local/etc
/usr/local/etc/gnuradio/conf.d
/home/ettus/.config/gnuradio
/home/ettus/.local/state/gnuradio
Fri, 09 Jan 2026 14:37:15Z
testing-support;python-support;post-install;doxygen;man-pages;gnuradio-runtime;common-precompiled-headers;gr-ctrlport;gnuradio-companion;JSON/YAML config blocks;gr-blocks;gr-fec;gr-fft;gr-filter;gr-analog;gr-digital;gr-dtv;gr-audio;* alsa;* oss;gr-channels;gr-pdu;gr-qtgui;gr-trellis;gr-uhd;gr-uhd UHD 4.0 RFNoC;gr-utils;gr_modtool;gr_blocktool;gr-video-sdl;gr-vocoder;* codec2;* freedv;* gsm;gr-wavelet;gr-zeromq;gr-network
3.10.12.0
cc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software see the source for copying conditions. There is NO
warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
c++ (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software see the source for copying conditions. There is NO
warranty not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
/usr/bin/cc:::-O3 -DNDEBUG -fvisibility=hidden -Wsign-compare -Wall -Wno-uninitialized -Wignored-qualifiers -Wcast-qual
/usr/bin/c++:::-O3 -DNDEBUG -fvisibility=hidden -Wsign-compare -Wall -Wno-uninitialized -Wignored-qualifiers -Wcast-qual
2.11.1
ettus@lenovo-t480s:~$

==Conclusion==

If the simple tests of the installation listed above worked without any errors, then you are now finished, and you are now ready for the workshop/tutorial.

We look forward to seeing you in the workshop/tutorial.

Verifying the Operation of the USRP Using UHD and GNU Radio

2026-08-02T19:24:02Z

SiddhantDhawan:

==Application Note Information==
'''AN-936'''

==Authors==
Neel Pandeya and Siddhant Dhawan

==Abstract==
This AN explains how to use UHD and GNU Radio, once installed, to verify the correct operation of the USRP. Several test procedures are explained in detail. Several tests make use of an optional spectrum analyzer and signal generator.

==Overview==
This application note will cover testing your USRP to verify it is operational. You will need to have a working installation of UHD to preform the following steps to verify your USRP. If you do not have UHD installed, please reference the Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on Linux|Linux]], [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on OS X|OS X]] and [[Building and Installing the USRP Open Source Toolchain (UHD and GNU Radio) on Windows|Windows]] Application Notes.

Alternatively, you may use the [[Live SDR Environment]] to perform the following steps. More information about the [[Live SDR Environment]] is available at the [[Live SDR Environment Getting Started Guides]] page.

==Proper Care and Handling==
All Ettus Research products are individually tested before shipment. The USRP™ is guaranteed to be functional at the time it is received by the customer. Improper use or handling of the USRP™ can easily cause the device to become non-functional. Listed below are some examples of actions which can prevent damage to the unit:

*Never allow metal objects to touch the circuit board while powered.
*Always properly terminate the transmit port with an antenna or 50Ω load.
*Always handle the board with proper anti-static methods.
*Never allow the board to directly or indirectly come into contact with any voltage spikes.
*Never allow any water, or condensing moisture, to come into contact with the boards.
*Always use caution with FPGA, firmware, or software modifications.
{|
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |[[File:Caution.png|24px|center]]
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |Never apply more than -15 dBm of power into any RF input
|-
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |[[File:Caution.png|24px|center]]
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |Always use at least 30dB attenuation if operating in loopback configuration
|-
|}

==Finding the Device==
*Report detailed information on UHD-supported Software Radio Peripherals attached by USB, network, or embedded configuration. Details include unit names, revision numbers, and available sensors on all attached USRP motherboards and daughterboards.
uhd_usrp_probe

Example output from <code>uhd_usrp_probe</code>:

<pre>
ettus-24-02@ettus-24-02-Dell-Pro-16-PC16255:~$ uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 13.3.0; Boost_108300; UHD_4.9.0.HEAD-0-g006d7f76
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum frame size: 1472 bytes.
[INFO] [X300] Radio 1x clock: 200 MHz
_____________________________________________________
/
| Device: X-Series Device
| _____________________________________________________
| /
| | Mboard: X310
| | revision: 11
| | revision_compat: 4
| | product: 30720
| | mac-addr0: 00:80:2f:21:9b:fa
| | mac-addr1: 00:80:2f:21:9b:fb
| | gateway: 192.168.10.1
| | ip-addr0: 192.168.10.3
| | subnet0: 255.255.255.0
| | ip-addr1: 192.168.20.2
| | subnet1: 255.255.255.0
| | ip-addr2: 192.168.30.2
| | subnet2: 255.255.255.0
| | ip-addr3: 192.168.40.2
| | subnet3: 255.255.255.0
| | serial: 30A0656
| | FW Version: 6.1
| | FPGA Version: 39.2
| | FPGA git hash: 6a990d9
| | RFNoC capable: Yes
| |
| | Time sources: internal, external, gpsdo
| | Clock sources: internal, external, gpsdo
| | Sensors: temp_fpga, ref_locked
| _____________________________________________________
| /
| | RFNoC blocks on this device:
| |
| | * 0/DDC#0
| | * 0/DDC#1
| | * 0/DUC#0
| | * 0/DUC#1
| | * 0/Radio#0
| | * 0/Radio#1
| | * 0/Replay#0
| _____________________________________________________
| /
| | Static connections on this device:
| |
| | * 0/SEP#0:0==>0/DUC#0:0
| | * 0/DUC#0:0==>0/Radio#0:0
| | * 0/Radio#0:0==>0/DDC#0:0
| | * 0/DDC#0:0==>0/SEP#0:0
| | * 0/Radio#0:1==>0/DDC#0:1
| | * 0/DDC#0:1==>0/SEP#1:0
| | * 0/SEP#2:0==>0/DUC#1:0
| | * 0/DUC#1:0==>0/Radio#1:0
| | * 0/Radio#1:0==>0/DDC#1:0
| | * 0/DDC#1:0==>0/SEP#2:0
| | * 0/Radio#1:1==>0/DDC#1:1
| | * 0/DDC#1:1==>0/SEP#3:0
| | * 0/SEP#4:0==>0/Replay#0:0
| | * 0/Replay#0:0==>0/SEP#4:0
| | * 0/SEP#5:0==>0/Replay#0:1
| | * 0/Replay#0:1==>0/SEP#5:0
| _____________________________________________________
| /
| | TX Dboard: 0/Radio#0
| | ID: UBX-TDD (0x0202)
| | Serial: 322248F
| | Revision: 2
| | _____________________________________________________
| | /
| | | TX Frontend: 0
| | | Name: UBX TX
| | | Antennas: TX/RX, CAL
| | | Sensors: lo_locked
| | | Freq range: 10.000 to 6000.000 MHz
| | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB
| | | Bandwidth range: 160000000.0 to 160000000.0 step 0.0 Hz
| | | Connection Type: QI
| | | Uses LO offset: No
| _____________________________________________________
| /
| | RX Dboard: 0/Radio#0
| | ID: UBX-TDD (0x0203)
| | Serial: 322248F
| | Revision: 2
| | _____________________________________________________
| | /
| | | RX Frontend: 0
| | | Name: UBX RX
| | | Antennas: TX/RX, RX2, CAL
| | | Sensors: lo_locked
| | | Freq range: 10.000 to 6000.000 MHz
| | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB
| | | Bandwidth range: 160000000.0 to 160000000.0 step 0.0 Hz
| | | Connection Type: IQ
| | | Uses LO offset: No
| _____________________________________________________
| /
| | TX Dboard: 0/Radio#1
| | ID: CBX-120 (0x0084)
| | Serial: 313BF2A
| | Revision: 1
| | _____________________________________________________
| | /
| | | TX Frontend: 0
| | | Name: CBX-120 TX
| | | Antennas: TX/RX, CAL
| | | Sensors: lo_locked
| | | Freq range: 1200.000 to 6000.000 MHz
| | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB
| | | Bandwidth range: 120000000.0 to 120000000.0 step 0.0 Hz
| | | Connection Type: QI
| | | Uses LO offset: No
| _____________________________________________________
| /
| | RX Dboard: 0/Radio#1
| | ID: CBX-120 (0x0085)
| | Serial: 313BF2A
| | Revision: 1
| | _____________________________________________________
| | /
| | | RX Frontend: 0
| | | Name: CBX-120 RX
| | | Antennas: TX/RX, RX2, CAL
| | | Sensors: lo_locked
| | | Freq range: 1200.000 to 6000.000 MHz
| | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB
| | | Bandwidth range: 120000000.0 to 120000000.0 step 0.0 Hz
| | | Connection Type: IQ
| | | Uses LO offset: No

</pre>

*Find UHD-supporting Software Radio Peripherals attached by USB, network or embedded configuration. Uses broadcast packets for discovery. Often blocked by routers, switches, firewalls.
uhd_find_devices

Example output from <code>uhd_find_devices</code>:

<pre>
[INFO] [UHD] linux; GNU C++ version 13.3.0; Boost_108300; UHD_4.9.0.HEAD-0-g006d7f76
--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
serial: 30A0656
addr: 192.168.10.3
fpga: HG
name:
product: X310
type: x300

--------------------------------------------------
-- UHD Device 1
--------------------------------------------------
Device Address:
serial: 345D72B
name: PBU_USRP_2901
product: B210
type: b200

--------------------------------------------------
-- UHD Device 2
--------------------------------------------------
Device Address:
serial: 352F061
name: B206i
product: B206mini
type: b200

</pre>

*View firewall settings with:
sudo iptables -L

==UHD Programs==
The example programs included with the UHD driver will be located at:
$install_prefix/lib/uhd/examples

On Linux, the default installation prefix location is <code>/usr/local</code>.

The example programs are located in the folder:
/usr/local/lib/uhd/examples

On OSX, the configuration is similar to Linux, however the default installation prefix location is <code>/opt/local</code>.

The example programs will be located in the folder:
/opt/local/lib/uhd/examples

On Windows, the default installation prefix will be <code>C:\Program Files\UHD\</code>.

The example programs will be located in the folder:
C:\Program Files\UHD\lib\uhd\examples

Before executing the following commands, change directory to the appropriate location.

==Benchmarking your system==
*Benchmarks interface with device.
./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --args "type=x300"

Example output from <code>benmark_rate</code>:

<pre>
ettus-24-02@ettus-24-02-Dell-Pro-16-PC16255:/usr/local/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --args "type=x300"

[INFO] [UHD] linux; GNU C++ version 13.3.0; Boost_108300; UHD_4.9.0.HEAD-0-g006d7f76
[00:00:00.000330] Creating the usrp device with: type=x300...
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum frame size: 1472 bytes.
[INFO] [X300] Radio 1x clock: 200 MHz
Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: UBX RX
RX Channel: 1
RX DSP: 1
RX Dboard: B
RX Subdev: CBX-120 RX
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: UBX TX
TX Channel: 1
TX DSP: 1
TX Dboard: B
TX Subdev: CBX-120 TX

[00:00:02.315579022] Setting device timestamp to 0...
Setting TX samples per packet (spp) to 364
Setting TX samples per burst (spb) to 364
[00:00:02.318249157] Testing receive rate 10.000000 Msps on 1 channels
[00:00:02.320136063] Testing transmit rate 10.000000 Msps on 1 channels
[00:00:12.332582703] Benchmark complete.

Benchmark rate summary:
Num received samples: 99999647
Num dropped samples: 0
Num overruns detected: 0
Num transmitted samples: 100113832
Num sequence errors (Tx): 0
Num sequence errors (Rx): 0
Num underruns detected: 0
Num late commands: 0
Num timeouts (Tx): 0
Num timeouts (Rx): 0

Done!

</pre>

==Receiving Samples==
*Saves samples to file
./rx_samples_to_file --freq 98e6 --rate 5e6 --gain 20 --duration 10 usrp_samples.dat

Example output from <code>rx_samples_to_file</code>:

<pre>
ettus-24-02@ettus-24-02-Dell-Pro-16-PC16255:/usr/local/lib/uhd/examples$ sudo ./rx_samples_to_file --freq 98e6 --rate 5e6 --gain 20 --duration 10 --args "type=x300" usrp_samples.dat
[sudo] password for ettus-24-02:

Creating the usrp device with: type=x300...
[INFO] [UHD] linux; GNU C++ version 13.3.0; Boost_108300; UHD_4.9.0.HEAD-0-g006d7f76
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum frame size: 1472 bytes.
[INFO] [X300] Radio 1x clock: 200 MHz
Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: UBX RX
RX Channel: 1
RX DSP: 1
RX Dboard: B
RX Subdev: CBX-120 RX
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: UBX TX
TX Channel: 1
TX DSP: 1
TX Dboard: B
TX Subdev: CBX-120 TX

Setting RX Rate: 5.000000 Msps...
Actual RX Rate: 5.000000 Msps...

Setting RX Freq: 98.000000 MHz...
Setting RX LO Offset: 0.000000 MHz...
Actual RX Freq: 98.000000 MHz...

Setting RX Gain: 20.000000 dB...
Actual RX Gain: 20.000000 dB...

Locking LO on channel 0
Waiting for "lo_locked": ++++++++++ locked.

Press Ctrl + C to stop streaming...

Done!

ettus-24-02@ettus-24-02-Dell-Pro-16-PC16255:/usr/local/lib/uhd/examples$ sudo ./rx_samples_to_file --freq 98e6 --rate 5e6 --gain 20 --duration 10 --args "type=b200,product=B206mini" usrp_samples.dat

Creating the usrp device with: type=b200,product=B206mini...
[INFO] [UHD] linux; GNU C++ version 13.3.0; Boost_108300; UHD_4.9.0.HEAD-0-g006d7f76
[INFO] [B200] Detected Device: B206mini
[INFO] [B200] Operating over USB 3.
[INFO] [B200] Initialize CODEC control...
[INFO] [B200] Initialize Radio control...
[INFO] [B200] Performing register loopback test...
[INFO] [B200] Register loopback test passed
[INFO] [B200] Setting master clock rate selection to 'automatic'.
[INFO] [B200] Asking for clock rate 16.000000 MHz...
[INFO] [B200] Actually got clock rate 16.000000 MHz.
Using Device: Single USRP:
Device: B-Series Device
Mboard 0: B206mini
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: FE-RX1
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: FE-TX1

Setting RX Rate: 5.000000 Msps...
[INFO] [B200] Asking for clock rate 40.000000 MHz...
[INFO] [B200] Actually got clock rate 40.000000 MHz.
Actual RX Rate: 5.000000 Msps...

Setting RX Freq: 98.000000 MHz...
Setting RX LO Offset: 0.000000 MHz...
Actual RX Freq: 98.000000 MHz...

Setting RX Gain: 20.000000 dB...
Actual RX Gain: 20.000000 dB...

Locking LO on channel 0
Waiting for "lo_locked": ++++++++++ locked.

Press Ctrl + C to stop streaming...

Done!
</pre>

Example of file size output from <code>rx_samples_to_file</code>:

<pre>
ettus-24-02@ettus-24-02-Dell-Pro-16-PC16255:/usr/local/lib/uhd/examples$ ls -al usrp_samples.dat
-rw-r--r-- 1 root root 200000000 Jun 16 23:53 usrp_samples.dat
</pre>

==Transmitting Samples==
*Transmits samples from file
./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 --args "type=x300" usrp_samples.dat

Example of output from <code>tx_samples_from_file</code>:

<pre>
ettus-24-02@ettus-24-02-Dell-Pro-16-PC16255:/usr/local/lib/uhd/examples$ ./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 --args "type=x300" usrp_samples.dat

Creating the usrp device with: type=x300...
[INFO] [UHD] linux; GNU C++ version 13.3.0; Boost_108300; UHD_4.9.0.HEAD-0-g006d7f76
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum frame size: 1472 bytes.
[INFO] [X300] Radio 1x clock: 200 MHz
Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: UBX RX
RX Channel: 1
RX DSP: 1
RX Dboard: B
RX Subdev: CBX-120 RX
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: UBX TX
TX Channel: 1
TX DSP: 1
TX Dboard: B
TX Subdev: CBX-120 TX

Setting TX Rate: 5.000000 Msps...
Actual TX Rate: 5.000000 Msps...

Setting TX Freq: 915.000000 MHz...
Setting TX LO Offset: 0.000000 MHz...
Actual TX Freq: 915.000000 MHz...

Setting TX Gain: 10.000000 dB...
Actual TX Gain: 10.000000 dB...

Checking TX: TXLO: locked ...
[WARNING] [0/Radio#0] Attempting to set tick rate to 0. Skipping.

Done!
</pre>

==Terminal DFT/FFT==
*Creates ASCII/Ncurses FFT
./rx_ascii_art_dft --freq 98e6 --rate 5e6 --gain 20 --bw 5e6 --args "type=x300" --ref-lvl -30

Example output from <code>rx_ascii_art_dft</code>:

<pre>
ettus-24-02@ettus-24-02-Dell-Pro-16-PC16255:/usr/local/lib/uhd/examples$ ./rx_ascii_art_dft --freq 98e6 --rate 5e6 --gain 20 --bw 5e6 --args "type=x300" --ref-lvl -30

Creating the usrp device with: type=x300...
[INFO] [UHD] linux; GNU C++ version 13.3.0; Boost_108300; UHD_4.9.0.HEAD-0-g006d7f76
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum frame size: 1472 bytes.
[INFO] [X300] Radio 1x clock: 200 MHz
Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: UBX RX
RX Channel: 1
RX DSP: 1
RX Dboard: B
RX Subdev: CBX-120 RX
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: UBX TX
TX Channel: 1
TX DSP: 1
TX Dboard: B
TX Subdev: CBX-120 TX

Setting RX Rate: 5.000000 Msps...
Actual RX Rate: 5.000000 Msps...

Setting RX Freq: 98.000000 MHz...
Actual RX Freq: 98.000000 MHz...

Setting RX Gain: 20.000000 dB...
Actual RX Gain: 20.000000 dB...

Setting RX Bandwidth: 5.000000 MHz...
Actual RX Bandwidth: 160.000000 MHz...

Checking RX: RXLO: locked ...
</pre>

Example screenshot of <code>rx_ascii_art_dft</code> running:

[[File:rx ascii art dft.png|900px]]

==Transmit test signal==
*Transmits specific waveform
./tx_waveforms --freq 915e6 --rate 5e6 --gain 0 --args "type=b200,product=B206mini"

Example output from <code>tx_waveforms</code>:

<pre>
ettus-24-02@ettus-24-02-Dell-Pro-16-PC16255:/usr/local/lib/uhd/examples$./tx_waveforms --freq 915e6 --rate 5e6 --gain 0 --args "type=b200,product=B206mini"

Creating the usrp device with: type=b200,product=B206mini...
[INFO] [UHD] linux; GNU C++ version 13.3.0; Boost_108300; UHD_4.9.0.HEAD-0-g006d7f76
[INFO] [B200] Detected Device: B206mini
[INFO] [B200] Operating over USB 3.
[INFO] [B200] Initialize CODEC control...
[INFO] [B200] Initialize Radio control...
[INFO] [B200] Performing register loopback test...
[INFO] [B200] Register loopback test passed
[INFO] [B200] Setting master clock rate selection to 'automatic'.
[INFO] [B200] Asking for clock rate 16.000000 MHz...
[INFO] [B200] Actually got clock rate 16.000000 MHz.
Using Device: Single USRP:
Device: B-Series Device
Mboard 0: B206mini
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: FE-RX1
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: FE-TX1

Setting TX Rate: 5.000000 Msps...
[INFO] [B200] Asking for clock rate 40.000000 MHz...
[INFO] [B200] Actually got clock rate 40.000000 MHz.
Actual TX Rate: 5.000000 Msps...

Setting TX Gain: 0.000000 dB...
Actual TX Gain: 0.000000 dB...

Setting device timestamp to 0...
Setting TX Freq: 915.000000 MHz...
Setting TX LO Offset: 0.000000 MHz...
Actual TX Freq: 915.000000 MHz...

Checking TX: LO: locked ...
Press Ctrl + C to stop streaming...
^C
Done!
</pre>

==USRP as Spectrum Analyzer using uhd_fft==

Receives signals and acts as a spectrum analyzer. The <code>uhd_fft</code> utility receives samples from a USRP, performs an FFT, and displays the power spectrum (frequency versus power).

You can find this utility under:

/usr/local/bin

[[File:uhd fft 1.jpg|900px]]

Example:

Go to the directory:

/usr/local/bin

Run the following command:

uhd_fft --args "addr=192.168.10.2" --freq 915e6 -s 20e6 -g 25

'''Note:''' We have generated a CW signal at 915 MHz using the <code>uhd_siggen_gui</code> example, which is discussed in the next section. This signal is received and displayed using <code>uhd_fft</code>.

[[File:uhd fft 2.jpg|900px]]

[[File:uhd fft 3.jpg|900px]]

==USRP as Signal Generator using uhd_siggen and uhd_siggen_gui==

<code>uhd_siggen</code> is a USRP signal generator utility provided by UHD (USRP Hardware Driver). It can generate test signals or continuous wave (CW) transmissions using any UHD-supported USRP device.

It provides a simple software-based RF signal generator without requiring a custom application or GNU Radio flowgraph.

Example:

Go to the directory:

/usr/local/bin

Run the following command:

uhd_siggen --args "type=b200" --freq 915e6 -g 40

[[File:uhd siggen 1.jpg|900px]]

The <code>uhd_siggen_gui</code> utility provides the same functionality as <code>uhd_siggen</code> but includes a graphical user interface that allows parameters to be adjusted dynamically during operation.

Example:

Go to the directory:

/usr/local/bin

Run the following command:

uhd_siggen_gui --args "type=b200" --freq 915e6 -g 40

[[File:uhd siggen 2.jpg|900px]]

==Additional UHD Utilities==

*Downloads FPGA images for the currently installed UHD version.

sudo uhd_images_downloader

Example output from <code>uhd_images_downloader</code>:

<pre>
$ [sudo] uhd_images_downloader

Images destination: /usr/local/share/uhd/images
Downloading images from: http://files.ettus.com/binaries/images/uhd-images_003.010.000.000-release.zip
Downloading images to: /tmp/tmpPYd_5J/uhd-images_003.010.000.000-release.zip
58959 kB / 58959 kB (100%)

Images successfully installed to: /usr/local/share/uhd/images
</pre>

[[Category:Application Notes]]

X300/X310 Device Recovery

2026-08-02T14:21:18Z

SiddhantDhawan:

==Application Note Information==
'''AN-305''' by Neel Pandeya, Michael Dickens and Siddhant Dhawan

==Overview==

This application note covers the process of recovering the USRP X300/X310 by flashing the FPGA image via the JTAG interface.

Note: This guide is written for Linux only. In theory it can be made to work on any OS that supports Xilinx Vivado.

==Manual==

For reference, please refer to the [https://files.ettus.com/manual/page_usrp_x3x0.html user manual page for the X300/X310].

==Required Tools==

* Host Computer
:- USB2/3 port
:- 1 GbE or 10 GbE network interface (NIC)
:- Supports Xilinx Vivado Lab installation
:- Supports UHD installation

* Connections from host to the X3x0 USRP via
:- USB2 cable
:- One of the following, depending on the host computer's NIC
:* SFP+ / RJ45 Adapter and Ethernet cable
:* SFP+ DAC cable

==Prerequisites==

This guide assumes you have a Linux-based host computer that supports Xilinx Vivado, with UHD installed into the default prefix <code>/usr/local</code>; for example we are using Ubuntu Linux and installed UHD from source using the default <code>CMAKE_INSTALL_PREFIX</code>. If you do not have UHD installed, please install it, for example via the [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on Linux]] Application Note.

We recommend using an X310 FPGA image provided by the host computer's UHD install, so that their versions match up. During runtime, UHD checks its version against that of all target USRPs' FPGA versions, and if they are too different then UHD prints a note about the mismatch and errors out.

There are circumstances where using different versions for the host UHD and FPGA image is necessary; performing this scenario is very similar to the steps in this guide, but requires some additional steps once the USRP is accessible via networking. We do not cover this scenario in this guide. If you need assistance under this scenario, please contact Ettus Support for assistance and we will provide you with the extra note steps.

If you do not have the FPGA images downloaded for your current host UHD install, you can obtain them by executing the command:

sudo uhd_images_downloader

Verify you have the FPGA images downloaded by running the command:

ls -alh /usr/local/share/uhd/images/usrp_x3*

[[File:1 x300 device recovery 2026.jpg|700px|center]]

==Installing Xilinx Vivado Lab Edition==

You will need to have an install of Xilinx Vivado Lab Edition, Xilinx Vivado Design Edition, or Xilinx Vivado System Edition. If you have none of those installed, then the minimum install is via Xilinx Vivado Lab Edition -- and that's what we cover in this guide. If you are using the Xilinx Vivado Design or System Edition then the paths may differ slightly from those described herein but the basic steps and process are the same; you can skip this section and go to the next one.

Xilinx Vivado Lab Edition can be downloaded from one the following links:

* [https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/vivado-design-tools.html current version]

* [https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/vivado-design-tools/archive.html legacy versions for older OSs]

===Steps to Install Vivado Lab Edition (License Free)===

After the download is complete, you can verify the MD5 sum of the file if you choose to do so, since Xilinx provides a MD5 SUM Value for each download:

cd ~/Downloads
md5sum Vivado_Lab_Lin_2025.2_1114_2157.tar

'''Note:''' The filename and MD5 hash may differ from the screen capture shown. Verify the MD5 sum against the hash listed on the Xilinx download page.

[[File:2 x300 device recovery 2026.jpg|700px|center]]

Next, decompress the downloaded tarball:

tar -xvf Vivado_Lab_Lin_2025.2_1114_2157.tar

This creates:

Vivado_Lab_Lin_2025.2_1114_2157/

[[File:3 x300 device recovery 2026.jpg|700px|center]]

Next, go into the new directory and run the <code>xsetup</code> installer using superuser <code>sudo</code> permissions:

cd Vivado_Lab_Lin_2025.2_1114_2157
sudo ./xsetup

The installer will then be at a Welcome screen, click Next.

[[File:4 x300 device recovery 2026.jpg|700px|center]]

Check the following Check Box and click <code>Next</code>.

[[File:5 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted to accept the various License Agreements, select all of the "I Agree" boxes then click <code>Next</code>.

[[File:6 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted with the installation locations. The default value for older Xilinx Vivado Lab is <code>/opt/Xilinx</code> while for newer versions it is <code>/tools/Xilinx</code>. We will be using the latter here; what you use is your choice, but please note the install directory so that you can make sure to use it correctly later in this guide.

If the install directory does not exist, you will be prompted immediately to create it. Click <code>Yes</code>.

[[File:7 x300 device recovery 2026.jpg|700px|center]]

Finally, you will be at the Installation Summary prompt. Click <code>Install</code>.

[[File:8 x300 device recovery 2026.jpg|700px|center]]

The installer has to download files from the internet, but they are not large and hence the installation process typically takes only a few minutes.

[[File:9 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted that the installation was successful. Click <code>Ok</code>, and the installer will close.

[[File:10 x300 device recovery 2026.jpg|700px|center]]

==Installing the Digilent Cable Driver==

In order to use the JTAG interface built into the USRP X300/X310 front panel, you will need to install the Digilent Cable Driver. It is included with the Xilinx Vivado Lab Edition package.

Navigate to the folder <code>/tools/Xilinx/2025.2/data/xicom/cable_drivers/lin64/install_script/install_drivers</code>, and run the installer script.

cd /tools/Xilinx/2025.2/data/xicom/cable_drivers/lin64/install_script/install_drivers

Verify contents in the directory:

ls

Expected Output:

install_digilent.sh
52-xilinx-digilent-usb.rules

[[File:11 x300 device recovery 2026.jpg|700px|center]]

Now run the installer script:

# The installer requires RDI_BINROOT to be set manually.

export RDI_BINROOT=$(pwd)
sudo -E ./install_digilent.sh

[[File:12 x300 device recovery 2026.jpg|700px|center]]

Next, reload the UDEV rules:

sudo udevadm control --reload
sudo udevadm trigger

[[File:13 x300 device recovery 2026.jpg|700px|center]]

Verify:

ls /etc/udev/rules.d | grep digilent

Expected Output:

52-xilinx-digilent-usb.rules

==Configuring Network Interface==

You will need to set your ethernet interface that will be connected to the USRP X300/X310 to a static IP address of <code>192.168.10.1</code> along with setting a MTU of <code>1500</code>.

Attach the SFP+/RJ45 adapter to Port 0 and connect your computer via ethernet.

{| style="width:100%;"
| style="width:50%; text-align:center;" |
[[File:14 x300 device recovery 2026.jpg|450px]]

| style="width:50%; text-align:center;" |
[[File:15 x300 device recovery 2026.jpg|450px]]
|}

==Prepare the X300/X310==

Connect the host computer where Xilinx Vivado was installed to the USRP X300/X310 via a USB2 cable. On the USRP X300/X310, plug the USB2 cable into the JTAG port on the front face plate. Once the USB cable is connected on both sides, power on the USRP X300/X310.

[[File:16 x300 device recovery 2026.jpg|700px|center]]

==Starting Xilinx Vivado Lab Edition==

Start by navigating back to your home directory:

cd ~/

Next, start Xilinx Vivado Lab via the command line:

/tools/Xilinx/2025.2/Vivado_Lab/bin/vivado_lab

You can also add Vivado Lab to the path so that you can open it from any directory:

echo 'source /tools/Xilinx/2025.2/Vivado_Lab/settings64.sh' >> ~/.bashrc
source ~/.bashrc

[[File:17 x300 device recovery 2026.jpg|700px|center]]

Now, go to any directory (for example <code>cd ~/</code>) and run:

vivado_lab

This will bring up the main Vivado Lab window.

[[File:18 x300 device recovery 2026.jpg|700px|center]]

Open the Hardware Manager by selecting <code>Open Hardware Manager</code>.

[[File:19 x300 device recovery 2026.jpg|700px|center]]

Next, within the menu of the Hardware Manager select <code>Tools</code> -> <code>Auto Connect</code>.

[[File:20 x300 device recovery 2026.jpg|700px|center]]

The details of the FPGA should populate the window on the left side of the Hardware Manager. Right click on the FPGA listed, and select <code>Program Device</code>.

[[File:21 x300 device recovery 2026.jpg|700px|center]]

This will popup a new window. Click on the file selection button and navigate to the location of the UHD FPGA images, and select the correct FPGA image for your device (<code>/usr/local/share/uhd/images</code>).

'''Note:''' Select the correct FPGA image that matches your USRP (either <code>_x300</code> or <code>_x310</code>) with the <code>.bit</code> file extension. It is recommended to select the <code>_HG</code> FPGA image, which will initialize Port 0 as 1 GbE and Port 1 as 10 GbE. Advanced users operating with dual 10 GbE may select the <code>_XG</code> image, however you will need to adjust the instructions listed within this document to match the dual 10GbE configuration (IP Addresses, MTU settings, etc).

[[File:22 x300 device recovery 2026.jpg|700px|center]]

Next, click <code>Program</code>.

[[File:23 x300 device recovery 2026.jpg|700px|center]]

A progress bar will popup as the FPGA is programmed.

[[File:24 x300 device recovery 2026.jpg|700px|center]]

Once the programming is completed, close Vivado Lab.

'''Note:''' If Vivado is actively attached to the USRP (<code>auto-connect</code> is enabled for the specific target), then at USRP power cycle Vivado ''will stop'' the USRP from auto-loading whatever FPGA image is stored on it.

[[File:25 x300 device recovery 2026.jpg|700px|center]]

'''Note:''' Do NOT power-cycle the device at this stage since it’s the temporary image. Flashing the FPGA image via JTAG only does not write the FPGA image to EEPROM, you must run the <code>uhd_image_loader</code> to write the FPGA image to the internal EEPROM.

Now, remove the JTAG cable from X310 and try to ping X310 using the command:

ping 192.168.10.2

(It should work if IP configuration step is performed correctly.)

At this point, if you're able to ping the USRP X300/X310, attempt to run the UHD utility <code>uhd_usrp_probe</code>.

uhd_usrp_probe

Example output from <code>uhd_usrp_probe</code>:

[[File:26 x300 device recovery 2026.jpg|700px|center]]

If running <code>uhd_usrp_probe</code> is successful, proceed with flashing the FPGA image with the UHD utility <code>uhd_image_loader</code>.

'''Note:''' Flashing the FPGA image via JTAG only does not write the FPGA image to EEPROM, you must run the <code>uhd_image_loader</code> to write the FPGA image to the internal EEPROM.

uhd_image_loader --args "type=x300,addr=192.168.10.2,fpga=HG"

When <code>uhd_image_loader</code> has completed the flashing process, it will recommend to power cycle the USRP X300/X310.

[[File:27 x300 device recovery 2026.jpg|700px|center]]

Power off the USRP X300/X310, and then power on the USRP X300/X310.

The USRP X300/X310 is now recovered. You should be able to <code>ping</code>, run <code>uhd_usrp_probe</code> and any other UHD utility/application as normal.

[[File:26 x300 device recovery 2026.jpg|700px|center]]

[[Category:Application Notes]]

Verifying the Operation of the USRP Using UHD and GNU Radio

2026-06-16T18:36:41Z

SiddhantDhawan:

Verifying the Operation of the USRP Using UHD and GNU Radio

2026-06-16T18:11:10Z

SiddhantDhawan:

==Application Note Information==
'''AN-936'''

==Authors==
Neel Pandeya and Siddhant Dhawan

==Abstract==
This AN explains how to use UHD and GNU Radio, once installed, to verify the correct operation of the USRP. Several test procedures are explained in detail. Several tests make use of an optional spectrum analyzer and signal generator.

==Overview==
This application note will cover testing your USRP to verify it is operational. You will need to have a working installation of UHD to preform the following steps to verify your USRP. If you do not have UHD installed, please reference the Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on Linux|Linux]], [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on OS X|OS X]] and [[Building and Installing the USRP Open Source Toolchain (UHD and GNU Radio) on Windows|Windows]] Application Notes.

Alternatively, you may use the [[Live SDR Environment]] to perform the following steps. More information about the [[Live SDR Environment]] is available at the [[Live SDR Environment Getting Started Guides]] page.

==Proper Care and Handling==
All Ettus Research products are individually tested before shipment. The USRP™ is guaranteed to be functional at the time it is received by the customer. Improper use or handling of the USRP™ can easily cause the device to become non-functional. Listed below are some examples of actions which can prevent damage to the unit:

*Never allow metal objects to touch the circuit board while powered.
*Always properly terminate the transmit port with an antenna or 50Ω load.
*Always handle the board with proper anti-static methods.
*Never allow the board to directly or indirectly come into contact with any voltage spikes.
*Never allow any water, or condensing moisture, to come into contact with the boards.
*Always use caution with FPGA, firmware, or software modifications.
{|
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |[[File:Caution.png|24px|center]]
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |Never apply more than -15 dBm of power into any RF input
|-
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |[[File:Caution.png|24px|center]]
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |Always use at least 30dB attenuation if operating in loopback configuration
|-
|}

==Finding the Device==
*Report detailed information on UHD-supported Software Radio Peripherals attached by USB, network, or embedded configuration. Details include unit names, revision numbers, and available sensors on all attached USRP motherboards and daughterboards.
uhd_usrp_probe

Example output from <code>uhd_usrp_probe</code>:

<pre>
$ uhd_usrp_probe
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
_____________________________________________________
/
| Device: USRP2 / N-Series Device
| _____________________________________________________
| /
| | Mboard: N210r4
| | hardware: 2577
| | mac-addr: 00:00:00:00:00:00
| | ip-addr: 192.168.10.2
| | subnet: 255.255.255.255
| | gateway: 255.255.255.255
| | gpsdo: none
| | serial: xxxxxx
| | FW Version: 12.4
| | FPGA Version: 11.1
| |
| | Time sources: none, external, _external_, mimo
| | Clock sources: internal, external, mimo
| | Sensors: mimo_locked, ref_locked
| | _____________________________________________________
| | /
| | | RX DSP: 0
| | |
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | RX DSP: 1
| | |
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | RX Dboard: A
| | | ID: WBX, WBX + Simple GDB (0x0053)
| | | Serial: xxxxxx
| | | _____________________________________________________
| | | /
| | | | RX Frontend: 0
| | | | Name: WBXv2 RX+GDB
| | | | Antennas: TX/RX, RX2, CAL
| | | | Sensors: lo_locked
| | | | Freq range: 68.750 to 2200.000 MHz
| | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB
| | | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | RX Codec: A
| | | | Name: ads62p44
| | | | Gain range digital: 0.0 to 6.0 step 0.5 dB
| | | | Gain range fine: 0.0 to 0.5 step 0.1 dB
| | _____________________________________________________
| | /
| | | TX DSP: 0
| | |
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | TX Dboard: A
| | | ID: WBX (0x0052)
| | | Serial: xxxxxx
| | | _____________________________________________________
| | | /
| | | | TX Frontend: 0
| | | | Name: WBXv2 TX+GDB
| | | | Antennas: TX/RX, CAL
| | | | Sensors: lo_locked
| | | | Freq range: 68.750 to 2200.000 MHz
| | | | Gain range PGA0: 0.0 to 25.0 step 0.1 dB
| | | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | TX Codec: A
| | | | Name: ad9777
| | | | Gain Elements: None

</pre>

*Find UHD-supporting Software Radio Peripherals attached by USB, network or embedded configuration. Uses broadcast packets for discovery. Often blocked by routers, switches, firewalls.
uhd_find_devices

Example output from <code>uhd_find_devices</code>:

<pre>
$ uhd_find_devices
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
type: usrp2
addr: 192.168.10.2
name:
serial: xxxxxx
</pre>

*View firewall settings with:
sudo iptables -L

==UHD Programs==
The example programs included with the UHD driver will be located at:
$install_prefix/lib/uhd/examples

On Linux, the default installation prefix location is <code>/usr/local</code>.

The example programs are located in the folder:
/usr/local/lib/uhd/examples

On OSX, the configuration is similar to Linux, however the default installation prefix location is <code>/opt/local</code>.

The example programs will be located in the folder:
/opt/local/lib/uhd/examples

On Windows, the default installation prefix will be <code>C:\Program Files\UHD\</code>.

The example programs will be located in the folder:
C:\Program Files\UHD\lib\uhd\examples

Before executing the following commands, change directory to the appropriate location.

==Benchmarking your system==
*Benchmarks interface with device.
./benchmark_rate --rx_rate 10e6 --tx_rate 10e6

Example output from <code>benmark_rate</code>:

<pre>
$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting device timestamp to 0...
Testing receive rate 10.000000 Msps on 1 channels
Testing transmit rate 10.000000 Msps on 1 channels

Benchmark rate summary:
Num received samples: 100104043
Num dropped samples: 0
Num overflows detected: 0
Num transmitted samples: 100229019
Num sequence errors: 0
Num underflows detected: 0
Num late commands: 0
Num timeouts: 0

Done!

</pre>

==Receiving Samples==
*Saves samples to file
./rx_samples_to_file --freq 98e6 --rate 5e6 --gain 20 --duration 10 usrp_samples.dat

Example output from <code>rx_samples_to_file</code>:

<pre>
$ ./rx_samples_to_file --freq 98e6 --rate 5e6 --gain 20 --duration 10 usrp_samples.dat
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting RX Rate: 5.000000 Msps...
Actual RX Rate: 5.000000 Msps...

Setting RX Freq: 98.000000 MHz...
Actual RX Freq: 98.000000 MHz...

Setting RX Gain: 20.000000 dB...
Actual RX Gain: 20.000000 dB...

Waiting for "lo_locked": ++++++++++ locked.

Press Ctrl + C to stop streaming...

Done!
</pre>

Example of file size output from <code>rx_samples_to_file</code>:

<pre>
$ ls -al usrp_samples.dat
-rw-rw-r-- 1 user user 200040000 Sep 1 14:43 usrp_samples.dat
</pre>

==Transmitting Samples==
*Transmits samples from file
./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat

Example of output from <code>tx_samples_from_file</code>:

<pre>
$ ./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting TX Rate: 5.000000 Msps...
Actual TX Rate: 5.000000 Msps...

Setting TX Freq: 915.000000 MHz...
Actual TX Freq: 915.000000 MHz...

Setting TX Gain: 10.000000 dB...
Actual TX Gain: 10.000000 dB...

Checking TX: LO: locked ...

Done!
</pre>

==Terminal DFT/FFT==
*Creates ASCII/Ncurses FFT
./rx_ascii_art_dft --freq 98e6 --rate 5e6 --gain 20 --bw 5e6 --ref-lvl -30

Example output from <code>rx_ascii_art_dft</code>:

<pre>
$ ./rx_ascii_art_dft --freq 98e6 --rate 5e6 --gain 20 --bw 5e6 --ref-lvl -30
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting RX Rate: 5.000000 Msps...
Actual RX Rate: 5.000000 Msps...

Setting RX Freq: 98.000000 MHz...
Actual RX Freq: 98.000000 MHz...

Setting RX Gain: 20.000000 dB...
Actual RX Gain: 20.000000 dB...

Setting RX Bandwidth: 5.000000 MHz...
Actual RX Bandwidth: 5.000000 MHz...

Checking RX: LO: locked ...
</pre>

Example screenshot of <code>rx_ascii_art_dft</code> running:

[[File:rx ascii art dft.png|900px]]

==Transmit test signal==
*Transmits specific waveform
./tx_waveforms --freq 915e6 --rate 5e6 --gain 0

Example output from <code>tx_waveforms</code>:

<pre>
$ ./tx_waveforms --freq 915e6 --rate 5e6 --gain 0
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting TX Rate: 5.000000 Msps...
Actual TX Rate: 5.000000 Msps...

Setting TX Freq: 915.000000 MHz...
Actual TX Freq: 915.000000 MHz...

Setting TX Gain: 0.000000 dB...
Actual TX Gain: 0.000000 dB...

Setting device timestamp to 0...
Checking TX: LO: locked ...
Press Ctrl + C to stop streaming...
^C
Done!
</pre>

==USRP as Spectrum Analyzer using uhd_fft==

Receives signals and acts as a spectrum analyzer. The <code>uhd_fft</code> utility receives samples from a USRP, performs an FFT, and displays the power spectrum (frequency versus power).

You can find this utility under:

/usr/local/bin

[[File:uhd fft 1.jpg|900px]]

Example:

Go to the directory:

/usr/local/bin

Run the following command:

uhd_fft --args "addr=192.168.10.2" --freq 915e6 -s 20e6 -g 25

'''Note:''' We have generated a CW signal at 915 MHz using the <code>uhd_siggen_gui</code> example, which is discussed in the next section. This signal is received and displayed using <code>uhd_fft</code>.

[[File:uhd fft 2.jpg|900px]]

[[File:uhd fft 3.jpg|900px]]

==USRP as Signal Generator using uhd_siggen and uhd_siggen_gui==

<code>uhd_siggen</code> is a USRP signal generator utility provided by UHD (USRP Hardware Driver). It can generate test signals or continuous wave (CW) transmissions using any UHD-supported USRP device.

It provides a simple software-based RF signal generator without requiring a custom application or GNU Radio flowgraph.

Example:

Go to the directory:

/usr/local/bin

Run the following command:

uhd_siggen --args "type=b200" --freq 915e6 -g 40

[[File:uhd siggen 1.jpg|900px]]

The <code>uhd_siggen_gui</code> utility provides the same functionality as <code>uhd_siggen</code> but includes a graphical user interface that allows parameters to be adjusted dynamically during operation.

Example:

Go to the directory:

/usr/local/bin

Run the following command:

uhd_siggen_gui --args "type=b200" --freq 915e6 -g 40

[[File:uhd siggen 2.jpg|900px]]

==Additional UHD Utilities==

*Downloads FPGA images for the currently installed UHD version.

sudo uhd_images_downloader

Example output from <code>uhd_images_downloader</code>:

<pre>
$ [sudo] uhd_images_downloader

Images destination: /usr/local/share/uhd/images
Downloading images from: http://files.ettus.com/binaries/images/uhd-images_003.010.000.000-release.zip
Downloading images to: /tmp/tmpPYd_5J/uhd-images_003.010.000.000-release.zip
58959 kB / 58959 kB (100%)

Images successfully installed to: /usr/local/share/uhd/images
</pre>

*Flashes an image onto the X300/X310 FPGA.

usrp_x3xx_fpga_burner

*Reads and writes motherboard EEPROM.

usrp_burn_mb_eeprom

*Reads and writes daughterboard EEPROM.

usrp_burn_db_eeprom

[[Category:Application Notes]]

Verifying the Operation of the USRP Using UHD and GNU Radio

2026-06-16T18:10:02Z

SiddhantDhawan:

==Application Note Information==
'''AN-936'''

==Authors==
Neel Pandeya and Siddhant Dhawan

==Abstract==
This AN explains how to use UHD and GNU Radio, once installed, to verify the correct operation of the USRP. Several test procedures are explained in detail. Several tests make use of an optional spectrum analyzer and signal generator.

==Overview==
This application note will cover testing your USRP to verify it is operational. You will need to have a working installation of UHD to preform the following steps to verify your USRP. If you do not have UHD installed, please reference the Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on Linux|Linux]], [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on OS X|OS X]] and [[Building and Installing the USRP Open Source Toolchain (UHD and GNU Radio) on Windows|Windows]] Application Notes.

Alternatively, you may use the [[Live SDR Environment]] to perform the following steps. More information about the [[Live SDR Environment]] is available at the [[Live SDR Environment Getting Started Guides]] page.

==Proper Care and Handling==
All Ettus Research products are individually tested before shipment. The USRP™ is guaranteed to be functional at the time it is received by the customer. Improper use or handling of the USRP™ can easily cause the device to become non-functional. Listed below are some examples of actions which can prevent damage to the unit:

*Never allow metal objects to touch the circuit board while powered.
*Always properly terminate the transmit port with an antenna or 50Ω load.
*Always handle the board with proper anti-static methods.
*Never allow the board to directly or indirectly come into contact with any voltage spikes.
*Never allow any water, or condensing moisture, to come into contact with the boards.
*Always use caution with FPGA, firmware, or software modifications.
{|
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |[[File:Caution.png|24px|center]]
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |Never apply more than -15 dBm of power into any RF input
|-
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |[[File:Caution.png|24px|center]]
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |Always use at least 30dB attenuation if operating in loopback configuration
|-
|}

==Finding the Device==
*Report detailed information on UHD-supported Software Radio Peripherals attached by USB, network, or embedded configuration. Details include unit names, revision numbers, and available sensors on all attached USRP motherboards and daughterboards.
uhd_usrp_probe

Example output from <code>uhd_usrp_probe</code>:

<pre>
$ uhd_usrp_probe
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
_____________________________________________________
/
| Device: USRP2 / N-Series Device
| _____________________________________________________
| /
| | Mboard: N210r4
| | hardware: 2577
| | mac-addr: 00:00:00:00:00:00
| | ip-addr: 192.168.10.2
| | subnet: 255.255.255.255
| | gateway: 255.255.255.255
| | gpsdo: none
| | serial: xxxxxx
| | FW Version: 12.4
| | FPGA Version: 11.1
| |
| | Time sources: none, external, _external_, mimo
| | Clock sources: internal, external, mimo
| | Sensors: mimo_locked, ref_locked
| | _____________________________________________________
| | /
| | | RX DSP: 0
| | |
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | RX DSP: 1
| | |
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | RX Dboard: A
| | | ID: WBX, WBX + Simple GDB (0x0053)
| | | Serial: xxxxxx
| | | _____________________________________________________
| | | /
| | | | RX Frontend: 0
| | | | Name: WBXv2 RX+GDB
| | | | Antennas: TX/RX, RX2, CAL
| | | | Sensors: lo_locked
| | | | Freq range: 68.750 to 2200.000 MHz
| | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB
| | | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | RX Codec: A
| | | | Name: ads62p44
| | | | Gain range digital: 0.0 to 6.0 step 0.5 dB
| | | | Gain range fine: 0.0 to 0.5 step 0.1 dB
| | _____________________________________________________
| | /
| | | TX DSP: 0
| | |
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | TX Dboard: A
| | | ID: WBX (0x0052)
| | | Serial: xxxxxx
| | | _____________________________________________________
| | | /
| | | | TX Frontend: 0
| | | | Name: WBXv2 TX+GDB
| | | | Antennas: TX/RX, CAL
| | | | Sensors: lo_locked
| | | | Freq range: 68.750 to 2200.000 MHz
| | | | Gain range PGA0: 0.0 to 25.0 step 0.1 dB
| | | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | TX Codec: A
| | | | Name: ad9777
| | | | Gain Elements: None

</pre>

*Find UHD-supporting Software Radio Peripherals attached by USB, network or embedded configuration. Uses broadcast packets for discovery. Often blocked by routers, switches, firewalls.
uhd_find_devices

Example output from <code>uhd_find_devices</code>:

<pre>
$ uhd_find_devices
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
type: usrp2
addr: 192.168.10.2
name:
serial: xxxxxx
</pre>

*View firewall settings with:
sudo iptables -L

==UHD Programs==
The example programs included with the UHD driver will be located at:
$install_prefix/lib/uhd/examples

On Linux, the default installation prefix location is <code>/usr/local</code>.

The example programs are located in the folder:
/usr/local/lib/uhd/examples

On OSX, the configuration is similar to Linux, however the default installation prefix location is <code>/opt/local</code>.

The example programs will be located in the folder:
/opt/local/lib/uhd/examples

On Windows, the default installation prefix will be <code>C:\Program Files\UHD\</code>.

The example programs will be located in the folder:
C:\Program Files\UHD\lib\uhd\examples

Before executing the following commands, change directory to the appropriate location.

==Benchmarking your system==
*Benchmarks interface with device.
./benchmark_rate --rx_rate 10e6 --tx_rate 10e6

Example output from <code>benmark_rate</code>:

<pre>
$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting device timestamp to 0...
Testing receive rate 10.000000 Msps on 1 channels
Testing transmit rate 10.000000 Msps on 1 channels

Benchmark rate summary:
Num received samples: 100104043
Num dropped samples: 0
Num overflows detected: 0
Num transmitted samples: 100229019
Num sequence errors: 0
Num underflows detected: 0
Num late commands: 0
Num timeouts: 0

Done!

</pre>

==Receiving Samples==
*Saves samples to file
./rx_samples_to_file --freq 98e6 --rate 5e6 --gain 20 --duration 10 usrp_samples.dat

Example output from <code>rx_samples_to_file</code>:

<pre>
$ ./rx_samples_to_file --freq 98e6 --rate 5e6 --gain 20 --duration 10 usrp_samples.dat
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting RX Rate: 5.000000 Msps...
Actual RX Rate: 5.000000 Msps...

Setting RX Freq: 98.000000 MHz...
Actual RX Freq: 98.000000 MHz...

Setting RX Gain: 20.000000 dB...
Actual RX Gain: 20.000000 dB...

Waiting for "lo_locked": ++++++++++ locked.

Press Ctrl + C to stop streaming...

Done!
</pre>

Example of file size output from <code>rx_samples_to_file</code>:

<pre>
$ ls -al usrp_samples.dat
-rw-rw-r-- 1 user user 200040000 Sep 1 14:43 usrp_samples.dat
</pre>

==Transmitting Samples==
*Transmits samples from file
./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat

Example of output from <code>tx_samples_from_file</code>:

<pre>
$ ./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting TX Rate: 5.000000 Msps...
Actual TX Rate: 5.000000 Msps...

Setting TX Freq: 915.000000 MHz...
Actual TX Freq: 915.000000 MHz...

Setting TX Gain: 10.000000 dB...
Actual TX Gain: 10.000000 dB...

Checking TX: LO: locked ...

Done!
</pre>

==Terminal DFT/FFT==
*Creates ASCII/Ncurses FFT
./rx_ascii_art_dft --freq 98e6 --rate 5e6 --gain 20 --bw 5e6 --ref-lvl -30

Example output from <code>rx_ascii_art_dft</code>:

<pre>
$ ./rx_ascii_art_dft --freq 98e6 --rate 5e6 --gain 20 --bw 5e6 --ref-lvl -30
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting RX Rate: 5.000000 Msps...
Actual RX Rate: 5.000000 Msps...

Setting RX Freq: 98.000000 MHz...
Actual RX Freq: 98.000000 MHz...

Setting RX Gain: 20.000000 dB...
Actual RX Gain: 20.000000 dB...

Setting RX Bandwidth: 5.000000 MHz...
Actual RX Bandwidth: 5.000000 MHz...

Checking RX: LO: locked ...
</pre>

Example screenshot of <code>rx_ascii_art_dft</code> running:

[[File:rx ascii art dft.png|900px]]

==Transmit test signal==
*Transmits specific waveform
./tx_waveforms --freq 915e6 --rate 5e6 --gain 0

Example output from <code>tx_waveforms</code>:

<pre>
$ ./tx_waveforms --freq 915e6 --rate 5e6 --gain 0
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting TX Rate: 5.000000 Msps...
Actual TX Rate: 5.000000 Msps...

Setting TX Freq: 915.000000 MHz...
Actual TX Freq: 915.000000 MHz...

Setting TX Gain: 0.000000 dB...
Actual TX Gain: 0.000000 dB...

Setting device timestamp to 0...
Checking TX: LO: locked ...
Press Ctrl + C to stop streaming...
^C
Done!
</pre>

==USRP as Spectrum Analyzer using uhd_fft==

Receives signals and acts as a spectrum analyzer. The <code>uhd_fft</code> utility receives samples from a USRP, performs an FFT, and displays the power spectrum (frequency versus power).

You can find this utility under:

/usr/local/bin

[[File:uhd fft 1.png|900px]]

Example:

Go to the directory:

/usr/local/bin

Run the following command:

uhd_fft --args "addr=192.168.10.2" --freq 915e6 -s 20e6 -g 25

'''Note:''' We have generated a CW signal at 915 MHz using the <code>uhd_siggen_gui</code> example, which is discussed in the next section. This signal is received and displayed using <code>uhd_fft</code>.

[[File:uhd fft 2.png|900px]]

[[File:uhd fft 3.png|900px]]

==USRP as Signal Generator using uhd_siggen and uhd_siggen_gui==

<code>uhd_siggen</code> is a USRP signal generator utility provided by UHD (USRP Hardware Driver). It can generate test signals or continuous wave (CW) transmissions using any UHD-supported USRP device.

It provides a simple software-based RF signal generator without requiring a custom application or GNU Radio flowgraph.

Example:

Go to the directory:

/usr/local/bin

Run the following command:

uhd_siggen --args "type=b200" --freq 915e6 -g 40

[[File:uhd siggen 1.png|900px]]

The <code>uhd_siggen_gui</code> utility provides the same functionality as <code>uhd_siggen</code> but includes a graphical user interface that allows parameters to be adjusted dynamically during operation.

Example:

Go to the directory:

/usr/local/bin

Run the following command:

uhd_siggen_gui --args "type=b200" --freq 915e6 -g 40

[[File:uhd siggen 2.png|900px]]

==Additional UHD Utilities==

*Downloads FPGA images for the currently installed UHD version.

sudo uhd_images_downloader

Example output from <code>uhd_images_downloader</code>:

<pre>
$ [sudo] uhd_images_downloader

Images destination: /usr/local/share/uhd/images
Downloading images from: http://files.ettus.com/binaries/images/uhd-images_003.010.000.000-release.zip
Downloading images to: /tmp/tmpPYd_5J/uhd-images_003.010.000.000-release.zip
58959 kB / 58959 kB (100%)

Images successfully installed to: /usr/local/share/uhd/images
</pre>

*Flashes an image onto the X300/X310 FPGA.

usrp_x3xx_fpga_burner

*Reads and writes motherboard EEPROM.

usrp_burn_mb_eeprom

*Reads and writes daughterboard EEPROM.

usrp_burn_db_eeprom

[[Category:Application Notes]]

File:uhd siggen 2.jpg

2026-06-16T18:08:17Z

SiddhantDhawan:

File:uhd siggen 1.jpg

2026-06-16T18:07:55Z

SiddhantDhawan:

File:uhd fft 3.jpg

2026-06-16T18:07:31Z

SiddhantDhawan:

File:uhd fft 2.jpg

2026-06-16T18:07:11Z

SiddhantDhawan:

File:uhd fft 1.jpg

2026-06-16T18:06:50Z

SiddhantDhawan:

Verifying the Operation of the USRP Using UHD and GNU Radio

2026-06-16T18:00:34Z

SiddhantDhawan: /* USRP as Spectrum Analyzer using uhd_fft */

==Application Note Information==
'''AN-936''' by Neel Pandeya


==Abstract==
This AN explains how to use UHD and GNU Radio, once installed, to verify the correct operation of the USRP. Several test procedures are explained in detail. Several tests make use of an optional spectrum analyzer and signal generator.

==Overview==
This application note will cover testing your USRP to verify it is operational. You will need to have a working installation of UHD to preform the following steps to verify your USRP. If you do not have UHD installed, please reference the Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on Linux|Linux]], [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on OS X|OS X]] and [[Building and Installing the USRP Open Source Toolchain (UHD and GNU Radio) on Windows|Windows]] Application Notes.

Alternatively, you may use the [[Live SDR Environment]] to perform the following steps. More information about the [[Live SDR Environment]] is available at the [[Live SDR Environment Getting Started Guides]] page.

==Proper Care and Handling==
All Ettus Research products are individually tested before shipment. The USRP™ is guaranteed to be functional at the time it is received by the customer. Improper use or handling of the USRP™ can easily cause the device to become non-functional. Listed below are some examples of actions which can prevent damage to the unit:

*Never allow metal objects to touch the circuit board while powered.
*Always properly terminate the transmit port with an antenna or 50Ω load.
*Always handle the board with proper anti-static methods.
*Never allow the board to directly or indirectly come into contact with any voltage spikes.
*Never allow any water, or condensing moisture, to come into contact with the boards.
*Always use caution with FPGA, firmware, or software modifications.
{|
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |[[File:Caution.png|24px|center]]
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |Never apply more than -15 dBm of power into any RF input
|-
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |[[File:Caution.png|24px|center]]
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |Always use at least 30dB attenuation if operating in loopback configuration
|-
|}

==Finding the Device==
*Report detailed information on UHD-supported Software Radio Peripherals attached by USB, network, or embedded configuration. Details include unit names, revision numbers, and available sensors on all attached USRP motherboards and daughterboards.
uhd_usrp_probe

Example output from <code>uhd_usrp_probe</code>:

<pre>
$ uhd_usrp_probe
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
_____________________________________________________
/
| Device: USRP2 / N-Series Device
| _____________________________________________________
| /
| | Mboard: N210r4
| | hardware: 2577
| | mac-addr: 00:00:00:00:00:00
| | ip-addr: 192.168.10.2
| | subnet: 255.255.255.255
| | gateway: 255.255.255.255
| | gpsdo: none
| | serial: xxxxxx
| | FW Version: 12.4
| | FPGA Version: 11.1
| |
| | Time sources: none, external, _external_, mimo
| | Clock sources: internal, external, mimo
| | Sensors: mimo_locked, ref_locked
| | _____________________________________________________
| | /
| | | RX DSP: 0
| | |
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | RX DSP: 1
| | |
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | RX Dboard: A
| | | ID: WBX, WBX + Simple GDB (0x0053)
| | | Serial: xxxxxx
| | | _____________________________________________________
| | | /
| | | | RX Frontend: 0
| | | | Name: WBXv2 RX+GDB
| | | | Antennas: TX/RX, RX2, CAL
| | | | Sensors: lo_locked
| | | | Freq range: 68.750 to 2200.000 MHz
| | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB
| | | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | RX Codec: A
| | | | Name: ads62p44
| | | | Gain range digital: 0.0 to 6.0 step 0.5 dB
| | | | Gain range fine: 0.0 to 0.5 step 0.1 dB
| | _____________________________________________________
| | /
| | | TX DSP: 0
| | |
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | TX Dboard: A
| | | ID: WBX (0x0052)
| | | Serial: xxxxxx
| | | _____________________________________________________
| | | /
| | | | TX Frontend: 0
| | | | Name: WBXv2 TX+GDB
| | | | Antennas: TX/RX, CAL
| | | | Sensors: lo_locked
| | | | Freq range: 68.750 to 2200.000 MHz
| | | | Gain range PGA0: 0.0 to 25.0 step 0.1 dB
| | | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | TX Codec: A
| | | | Name: ad9777
| | | | Gain Elements: None

</pre>

*Find UHD-supporting Software Radio Peripherals attached by USB, network or embedded configuration. Uses broadcast packets for discovery. Often blocked by routers, switches, firewalls.
uhd_find_devices

Example output from <code>uhd_find_devices</code>:

<pre>
$ uhd_find_devices
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
type: usrp2
addr: 192.168.10.2
name:
serial: xxxxxx
</pre>

*View firewall settings with:
sudo iptables -L

==UHD Programs==
The example programs included with the UHD driver will be located at:
$install_prefix/lib/uhd/examples

On Linux, the default installation prefix location is <code>/usr/local</code>.

The example programs are located in the folder:
/usr/local/lib/uhd/examples

On OSX, the configuration is similar to Linux, however the default installation prefix location is <code>/opt/local</code>.

The example programs will be located in the folder:
/opt/local/lib/uhd/examples

On Windows, the default installation prefix will be <code>C:\Program Files\UHD\</code>.

The example programs will be located in the folder:
C:\Program Files\UHD\lib\uhd\examples

Before executing the following commands, change directory to the appropriate location.

==Benchmarking your system==
*Benchmarks interface with device.
./benchmark_rate --rx_rate 10e6 --tx_rate 10e6

Example output from <code>benmark_rate</code>:

<pre>
$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting device timestamp to 0...
Testing receive rate 10.000000 Msps on 1 channels
Testing transmit rate 10.000000 Msps on 1 channels

Benchmark rate summary:
Num received samples: 100104043
Num dropped samples: 0
Num overflows detected: 0
Num transmitted samples: 100229019
Num sequence errors: 0
Num underflows detected: 0
Num late commands: 0
Num timeouts: 0

Done!

</pre>

==Receiving Samples==
*Saves samples to file
./rx_samples_to_file --freq 98e6 --rate 5e6 --gain 20 --duration 10 usrp_samples.dat

Example output from <code>rx_samples_to_file</code>:

<pre>
$ ./rx_samples_to_file --freq 98e6 --rate 5e6 --gain 20 --duration 10 usrp_samples.dat
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting RX Rate: 5.000000 Msps...
Actual RX Rate: 5.000000 Msps...

Setting RX Freq: 98.000000 MHz...
Actual RX Freq: 98.000000 MHz...

Setting RX Gain: 20.000000 dB...
Actual RX Gain: 20.000000 dB...

Waiting for "lo_locked": ++++++++++ locked.

Press Ctrl + C to stop streaming...

Done!
</pre>

Example of file size output from <code>rx_samples_to_file</code>:

<pre>
$ ls -al usrp_samples.dat
-rw-rw-r-- 1 user user 200040000 Sep 1 14:43 usrp_samples.dat
</pre>

==Transmitting Samples==
*Transmits samples from file
./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat

Example of output from <code>tx_samples_from_file</code>:

<pre>
$ ./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting TX Rate: 5.000000 Msps...
Actual TX Rate: 5.000000 Msps...

Setting TX Freq: 915.000000 MHz...
Actual TX Freq: 915.000000 MHz...

Setting TX Gain: 10.000000 dB...
Actual TX Gain: 10.000000 dB...

Checking TX: LO: locked ...

Done!
</pre>

==Terminal DFT/FFT==
*Creates ASCII/Ncurses FFT
./rx_ascii_art_dft --freq 98e6 --rate 5e6 --gain 20 --bw 5e6 --ref-lvl -30

Example output from <code>rx_ascii_art_dft</code>:

<pre>
$ ./rx_ascii_art_dft --freq 98e6 --rate 5e6 --gain 20 --bw 5e6 --ref-lvl -30
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting RX Rate: 5.000000 Msps...
Actual RX Rate: 5.000000 Msps...

Setting RX Freq: 98.000000 MHz...
Actual RX Freq: 98.000000 MHz...

Setting RX Gain: 20.000000 dB...
Actual RX Gain: 20.000000 dB...

Setting RX Bandwidth: 5.000000 MHz...
Actual RX Bandwidth: 5.000000 MHz...

Checking RX: LO: locked ...
</pre>

Example screenshot of <code>rx_ascii_art_dft</code> running:

[[File:rx ascii art dft.png|900px]]

==Transmit test signal==
*Transmits specific waveform
./tx_waveforms --freq 915e6 --rate 5e6 --gain 0

Example output from <code>tx_waveforms</code>:

<pre>
$ ./tx_waveforms --freq 915e6 --rate 5e6 --gain 0
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting TX Rate: 5.000000 Msps...
Actual TX Rate: 5.000000 Msps...

Setting TX Freq: 915.000000 MHz...
Actual TX Freq: 915.000000 MHz...

Setting TX Gain: 0.000000 dB...
Actual TX Gain: 0.000000 dB...

Setting device timestamp to 0...
Checking TX: LO: locked ...
Press Ctrl + C to stop streaming...
^C
Done!
</pre>

==USRP as Spectrum Analyzer using uhd_fft==

Receives signals and acts as a spectrum analyzer. The <code>uhd_fft</code> utility receives samples from a USRP, performs an FFT, and displays the power spectrum (frequency versus power).

You can find this utility under:

/usr/local/bin

[[File:uhd fft 1.png|900px]]

Example:

Go to the directory:

/usr/local/bin

Run the following command:

uhd_fft --args "addr=192.168.10.2" --freq 915e6 -s 20e6 -g 25

'''Note:''' We have generated a CW signal at 915 MHz using the <code>uhd_siggen_gui</code> example, which is discussed in the next section. This signal is received and displayed using <code>uhd_fft</code>.

[[File:uhd fft 2.png|900px]]

[[File:uhd fft 3.png|900px]]

==USRP as Signal Generator using uhd_siggen and uhd_siggen_gui==

<code>uhd_siggen</code> is a USRP signal generator utility provided by UHD (USRP Hardware Driver). It can generate test signals or continuous wave (CW) transmissions using any UHD-supported USRP device.

It provides a simple software-based RF signal generator without requiring a custom application or GNU Radio flowgraph.

Example:

Go to the directory:

/usr/local/bin

Run the following command:

uhd_siggen --args "type=b200" --freq 915e6 -g 40

[[File:uhd siggen 1.png|900px]]

The <code>uhd_siggen_gui</code> utility provides the same functionality as <code>uhd_siggen</code> but includes a graphical user interface that allows parameters to be adjusted dynamically during operation.

Example:

Go to the directory:

/usr/local/bin

Run the following command:

uhd_siggen_gui --args "type=b200" --freq 915e6 -g 40

[[File:uhd siggen 2.png|900px]]

==Additional UHD Utilities==

*Downloads FPGA images for the currently installed UHD version.

sudo uhd_images_downloader

Example output from <code>uhd_images_downloader</code>:

<pre>
$ [sudo] uhd_images_downloader

Images destination: /usr/local/share/uhd/images
Downloading images from: http://files.ettus.com/binaries/images/uhd-images_003.010.000.000-release.zip
Downloading images to: /tmp/tmpPYd_5J/uhd-images_003.010.000.000-release.zip
58959 kB / 58959 kB (100%)

Images successfully installed to: /usr/local/share/uhd/images
</pre>

*Flashes an image onto the X300/X310 FPGA.

usrp_x3xx_fpga_burner

*Reads and writes motherboard EEPROM.

usrp_burn_mb_eeprom

*Reads and writes daughterboard EEPROM.

usrp_burn_db_eeprom

[[Category:Application Notes]]

Verifying the Operation of the USRP Using UHD and GNU Radio

2026-06-16T17:57:46Z

SiddhantDhawan:

==Application Note Information==
'''AN-936''' by Neel Pandeya


==Abstract==
This AN explains how to use UHD and GNU Radio, once installed, to verify the correct operation of the USRP. Several test procedures are explained in detail. Several tests make use of an optional spectrum analyzer and signal generator.

==Overview==
This application note will cover testing your USRP to verify it is operational. You will need to have a working installation of UHD to preform the following steps to verify your USRP. If you do not have UHD installed, please reference the Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on Linux|Linux]], [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on OS X|OS X]] and [[Building and Installing the USRP Open Source Toolchain (UHD and GNU Radio) on Windows|Windows]] Application Notes.

Alternatively, you may use the [[Live SDR Environment]] to perform the following steps. More information about the [[Live SDR Environment]] is available at the [[Live SDR Environment Getting Started Guides]] page.

==Proper Care and Handling==
All Ettus Research products are individually tested before shipment. The USRP™ is guaranteed to be functional at the time it is received by the customer. Improper use or handling of the USRP™ can easily cause the device to become non-functional. Listed below are some examples of actions which can prevent damage to the unit:

*Never allow metal objects to touch the circuit board while powered.
*Always properly terminate the transmit port with an antenna or 50Ω load.
*Always handle the board with proper anti-static methods.
*Never allow the board to directly or indirectly come into contact with any voltage spikes.
*Never allow any water, or condensing moisture, to come into contact with the boards.
*Always use caution with FPGA, firmware, or software modifications.
{|
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |[[File:Caution.png|24px|center]]
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |Never apply more than -15 dBm of power into any RF input
|-
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |[[File:Caution.png|24px|center]]
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |Always use at least 30dB attenuation if operating in loopback configuration
|-
|}

==Finding the Device==
*Report detailed information on UHD-supported Software Radio Peripherals attached by USB, network, or embedded configuration. Details include unit names, revision numbers, and available sensors on all attached USRP motherboards and daughterboards.
uhd_usrp_probe

Example output from <code>uhd_usrp_probe</code>:

<pre>
$ uhd_usrp_probe
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
_____________________________________________________
/
| Device: USRP2 / N-Series Device
| _____________________________________________________
| /
| | Mboard: N210r4
| | hardware: 2577
| | mac-addr: 00:00:00:00:00:00
| | ip-addr: 192.168.10.2
| | subnet: 255.255.255.255
| | gateway: 255.255.255.255
| | gpsdo: none
| | serial: xxxxxx
| | FW Version: 12.4
| | FPGA Version: 11.1
| |
| | Time sources: none, external, _external_, mimo
| | Clock sources: internal, external, mimo
| | Sensors: mimo_locked, ref_locked
| | _____________________________________________________
| | /
| | | RX DSP: 0
| | |
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | RX DSP: 1
| | |
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | RX Dboard: A
| | | ID: WBX, WBX + Simple GDB (0x0053)
| | | Serial: xxxxxx
| | | _____________________________________________________
| | | /
| | | | RX Frontend: 0
| | | | Name: WBXv2 RX+GDB
| | | | Antennas: TX/RX, RX2, CAL
| | | | Sensors: lo_locked
| | | | Freq range: 68.750 to 2200.000 MHz
| | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB
| | | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | RX Codec: A
| | | | Name: ads62p44
| | | | Gain range digital: 0.0 to 6.0 step 0.5 dB
| | | | Gain range fine: 0.0 to 0.5 step 0.1 dB
| | _____________________________________________________
| | /
| | | TX DSP: 0
| | |
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | TX Dboard: A
| | | ID: WBX (0x0052)
| | | Serial: xxxxxx
| | | _____________________________________________________
| | | /
| | | | TX Frontend: 0
| | | | Name: WBXv2 TX+GDB
| | | | Antennas: TX/RX, CAL
| | | | Sensors: lo_locked
| | | | Freq range: 68.750 to 2200.000 MHz
| | | | Gain range PGA0: 0.0 to 25.0 step 0.1 dB
| | | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | TX Codec: A
| | | | Name: ad9777
| | | | Gain Elements: None

</pre>

*Find UHD-supporting Software Radio Peripherals attached by USB, network or embedded configuration. Uses broadcast packets for discovery. Often blocked by routers, switches, firewalls.
uhd_find_devices

Example output from <code>uhd_find_devices</code>:

<pre>
$ uhd_find_devices
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
type: usrp2
addr: 192.168.10.2
name:
serial: xxxxxx
</pre>

*View firewall settings with:
sudo iptables -L

==UHD Programs==
The example programs included with the UHD driver will be located at:
$install_prefix/lib/uhd/examples

On Linux, the default installation prefix location is <code>/usr/local</code>.

The example programs are located in the folder:
/usr/local/lib/uhd/examples

On OSX, the configuration is similar to Linux, however the default installation prefix location is <code>/opt/local</code>.

The example programs will be located in the folder:
/opt/local/lib/uhd/examples

On Windows, the default installation prefix will be <code>C:\Program Files\UHD\</code>.

The example programs will be located in the folder:
C:\Program Files\UHD\lib\uhd\examples

Before executing the following commands, change directory to the appropriate location.

==Benchmarking your system==
*Benchmarks interface with device.
./benchmark_rate --rx_rate 10e6 --tx_rate 10e6

Example output from <code>benmark_rate</code>:

<pre>
$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting device timestamp to 0...
Testing receive rate 10.000000 Msps on 1 channels
Testing transmit rate 10.000000 Msps on 1 channels

Benchmark rate summary:
Num received samples: 100104043
Num dropped samples: 0
Num overflows detected: 0
Num transmitted samples: 100229019
Num sequence errors: 0
Num underflows detected: 0
Num late commands: 0
Num timeouts: 0

Done!

</pre>

==Receiving Samples==
*Saves samples to file
./rx_samples_to_file --freq 98e6 --rate 5e6 --gain 20 --duration 10 usrp_samples.dat

Example output from <code>rx_samples_to_file</code>:

<pre>
$ ./rx_samples_to_file --freq 98e6 --rate 5e6 --gain 20 --duration 10 usrp_samples.dat
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting RX Rate: 5.000000 Msps...
Actual RX Rate: 5.000000 Msps...

Setting RX Freq: 98.000000 MHz...
Actual RX Freq: 98.000000 MHz...

Setting RX Gain: 20.000000 dB...
Actual RX Gain: 20.000000 dB...

Waiting for "lo_locked": ++++++++++ locked.

Press Ctrl + C to stop streaming...

Done!
</pre>

Example of file size output from <code>rx_samples_to_file</code>:

<pre>
$ ls -al usrp_samples.dat
-rw-rw-r-- 1 user user 200040000 Sep 1 14:43 usrp_samples.dat
</pre>

==Transmitting Samples==
*Transmits samples from file
./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat

Example of output from <code>tx_samples_from_file</code>:

<pre>
$ ./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting TX Rate: 5.000000 Msps...
Actual TX Rate: 5.000000 Msps...

Setting TX Freq: 915.000000 MHz...
Actual TX Freq: 915.000000 MHz...

Setting TX Gain: 10.000000 dB...
Actual TX Gain: 10.000000 dB...

Checking TX: LO: locked ...

Done!
</pre>

==Terminal DFT/FFT==
*Creates ASCII/Ncurses FFT
./rx_ascii_art_dft --freq 98e6 --rate 5e6 --gain 20 --bw 5e6 --ref-lvl -30

Example output from <code>rx_ascii_art_dft</code>:

<pre>
$ ./rx_ascii_art_dft --freq 98e6 --rate 5e6 --gain 20 --bw 5e6 --ref-lvl -30
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting RX Rate: 5.000000 Msps...
Actual RX Rate: 5.000000 Msps...

Setting RX Freq: 98.000000 MHz...
Actual RX Freq: 98.000000 MHz...

Setting RX Gain: 20.000000 dB...
Actual RX Gain: 20.000000 dB...

Setting RX Bandwidth: 5.000000 MHz...
Actual RX Bandwidth: 5.000000 MHz...

Checking RX: LO: locked ...
</pre>

Example screenshot of <code>rx_ascii_art_dft</code> running:

[[File:rx ascii art dft.png|900px]]

==Transmit test signal==
*Transmits specific waveform
./tx_waveforms --freq 915e6 --rate 5e6 --gain 0

Example output from <code>tx_waveforms</code>:

<pre>
$ ./tx_waveforms --freq 915e6 --rate 5e6 --gain 0
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting TX Rate: 5.000000 Msps...
Actual TX Rate: 5.000000 Msps...

Setting TX Freq: 915.000000 MHz...
Actual TX Freq: 915.000000 MHz...

Setting TX Gain: 0.000000 dB...
Actual TX Gain: 0.000000 dB...

Setting device timestamp to 0...
Checking TX: LO: locked ...
Press Ctrl + C to stop streaming...
^C
Done!
</pre>

==USRP as Spectrum Analyzer using uhd_fft==

Receives signals and acts as a spectrum analyzer. The <code>uhd_fft</code> utility receives samples from a USRP, performs an FFT, and displays the power spectrum (frequency versus power).

You can find this utility under:

/usr/local/bin

[[File:uhd fft 1.jpg|900px]]

Example:

Go to the directory:

/usr/local/bin

Run the following command:

uhd_fft --args "addr=192.168.10.2" --freq 915e6 -s 20e6 -g 25

'''Note:''' We have generated a CW signal at 915 MHz using the <code>uhd_siggen_gui</code> example, which is discussed in the next section. This signal is received and displayed using <code>uhd_fft</code>.

[[File:uhd fft 2.png|900px]]

[[File:uhd fft 3.png|900px]]

==USRP as Signal Generator using uhd_siggen and uhd_siggen_gui==

<code>uhd_siggen</code> is a USRP signal generator utility provided by UHD (USRP Hardware Driver). It can generate test signals or continuous wave (CW) transmissions using any UHD-supported USRP device.

It provides a simple software-based RF signal generator without requiring a custom application or GNU Radio flowgraph.

Example:

Go to the directory:

/usr/local/bin

Run the following command:

uhd_siggen --args "type=b200" --freq 915e6 -g 40

[[File:uhd siggen 1.png|900px]]

The <code>uhd_siggen_gui</code> utility provides the same functionality as <code>uhd_siggen</code> but includes a graphical user interface that allows parameters to be adjusted dynamically during operation.

Example:

Go to the directory:

/usr/local/bin

Run the following command:

uhd_siggen_gui --args "type=b200" --freq 915e6 -g 40

[[File:uhd siggen 2.png|900px]]

==Additional UHD Utilities==

*Downloads FPGA images for the currently installed UHD version.

sudo uhd_images_downloader

Example output from <code>uhd_images_downloader</code>:

<pre>
$ [sudo] uhd_images_downloader

Images destination: /usr/local/share/uhd/images
Downloading images from: http://files.ettus.com/binaries/images/uhd-images_003.010.000.000-release.zip
Downloading images to: /tmp/tmpPYd_5J/uhd-images_003.010.000.000-release.zip
58959 kB / 58959 kB (100%)

Images successfully installed to: /usr/local/share/uhd/images
</pre>

*Flashes an image onto the X300/X310 FPGA.

usrp_x3xx_fpga_burner

*Reads and writes motherboard EEPROM.

usrp_burn_mb_eeprom

*Reads and writes daughterboard EEPROM.

usrp_burn_db_eeprom

[[Category:Application Notes]]

Verifying the Operation of the USRP Using UHD and GNU Radio

2026-06-16T17:49:42Z

SiddhantDhawan:

==Application Note Number==
'''AN-936'''

==Authors==
Neel Pandeya and Siddhant Dhawan

==Abstract==
This AN explains how to use UHD and GNU Radio, once installed, to verify the correct operation of the USRP. Several test procedures are explained in detail. Several tests make use of an optional spectrum analyzer and signal generator.

==Overview==
This application note will cover testing your USRP to verify it is operational. You will need to have a working installation of UHD to perform the following steps to verify your USRP. If you do not have UHD installed, please reference the Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on Linux|Linux]], [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on OS X|OS X]] and [[Building and Installing the USRP Open Source Toolchain (UHD and GNU Radio) on Windows|Windows]] Application Notes.
Alternatively, you may use the [[Live SDR Environment]] to perform the following steps. More information about the [[Live SDR Environment]] is available at the [[Live SDR Environment Getting Started Guides]] page.

==Proper Care and Handling==
All Ettus Research products are individually tested before shipment. The USRP™ is guaranteed to be functional at the time it is received by the customer. Improper use or handling of the USRP™ can easily cause the device to become non-functional. Listed below are some examples of actions which can prevent damage to the unit:
• Never allow metal objects to touch the circuit board while powered.
• Always properly terminate the transmit port with an antenna or 50Ω load.
• Always handle the board with proper anti-static methods.
• Never allow the board to directly or indirectly come into contact with any voltage spikes.
• Never allow any water, or condensing moisture, to come into contact with the boards.
• Always use caution with FPGA, firmware, or software modifications.
{| |style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |[[File:Caution.png|24px|center]]
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |Never apply more than -15 dBm of power into any RF input |- |style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |[[File:Caution.png|24px|center]]
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |Always use at least 30dB attenuation if operating in loopback configuration |- |}

==Finding the Device==
• Report detailed information on UHD-supported Software Radio Peripherals attached by USB, network, or embedded configuration. Details include unit names, revision numbers, and available sensors on all attached USRP motherboards and daughterboards.
uhd_usrp_probe
Example output from uhd_usrp_probe:
$ uhd_usrp_probe
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
_____________________________________________________
/
| Device: USRP2 / N-Series Device
| _____________________________________________________
| /
| | Mboard: N210r4
| | hardware: 2577
| | mac-addr: 00:00:00:00:00:00
| | ip-addr: 192.168.10.2
| | subnet: 255.255.255.255
| | gateway: 255.255.255.255
| | gpsdo: none
| | serial: xxxxxx
| | FW Version: 12.4
| | FPGA Version: 11.1
| |
| | Time sources: none, external, _external_, mimo
| | Clock sources: internal, external, mimo
| | Sensors: mimo_locked, ref_locked
| | _____________________________________________________
| | /
| | | RX DSP: 0
| | |
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | RX DSP: 1
| | |
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | RX Dboard: A
| | | ID: WBX, WBX + Simple GDB (0x0053)
| | | Serial: xxxxxx
| | | _____________________________________________________
| | | /
| | | | RX Frontend: 0
| | | | Name: WBXv2 RX+GDB
| | | | Antennas: TX/RX, RX2, CAL
| | | | Sensors: lo_locked
| | | | Freq range: 68.750 to 2200.000 MHz
| | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB
| | | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | RX Codec: A
| | | | Name: ads62p44
| | | | Gain range digital: 0.0 to 6.0 step 0.5 dB
| | | | Gain range fine: 0.0 to 0.5 step 0.1 dB
| | _____________________________________________________
| | /
| | | TX DSP: 0
| | |
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | TX Dboard: A
| | | ID: WBX (0x0052)
| | | Serial: xxxxxx
| | | _____________________________________________________
| | | /
| | | | TX Frontend: 0
| | | | Name: WBXv2 TX+GDB
| | | | Antennas: TX/RX, CAL
| | | | Sensors: lo_locked
| | | | Freq range: 68.750 to 2200.000 MHz
| | | | Gain range PGA0: 0.0 to 25.0 step 0.1 dB
| | | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | TX Codec: A
| | | | Name: ad9777
| | | | Gain Elements: None

• Find UHD-supporting Software Radio Peripherals attached by USB, network or embedded configuration. Uses broadcast packets for discovery. Often blocked by routers, switches, firewalls.
uhd_find_devices
Example output from uhd_find_devices:
$ uhd_find_devices
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
type: usrp2
addr: 192.168.10.2
name:
serial: xxxxxx

• View firewall settings with:
sudo iptables -L

==UHD Programs==
The example programs included with the UHD driver will be located at:
$install_prefix/lib/uhd/examples

On Linux, the default installation prefix location is /usr/local.
The example programs are located in the folder:
/usr/local/lib/uhd/examples

On OSX, the configuration is similar to Linux, however the default installation prefix location is /opt/local.
The example programs will be located in the folder:
/opt/local/lib/uhd/examples

On Windows, the default installation prefix will be C:\Program Files\UHD</code>.
The example programs will be located in the folder:
C:\Program Files\UHD\lib\uhd\examples

Before executing the following commands, change directory to the appropriate location.

==Benchmarking your system==
• Benchmarks interface with device.
./benchmark_rate --rx_rate 10e6 --tx_rate 10e6
Example output from benchmark_rate:
$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting device timestamp to 0...
Testing receive rate 10.000000 Msps on 1 channels
Testing transmit rate 10.000000 Msps on 1 channels

Benchmark rate summary:
Num received samples: 100104043
Num dropped samples: 0
Num overflows detected: 0
Num transmitted samples: 100229019
Num sequence errors: 0
Num underflows detected: 0
Num late commands: 0
Num timeouts: 0

Done!

==Receiving Samples==
• Saves samples to file
./rx_samples_to_file --freq 98e6 --rate 5e6 --gain 20 --duration 10 usrp_samples.dat
Example output from rx_samples_to_file:
$ ./rx_samples_to_file --freq 98e6 --rate 5e6 --gain 20 --duration 10 usrp_samples.dat
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting RX Rate: 5.000000 Msps...
Actual RX Rate: 5.000000 Msps...

Setting RX Freq: 98.000000 MHz...
Actual RX Freq: 98.000000 MHz...

Setting RX Gain: 20.000000 dB...
Actual RX Gain: 20.000000 dB...

Waiting for "lo_locked": ++++++++++ locked.

Press Ctrl + C to stop streaming...

Done!

Example of file size output from rx_samples_to_file:
$ ls -al usrp_samples.dat
-rw-rw-r-- 1 user user 200040000 Sep 1 14:43 usrp_samples.dat

==Transmitting Samples==
• Transmits samples from file
./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat
Example output from tx_samples_from_file:
$ ./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting TX Rate: 5.000000 Msps...
Actual TX Rate: 5.000000 Msps...

Setting TX Freq: 915.000000 MHz...
Actual TX Freq: 915.000000 MHz...

Setting TX Gain: 10.000000 dB...
Actual TX Gain: 10.000000 dB...

Checking TX: LO: locked ...

Done!

==Terminal DFT/FFT==
• Creates ASCII/Ncurses FFT
./rx_ascii_art_dft --freq 98e6 --rate 5e6 --gain 20 --bw 5e6 --ref-lvl -30
Example output from rx_ascii_art_dft:
$ ./rx_ascii_art_dft --freq 98e6 --rate 5e6 --gain 20 --bw 5e6 --ref-lvl -30
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting RX Rate: 5.000000 Msps...
Actual RX Rate: 5.000000 Msps...

Setting RX Freq: 98.000000 MHz...
Actual RX Freq: 98.000000 MHz...

Setting RX Gain: 20.000000 dB...
Actual RX Gain: 20.000000 dB...

Setting RX Bandwidth: 5.000000 MHz...
Actual RX Bandwidth: 5.000000 MHz...

Checking RX: LO: locked ...

Example screenshot of rx_ascii_art_dft running:
[[File:rx ascii art dft.png|900px]]
==Transmit test signal==
• Transmits specific waveform
./tx_waveforms --freq 915e6 --rate 5e6 --gain 0
Example output from tx_waveforms:
$ ./tx_waveforms --freq 915e6 --rate 5e6 --gain 0
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting TX Rate: 5.000000 Msps...
Actual TX Rate: 5.000000 Msps...

Setting TX Freq: 915.000000 MHz...
Actual TX Freq: 915.000000 MHz...

Setting TX Gain: 0.000000 dB...
Actual TX Gain: 0.000000 dB...

Setting device timestamp to 0...
Checking TX: LO: locked ...
Press Ctrl + C to stop streaming...
^C
Done!

==USRP as Spectrum analyzer using uhd_fft==
Receives signal and acts as a spectrum analyzer. It is done using uhd_fft example. It receives samples from a USRP, performs an FFT, and displays the power spectrum (frequency vs power).
You can find this under:<code>/usr/local/bin</code>

[[File:uhd fft 1.jpg|900px]]

Example:
Go to directory:
/usr/local/bin

Run the following command:
uhd_fft --args "addr=192.168.10.2" --freq 915e6 -s 20e6 -g 25

Note: We have generated a CW signal at 915 MHz using uhd_siggen_gui example which will be discussed further in this document. This signal we are receiving using uhd_fft example.

[[File:uhd fft 2.png|900px]]

[[File:uhd fft 3.png|900px]]

==USRP as signal generator using uhd_siggen and uhd_siggen_gui==
uhd_siggen is a USRP signal generator utility provided by UHD (USRP Hardware Driver). Its purpose is to generate test signals or continuous wave (CW) transmissions through any UHD-supported USRP device.
It is essentially a software-based RF signal generator, allowing you to test or transmit signals without writing a full program in Python or GNU Radio.
Example:
Go to directory:
/usr/local/bin

Run command:
uhd_siggen --args "type=b200" --freq 915e6 -g 40

[[File:uhd siggen 1.png|900px]]

uhd_siggen_gui is similar to uhd_siggen with the only difference being that it provides a GUI where you can adjust the parameters dynamically instead of setting everything in command line.

Example:

Go to directory: <code>/usr/local/bin</code>

Run command: <code>uhd_siggen_gui --args "type=b200" --freq 915e6 -g 40</code>

[[File:uhd siggen 2.png|900px]]

==Additional UHD Utilities==
• Downloads FPGA images for current UHD version
sudo uhd_images_downloader
Example output from running uhd_images_downloader:
$ [sudo] uhd_images_downloader
Images destination: /usr/local/share/uhd/images
Downloading images from: http://files.ettus.com/binaries/images/uhd-images_003.010.000.000-release.zip
Downloading images to: /tmp/tmpPYd_5J/uhd-images_003.010.000.000-release.zip
58959 kB / 58959 kB (100%)

Images successfully installed to: /usr/local/share/uhd/images

• Flashes an image onto the X300/X310 FPGA
usrp_x3xx_fpga_burner
• Reading and writing motherboard EEPROM
usrp_burn_mb_eeprom
• Reading and writing daughterboard EEPROM
usrp_burn_db_eeprom
[[Category:Application Notes]]

File:uhd siggen 2.png

2026-06-16T17:43:30Z

SiddhantDhawan:

File:uhd siggen 1.png

2026-06-16T17:43:16Z

SiddhantDhawan:

File:uhd fft 3.png

2026-06-16T17:42:57Z

SiddhantDhawan:

File:uhd fft 2.png

2026-06-16T17:42:43Z

SiddhantDhawan:

File:uhd fft 1.png

2026-06-16T17:42:19Z

SiddhantDhawan:

Verifying the Operation of the USRP Using UHD and GNU Radio

2026-06-16T17:41:20Z

SiddhantDhawan:

==Application Note Information== '''AN-936''' by Neel Pandeya and Siddhant Dhawan
==Abstract== This AN explains how to use UHD and GNU Radio, once installed, to verify the correct operation of the USRP. Several test procedures are explained in detail. Several tests make use of an optional spectrum analyzer and signal generator.
==Overview== This application note will cover testing your USRP to verify it is operational. You will need to have a working installation of UHD to perform the following steps to verify your USRP. If you do not have UHD installed, please reference the Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on Linux|Linux]], [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on OS X|OS X]] and [[Building and Installing the USRP Open Source Toolchain (UHD and GNU Radio) on Windows|Windows]] Application Notes.
Alternatively, you may use the [[Live SDR Environment]] to perform the following steps. More information about the [[Live SDR Environment]] is available at the [[Live SDR Environment Getting Started Guides]] page.
==Proper Care and Handling== All Ettus Research products are individually tested before shipment. The USRP™ is guaranteed to be functional at the time it is received by the customer. Improper use or handling of the USRP™ can easily cause the device to become non-functional. Listed below are some examples of actions which can prevent damage to the unit:
• Never allow metal objects to touch the circuit board while powered.
• Always properly terminate the transmit port with an antenna or 50Ω load.
• Always handle the board with proper anti-static methods.
• Never allow the board to directly or indirectly come into contact with any voltage spikes.
• Never allow any water, or condensing moisture, to come into contact with the boards.
• Always use caution with FPGA, firmware, or software modifications.
{| |style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |[[File:Caution.png|24px|center]]
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |Never apply more than -15 dBm of power into any RF input |- |style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |[[File:Caution.png|24px|center]]
|style="padding-left:10px; padding-right:10px; padding-bottom:10px;" |Always use at least 30dB attenuation if operating in loopback configuration |- |}
==Finding the Device==
• Report detailed information on UHD-supported Software Radio Peripherals attached by USB, network, or embedded configuration. Details include unit names, revision numbers, and available sensors on all attached USRP motherboards and daughterboards.
uhd_usrp_probe
Example output from uhd_usrp_probe:
$ uhd_usrp_probe
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
_____________________________________________________
/
| Device: USRP2 / N-Series Device
| _____________________________________________________
| /
| | Mboard: N210r4
| | hardware: 2577
| | mac-addr: 00:00:00:00:00:00
| | ip-addr: 192.168.10.2
| | subnet: 255.255.255.255
| | gateway: 255.255.255.255
| | gpsdo: none
| | serial: xxxxxx
| | FW Version: 12.4
| | FPGA Version: 11.1
| |
| | Time sources: none, external, _external_, mimo
| | Clock sources: internal, external, mimo
| | Sensors: mimo_locked, ref_locked
| | _____________________________________________________
| | /
| | | RX DSP: 0
| | |
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | RX DSP: 1
| | |
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | RX Dboard: A
| | | ID: WBX, WBX + Simple GDB (0x0053)
| | | Serial: xxxxxx
| | | _____________________________________________________
| | | /
| | | | RX Frontend: 0
| | | | Name: WBXv2 RX+GDB
| | | | Antennas: TX/RX, RX2, CAL
| | | | Sensors: lo_locked
| | | | Freq range: 68.750 to 2200.000 MHz
| | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB
| | | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | RX Codec: A
| | | | Name: ads62p44
| | | | Gain range digital: 0.0 to 6.0 step 0.5 dB
| | | | Gain range fine: 0.0 to 0.5 step 0.1 dB
| | _____________________________________________________
| | /
| | | TX DSP: 0
| | |
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | TX Dboard: A
| | | ID: WBX (0x0052)
| | | Serial: xxxxxx
| | | _____________________________________________________
| | | /
| | | | TX Frontend: 0
| | | | Name: WBXv2 TX+GDB
| | | | Antennas: TX/RX, CAL
| | | | Sensors: lo_locked
| | | | Freq range: 68.750 to 2200.000 MHz
| | | | Gain range PGA0: 0.0 to 25.0 step 0.1 dB
| | | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | TX Codec: A
| | | | Name: ad9777
| | | | Gain Elements: None

• Find UHD-supporting Software Radio Peripherals attached by USB, network or embedded configuration. Uses broadcast packets for discovery. Often blocked by routers, switches, firewalls.
uhd_find_devices
Example output from uhd_find_devices:
$ uhd_find_devices
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
type: usrp2
addr: 192.168.10.2
name:
serial: xxxxxx

• View firewall settings with:
sudo iptables -L
==UHD Programs==
The example programs included with the UHD driver will be located at:
$install_prefix/lib/uhd/examples

On Linux, the default installation prefix location is /usr/local.
The example programs are located in the folder:
/usr/local/lib/uhd/examples

On OSX, the configuration is similar to Linux, however the default installation prefix location is /opt/local.
The example programs will be located in the folder:
/opt/local/lib/uhd/examples

On Windows, the default installation prefix will be C:\Program Files\UHD</code>.
The example programs will be located in the folder:
C:\Program Files\UHD\lib\uhd\examples

Before executing the following commands, change directory to the appropriate location.
==Benchmarking your system==
• Benchmarks interface with device.
./benchmark_rate --rx_rate 10e6 --tx_rate 10e6
Example output from benchmark_rate:
$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting device timestamp to 0...
Testing receive rate 10.000000 Msps on 1 channels
Testing transmit rate 10.000000 Msps on 1 channels

Benchmark rate summary:
Num received samples: 100104043
Num dropped samples: 0
Num overflows detected: 0
Num transmitted samples: 100229019
Num sequence errors: 0
Num underflows detected: 0
Num late commands: 0
Num timeouts: 0

Done!

==Receiving Samples==
• Saves samples to file
./rx_samples_to_file --freq 98e6 --rate 5e6 --gain 20 --duration 10 usrp_samples.dat
Example output from rx_samples_to_file:
$ ./rx_samples_to_file --freq 98e6 --rate 5e6 --gain 20 --duration 10 usrp_samples.dat
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting RX Rate: 5.000000 Msps...
Actual RX Rate: 5.000000 Msps...

Setting RX Freq: 98.000000 MHz...
Actual RX Freq: 98.000000 MHz...

Setting RX Gain: 20.000000 dB...
Actual RX Gain: 20.000000 dB...

Waiting for "lo_locked": ++++++++++ locked.

Press Ctrl + C to stop streaming...

Done!

Example of file size output from rx_samples_to_file:
$ ls -al usrp_samples.dat
-rw-rw-r-- 1 user user 200040000 Sep 1 14:43 usrp_samples.dat

==Transmitting Samples==
• Transmits samples from file
./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat
Example output from tx_samples_from_file:
$ ./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting TX Rate: 5.000000 Msps...
Actual TX Rate: 5.000000 Msps...

Setting TX Freq: 915.000000 MHz...
Actual TX Freq: 915.000000 MHz...

Setting TX Gain: 10.000000 dB...
Actual TX Gain: 10.000000 dB...

Checking TX: LO: locked ...

Done!

==Terminal DFT/FFT==
• Creates ASCII/Ncurses FFT
./rx_ascii_art_dft --freq 98e6 --rate 5e6 --gain 20 --bw 5e6 --ref-lvl -30
Example output from rx_ascii_art_dft:
$ ./rx_ascii_art_dft --freq 98e6 --rate 5e6 --gain 20 --bw 5e6 --ref-lvl -30
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting RX Rate: 5.000000 Msps...
Actual RX Rate: 5.000000 Msps...

Setting RX Freq: 98.000000 MHz...
Actual RX Freq: 98.000000 MHz...

Setting RX Gain: 20.000000 dB...
Actual RX Gain: 20.000000 dB...

Setting RX Bandwidth: 5.000000 MHz...
Actual RX Bandwidth: 5.000000 MHz...

Checking RX: LO: locked ...

Example screenshot of rx_ascii_art_dft running:
[[File:rx ascii art dft.png|900px]]
==Transmit test signal==
• Transmits specific waveform
./tx_waveforms --freq 915e6 --rate 5e6 --gain 0
Example output from tx_waveforms:
$ ./tx_waveforms --freq 915e6 --rate 5e6 --gain 0
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.000.HEAD-0-g6e1ac3fc

Creating the usrp device with: ...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N210r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv2 RX+GDB
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv2 TX+GDB

Setting TX Rate: 5.000000 Msps...
Actual TX Rate: 5.000000 Msps...

Setting TX Freq: 915.000000 MHz...
Actual TX Freq: 915.000000 MHz...

Setting TX Gain: 0.000000 dB...
Actual TX Gain: 0.000000 dB...

Setting device timestamp to 0...
Checking TX: LO: locked ...
Press Ctrl + C to stop streaming...
^C
Done!

==USRP as Spectrum analyzer using uhd_fft==
Receives signal and acts as a spectrum analyzer. It is done using uhd_fft example. It receives samples from a USRP, performs an FFT, and displays the power spectrum (frequency vs power).
You can find this under:<code>/usr/local/bin</code>

[[File:uhd fft 1.jpg|900px]]

Example:
Go to directory:
/usr/local/bin

Run the following command:
uhd_fft --args "addr=192.168.10.2" --freq 915e6 -s 20e6 -g 25

Note: We have generated a CW signal at 915 MHz using uhd_siggen_gui example which will be discussed further in this document. This signal we are receiving using uhd_fft example.

[[File:uhd fft 2.png|900px]]

[[File:uhd fft 3.png|900px]]

==USRP as signal generator using uhd_siggen and uhd_siggen_gui==
uhd_siggen is a USRP signal generator utility provided by UHD (USRP Hardware Driver). Its purpose is to generate test signals or continuous wave (CW) transmissions through any UHD-supported USRP device.
It is essentially a software-based RF signal generator, allowing you to test or transmit signals without writing a full program in Python or GNU Radio.
Example:
Go to directory:
/usr/local/bin

Run command:
uhd_siggen --args "type=b200" --freq 915e6 -g 40

[[File:uhd siggen 1.png|900px]]

uhd_siggen_gui is similar to uhd_siggen with the only difference being that it provides a GUI where you can adjust the parameters dynamically instead of setting everything in command line.

Example:

Go to directory: <code>/usr/local/bin</code>

Run command: <code>uhd_siggen_gui --args "type=b200" --freq 915e6 -g 40</code>

[[File:uhd siggen 2.png|900px]]

==Additional UHD Utilities==
• Downloads FPGA images for current UHD version
sudo uhd_images_downloader
Example output from running uhd_images_downloader:
$ [sudo] uhd_images_downloader
Images destination: /usr/local/share/uhd/images
Downloading images from: http://files.ettus.com/binaries/images/uhd-images_003.010.000.000-release.zip
Downloading images to: /tmp/tmpPYd_5J/uhd-images_003.010.000.000-release.zip
58959 kB / 58959 kB (100%)

Images successfully installed to: /usr/local/share/uhd/images

• Flashes an image onto the X300/X310 FPGA
usrp_x3xx_fpga_burner
• Reading and writing motherboard EEPROM
usrp_burn_mb_eeprom
• Reading and writing daughterboard EEPROM
usrp_burn_db_eeprom
[[Category:Application Notes]]

X300/X310 Device Recovery

2026-06-16T17:20:51Z

SiddhantDhawan: /* Configuring Network Interface */

==Application Note Information==
'''AN-305''' by Neel Pandeya, Michael Dickens and Siddhant Dhawan

==Overview==

This application note covers the process of recovering the USRP X300/X310 by flashing the FPGA image via the JTAG interface.

Note: This guide is written for Linux only. In theory it can be made to work on any OS that supports Xilinx Vivado.

==Manual==

For reference, please refer to the [https://files.ettus.com/manual/page_usrp_x3x0.html user manual page for the X300/X310].

==Required Tools==

* Host Computer
:- USB2/3 port
:- 1 GbE or 10 GbE network interface (NIC)
:- Supports Xilinx Vivado Lab installation
:- Supports UHD installation

* Connections from host to the X3x0 USRP via
:- USB2 cable
:- One of the following, depending on the host computer's NIC
:* SFP+ / RJ45 Adapter and Ethernet cable
:* SFP+ DAC cable

==Prerequisites==

This guide assumes you have a Linux-based host computer that supports Xilinx Vivado, with UHD installed into the default prefix <code>/usr/local</code>; for example we are using Ubuntu Linux and installed UHD from source using the default <code>CMAKE_INSTALL_PREFIX</code>. If you do not have UHD installed, please install it, for example via the [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on Linux]] Application Note.

We recommend using an X310 FPGA image provided by the host computer's UHD install, so that their versions match up. During runtime, UHD checks its version against that of all target USRPs' FPGA versions, and if they are too different then UHD prints a note about the mismatch and errors out.

There are circumstances where using different versions for the host UHD and FPGA image is necessary; performing this scenario is very similar to the steps in this guide, but requires some additional steps once the USRP is accessible via networking. We do not cover this scenario in this guide. If you need assistance under this scenario, please contact Ettus Support for assistance and we will provide you with the extra note steps.

If you do not have the FPGA images downloaded for your current host UHD install, you can obtain them by executing the command:

sudo uhd_images_downloader

Verify you have the FPGA images downloaded by running the command:

ls -alh /usr/local/share/uhd/images/usrp_x3*

[[File:1 x300 device recovery 2026.jpg|700px|center]]

==Installing Xilinx Vivado Lab Edition==

You will need to have an install of Xilinx Vivado Lab Edition, Xilinx Vivado Design Edition, or Xilinx Vivado System Edition. If you have none of those installed, then the minimum install is via Xilinx Vivado Lab Edition -- and that's what we cover in this guide. If you are using the Xilinx Vivado Design or System Edition then the paths may differ slightly from those described herein but the basic steps and process are the same; you can skip this section and go to the next one.

Xilinx Vivado Lab Edition can be downloaded from one the following links:

* [https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/vivado-design-tools.html current version]

* [https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/vivado-design-tools/archive.html legacy versions for older OSs]

===Steps to Install Vivado Lab Edition (License Free)===

After the download is complete, you can verify the MD5 sum of the file if you choose to do so, since Xilinx provides a MD5 SUM Value for each download:

cd ~/Downloads
md5sum Xilinx_Vivado_Lab_Lin_2015.4_1118_2.tar.gz

'''Note:''' The filename and MD5 hash may differ from the screen capture shown. Verify the MD5 sum against the hash listed on the Xilinx download page.

[[File:2 x300 device recovery 2026.jpg|700px|center]]

Next, decompress the downloaded tarball:

tar -xvf Vivado_Lab_Lin_2025.2_1114_2157.tar

This creates:

Vivado_Lab_Lin_2025.2_1114_2157/

[[File:3 x300 device recovery 2026.jpg|700px|center]]

Next, go into the new directory and run the <code>xsetup</code> installer using superuser <code>sudo</code> permissions:

cd Vivado_Lab_Lin_2025.2_1114_2157
sudo ./xsetup

The installer will then be at a Welcome screen, click Next.

[[File:4 x300 device recovery 2026.jpg|700px|center]]

Check the following Check Box and click <code>Next</code>.

[[File:5 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted to accept the various License Agreements, select all of the "I Agree" boxes then click <code>Next</code>.

[[File:6 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted with the installation locations. The default value for older Xilinx Vivado Lab is <code>/opt/Xilinx</code> while for newer versions it is <code>/tools/Xilinx</code>. We will be using the latter here; what you use is your choice, but please note the install directory so that you can make sure to use it correctly later in this guide.

If the install directory does not exist, you will be prompted immediately to create it. Click <code>Yes</code>.

[[File:7 x300 device recovery 2026.jpg|700px|center]]

Finally, you will be at the Installation Summary prompt. Click <code>Install</code>.

[[File:8 x300 device recovery 2026.jpg|700px|center]]

The installer has to download files from the internet, but they are not large and hence the installation process typically takes only a few minutes.

[[File:9 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted that the installation was successful. Click <code>Ok</code>, and the installer will close.

[[File:10 x300 device recovery 2026.jpg|700px|center]]

==Installing the Digilent Cable Driver==

In order to use the JTAG interface built into the USRP X300/X310 front panel, you will need to install the Digilent Cable Driver. It is included with the Xilinx Vivado Lab Edition package.

Navigate to the folder <code>/tools/Xilinx/2025.2/data/xicom/cable_drivers/lin64/install_script/install_drivers</code>, and run the installer script.

cd /tools/Xilinx/2025.2/data/xicom/cable_drivers/lin64/install_script/install_drivers

Verify contents in the directory:

ls

Expected Output:

install_digilent.sh
52-xilinx-digilent-usb.rules

[[File:11 x300 device recovery 2026.jpg|700px|center]]

Now run the installer script:

# The installer requires RDI_BINROOT to be set manually.

export RDI_BINROOT=$(pwd)
sudo -E ./install_digilent.sh

[[File:12 x300 device recovery 2026.jpg|700px|center]]

Next, reload the UDEV rules:

sudo udevadm control --reload
sudo udevadm trigger

[[File:13 x300 device recovery 2026.jpg|700px|center]]

Verify:

ls /etc/udev/rules.d | grep digilent

Expected Output:

52-xilinx-digilent-usb.rules

==Configuring Network Interface==

You will need to set your ethernet interface that will be connected to the USRP X300/X310 to a static IP address of <code>192.168.10.1</code> along with setting a MTU of <code>1500</code>.

Attach the SFP+/RJ45 adapter to Port 0 and connect your computer via ethernet.

{| style="width:100%;"
| style="width:50%; text-align:center;" |
[[File:14 x300 device recovery 2026.jpg|450px]]

| style="width:50%; text-align:center;" |
[[File:15 x300 device recovery 2026.jpg|450px]]
|}

==Prepare the X300/X310==

Connect the host computer where Xilinx Vivado was installed to the USRP X300/X310 via a USB2 cable. On the USRP X300/X310, plug the USB2 cable into the JTAG port on the front face plate. Once the USB cable is connected on both sides, power on the USRP X300/X310.

[[File:16 x300 device recovery 2026.jpg|700px|center]]

==Starting Xilinx Vivado Lab Edition==

Start by navigating back to your home directory:

cd ~/

Next, start Xilinx Vivado Lab via the command line:

/tools/Xilinx/2025.2/Vivado_Lab/bin/vivado_lab

You can also add Vivado Lab to the path so that you can open it from any directory:

echo 'source /tools/Xilinx/2025.2/Vivado_Lab/settings64.sh' >> ~/.bashrc
source ~/.bashrc

[[File:17 x300 device recovery 2026.jpg|700px|center]]

Now, go to any directory (for example <code>cd ~/</code>) and run:

vivado_lab

This will bring up the main Vivado Lab window.

[[File:18 x300 device recovery 2026.jpg|700px|center]]

Open the Hardware Manager by selecting <code>Open Hardware Manager</code>.

[[File:19 x300 device recovery 2026.jpg|700px|center]]

Next, within the menu of the Hardware Manager select <code>Tools</code> -> <code>Auto Connect</code>.

[[File:20 x300 device recovery 2026.jpg|700px|center]]

The details of the FPGA should populate the window on the left side of the Hardware Manager. Right click on the FPGA listed, and select <code>Program Device</code>.

[[File:21 x300 device recovery 2026.jpg|700px|center]]

This will popup a new window. Click on the file selection button and navigate to the location of the UHD FPGA images, and select the correct FPGA image for your device (<code>/usr/local/share/uhd/images</code>).

'''Note:''' Select the correct FPGA image that matches your USRP (either <code>_x300</code> or <code>_x310</code>) with the <code>.bit</code> file extension. It is recommended to select the <code>_HG</code> FPGA image, which will initialize Port 0 as 1 GbE and Port 1 as 10 GbE. Advanced users operating with dual 10 GbE may select the <code>_XG</code> image, however you will need to adjust the instructions listed within this document to match the dual 10GbE configuration (IP Addresses, MTU settings, etc).

[[File:22 x300 device recovery 2026.jpg|700px|center]]

Next, click <code>Program</code>.

[[File:23 x300 device recovery 2026.jpg|700px|center]]

A progress bar will popup as the FPGA is programmed.

[[File:24 x300 device recovery 2026.jpg|700px|center]]

Once the programming is completed, close Vivado Lab.

'''Note:''' If Vivado is actively attached to the USRP (<code>auto-connect</code> is enabled for the specific target), then at USRP power cycle Vivado ''will stop'' the USRP from auto-loading whatever FPGA image is stored on it.

[[File:25 x300 device recovery 2026.jpg|700px|center]]

'''Note:''' Do NOT power-cycle the device at this stage since it’s the temporary image. Flashing the FPGA image via JTAG only does not write the FPGA image to EEPROM, you must run the <code>uhd_image_loader</code> to write the FPGA image to the internal EEPROM.

Now, remove the JTAG cable from X310 and try to ping X310 using the command:

ping 192.168.10.2

(It should work if IP configuration step is performed correctly.)

At this point, if you're able to ping the USRP X300/X310, attempt to run the UHD utility <code>uhd_usrp_probe</code>.

uhd_usrp_probe

Example output from <code>uhd_usrp_probe</code>:

[[File:26 x300 device recovery 2026.jpg|700px|center]]

If running <code>uhd_usrp_probe</code> is successful, proceed with flashing the FPGA image with the UHD utility <code>uhd_image_loader</code>.

'''Note:''' Flashing the FPGA image via JTAG only does not write the FPGA image to EEPROM, you must run the <code>uhd_image_loader</code> to write the FPGA image to the internal EEPROM.

uhd_image_loader --args "type=x300,addr=192.168.10.2,fpga=HG"

When <code>uhd_image_loader</code> has completed the flashing process, it will recommend to power cycle the USRP X300/X310.

[[File:27 x300 device recovery 2026.jpg|700px|center]]

Power off the USRP X300/X310, and then power on the USRP X300/X310.

The USRP X300/X310 is now recovered. You should be able to <code>ping</code>, run <code>uhd_usrp_probe</code> and any other UHD utility/application as normal.

[[File:26 x300 device recovery 2026.jpg|700px|center]]

[[Category:Application Notes]]

X300/X310 Device Recovery

2026-06-16T17:19:59Z

SiddhantDhawan: /* Configuring Network Interface */

==Application Note Information==
'''AN-305''' by Neel Pandeya, Michael Dickens and Siddhant Dhawan

==Overview==

This application note covers the process of recovering the USRP X300/X310 by flashing the FPGA image via the JTAG interface.

Note: This guide is written for Linux only. In theory it can be made to work on any OS that supports Xilinx Vivado.

==Manual==

For reference, please refer to the [https://files.ettus.com/manual/page_usrp_x3x0.html user manual page for the X300/X310].

==Required Tools==

* Host Computer
:- USB2/3 port
:- 1 GbE or 10 GbE network interface (NIC)
:- Supports Xilinx Vivado Lab installation
:- Supports UHD installation

* Connections from host to the X3x0 USRP via
:- USB2 cable
:- One of the following, depending on the host computer's NIC
:* SFP+ / RJ45 Adapter and Ethernet cable
:* SFP+ DAC cable

==Prerequisites==

This guide assumes you have a Linux-based host computer that supports Xilinx Vivado, with UHD installed into the default prefix <code>/usr/local</code>; for example we are using Ubuntu Linux and installed UHD from source using the default <code>CMAKE_INSTALL_PREFIX</code>. If you do not have UHD installed, please install it, for example via the [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on Linux]] Application Note.

We recommend using an X310 FPGA image provided by the host computer's UHD install, so that their versions match up. During runtime, UHD checks its version against that of all target USRPs' FPGA versions, and if they are too different then UHD prints a note about the mismatch and errors out.

There are circumstances where using different versions for the host UHD and FPGA image is necessary; performing this scenario is very similar to the steps in this guide, but requires some additional steps once the USRP is accessible via networking. We do not cover this scenario in this guide. If you need assistance under this scenario, please contact Ettus Support for assistance and we will provide you with the extra note steps.

If you do not have the FPGA images downloaded for your current host UHD install, you can obtain them by executing the command:

sudo uhd_images_downloader

Verify you have the FPGA images downloaded by running the command:

ls -alh /usr/local/share/uhd/images/usrp_x3*

[[File:1 x300 device recovery 2026.jpg|700px|center]]

==Installing Xilinx Vivado Lab Edition==

You will need to have an install of Xilinx Vivado Lab Edition, Xilinx Vivado Design Edition, or Xilinx Vivado System Edition. If you have none of those installed, then the minimum install is via Xilinx Vivado Lab Edition -- and that's what we cover in this guide. If you are using the Xilinx Vivado Design or System Edition then the paths may differ slightly from those described herein but the basic steps and process are the same; you can skip this section and go to the next one.

Xilinx Vivado Lab Edition can be downloaded from one the following links:

* [https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/vivado-design-tools.html current version]

* [https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/vivado-design-tools/archive.html legacy versions for older OSs]

===Steps to Install Vivado Lab Edition (License Free)===

After the download is complete, you can verify the MD5 sum of the file if you choose to do so, since Xilinx provides a MD5 SUM Value for each download:

cd ~/Downloads
md5sum Xilinx_Vivado_Lab_Lin_2015.4_1118_2.tar.gz

'''Note:''' The filename and MD5 hash may differ from the screen capture shown. Verify the MD5 sum against the hash listed on the Xilinx download page.

[[File:2 x300 device recovery 2026.jpg|700px|center]]

Next, decompress the downloaded tarball:

tar -xvf Vivado_Lab_Lin_2025.2_1114_2157.tar

This creates:

Vivado_Lab_Lin_2025.2_1114_2157/

[[File:3 x300 device recovery 2026.jpg|700px|center]]

Next, go into the new directory and run the <code>xsetup</code> installer using superuser <code>sudo</code> permissions:

cd Vivado_Lab_Lin_2025.2_1114_2157
sudo ./xsetup

The installer will then be at a Welcome screen, click Next.

[[File:4 x300 device recovery 2026.jpg|700px|center]]

Check the following Check Box and click <code>Next</code>.

[[File:5 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted to accept the various License Agreements, select all of the "I Agree" boxes then click <code>Next</code>.

[[File:6 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted with the installation locations. The default value for older Xilinx Vivado Lab is <code>/opt/Xilinx</code> while for newer versions it is <code>/tools/Xilinx</code>. We will be using the latter here; what you use is your choice, but please note the install directory so that you can make sure to use it correctly later in this guide.

If the install directory does not exist, you will be prompted immediately to create it. Click <code>Yes</code>.

[[File:7 x300 device recovery 2026.jpg|700px|center]]

Finally, you will be at the Installation Summary prompt. Click <code>Install</code>.

[[File:8 x300 device recovery 2026.jpg|700px|center]]

The installer has to download files from the internet, but they are not large and hence the installation process typically takes only a few minutes.

[[File:9 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted that the installation was successful. Click <code>Ok</code>, and the installer will close.

[[File:10 x300 device recovery 2026.jpg|700px|center]]

==Installing the Digilent Cable Driver==

In order to use the JTAG interface built into the USRP X300/X310 front panel, you will need to install the Digilent Cable Driver. It is included with the Xilinx Vivado Lab Edition package.

Navigate to the folder <code>/tools/Xilinx/2025.2/data/xicom/cable_drivers/lin64/install_script/install_drivers</code>, and run the installer script.

cd /tools/Xilinx/2025.2/data/xicom/cable_drivers/lin64/install_script/install_drivers

Verify contents in the directory:

ls

Expected Output:

install_digilent.sh
52-xilinx-digilent-usb.rules

[[File:11 x300 device recovery 2026.jpg|700px|center]]

Now run the installer script:

# The installer requires RDI_BINROOT to be set manually.

export RDI_BINROOT=$(pwd)
sudo -E ./install_digilent.sh

[[File:12 x300 device recovery 2026.jpg|700px|center]]

Next, reload the UDEV rules:

sudo udevadm control --reload
sudo udevadm trigger

[[File:13 x300 device recovery 2026.jpg|700px|center]]

Verify:

ls /etc/udev/rules.d | grep digilent

Expected Output:

52-xilinx-digilent-usb.rules

==Configuring Network Interface==

You will need to set your ethernet interface that will be connected to the USRP X300/X310 to a static IP address of <code>192.168.10.1</code> along with setting a MTU of <code>1500</code>.

Attach the SFP+/RJ45 adapter to Port 0 and connect your computer via ethernet.

{| style="width:100%;"
| style="width:70%; text-align:left;" |
[[File:14 x300 device recovery 2026.jpg|300px]]

| style="width:30%; text-align:right;" |
[[File:15 x300 device recovery 2026.jpg|500px]]
|}

==Prepare the X300/X310==

Connect the host computer where Xilinx Vivado was installed to the USRP X300/X310 via a USB2 cable. On the USRP X300/X310, plug the USB2 cable into the JTAG port on the front face plate. Once the USB cable is connected on both sides, power on the USRP X300/X310.

[[File:16 x300 device recovery 2026.jpg|700px|center]]

==Starting Xilinx Vivado Lab Edition==

Start by navigating back to your home directory:

cd ~/

Next, start Xilinx Vivado Lab via the command line:

/tools/Xilinx/2025.2/Vivado_Lab/bin/vivado_lab

You can also add Vivado Lab to the path so that you can open it from any directory:

echo 'source /tools/Xilinx/2025.2/Vivado_Lab/settings64.sh' >> ~/.bashrc
source ~/.bashrc

[[File:17 x300 device recovery 2026.jpg|700px|center]]

Now, go to any directory (for example <code>cd ~/</code>) and run:

vivado_lab

This will bring up the main Vivado Lab window.

[[File:18 x300 device recovery 2026.jpg|700px|center]]

Open the Hardware Manager by selecting <code>Open Hardware Manager</code>.

[[File:19 x300 device recovery 2026.jpg|700px|center]]

Next, within the menu of the Hardware Manager select <code>Tools</code> -> <code>Auto Connect</code>.

[[File:20 x300 device recovery 2026.jpg|700px|center]]

The details of the FPGA should populate the window on the left side of the Hardware Manager. Right click on the FPGA listed, and select <code>Program Device</code>.

[[File:21 x300 device recovery 2026.jpg|700px|center]]

This will popup a new window. Click on the file selection button and navigate to the location of the UHD FPGA images, and select the correct FPGA image for your device (<code>/usr/local/share/uhd/images</code>).

'''Note:''' Select the correct FPGA image that matches your USRP (either <code>_x300</code> or <code>_x310</code>) with the <code>.bit</code> file extension. It is recommended to select the <code>_HG</code> FPGA image, which will initialize Port 0 as 1 GbE and Port 1 as 10 GbE. Advanced users operating with dual 10 GbE may select the <code>_XG</code> image, however you will need to adjust the instructions listed within this document to match the dual 10GbE configuration (IP Addresses, MTU settings, etc).

[[File:22 x300 device recovery 2026.jpg|700px|center]]

Next, click <code>Program</code>.

[[File:23 x300 device recovery 2026.jpg|700px|center]]

A progress bar will popup as the FPGA is programmed.

[[File:24 x300 device recovery 2026.jpg|700px|center]]

Once the programming is completed, close Vivado Lab.

'''Note:''' If Vivado is actively attached to the USRP (<code>auto-connect</code> is enabled for the specific target), then at USRP power cycle Vivado ''will stop'' the USRP from auto-loading whatever FPGA image is stored on it.

[[File:25 x300 device recovery 2026.jpg|700px|center]]

'''Note:''' Do NOT power-cycle the device at this stage since it’s the temporary image. Flashing the FPGA image via JTAG only does not write the FPGA image to EEPROM, you must run the <code>uhd_image_loader</code> to write the FPGA image to the internal EEPROM.

Now, remove the JTAG cable from X310 and try to ping X310 using the command:

ping 192.168.10.2

(It should work if IP configuration step is performed correctly.)

At this point, if you're able to ping the USRP X300/X310, attempt to run the UHD utility <code>uhd_usrp_probe</code>.

uhd_usrp_probe

Example output from <code>uhd_usrp_probe</code>:

[[File:26 x300 device recovery 2026.jpg|700px|center]]

If running <code>uhd_usrp_probe</code> is successful, proceed with flashing the FPGA image with the UHD utility <code>uhd_image_loader</code>.

'''Note:''' Flashing the FPGA image via JTAG only does not write the FPGA image to EEPROM, you must run the <code>uhd_image_loader</code> to write the FPGA image to the internal EEPROM.

uhd_image_loader --args "type=x300,addr=192.168.10.2,fpga=HG"

When <code>uhd_image_loader</code> has completed the flashing process, it will recommend to power cycle the USRP X300/X310.

[[File:27 x300 device recovery 2026.jpg|700px|center]]

Power off the USRP X300/X310, and then power on the USRP X300/X310.

The USRP X300/X310 is now recovered. You should be able to <code>ping</code>, run <code>uhd_usrp_probe</code> and any other UHD utility/application as normal.

[[File:26 x300 device recovery 2026.jpg|700px|center]]

[[Category:Application Notes]]

X300/X310 Device Recovery

2026-06-16T17:17:55Z

SiddhantDhawan:

==Application Note Information==
'''AN-305''' by Neel Pandeya, Michael Dickens and Siddhant Dhawan

==Overview==

This application note covers the process of recovering the USRP X300/X310 by flashing the FPGA image via the JTAG interface.

Note: This guide is written for Linux only. In theory it can be made to work on any OS that supports Xilinx Vivado.

==Manual==

For reference, please refer to the [https://files.ettus.com/manual/page_usrp_x3x0.html user manual page for the X300/X310].

==Required Tools==

* Host Computer
:- USB2/3 port
:- 1 GbE or 10 GbE network interface (NIC)
:- Supports Xilinx Vivado Lab installation
:- Supports UHD installation

* Connections from host to the X3x0 USRP via
:- USB2 cable
:- One of the following, depending on the host computer's NIC
:* SFP+ / RJ45 Adapter and Ethernet cable
:* SFP+ DAC cable

==Prerequisites==

This guide assumes you have a Linux-based host computer that supports Xilinx Vivado, with UHD installed into the default prefix <code>/usr/local</code>; for example we are using Ubuntu Linux and installed UHD from source using the default <code>CMAKE_INSTALL_PREFIX</code>. If you do not have UHD installed, please install it, for example via the [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on Linux]] Application Note.

We recommend using an X310 FPGA image provided by the host computer's UHD install, so that their versions match up. During runtime, UHD checks its version against that of all target USRPs' FPGA versions, and if they are too different then UHD prints a note about the mismatch and errors out.

There are circumstances where using different versions for the host UHD and FPGA image is necessary; performing this scenario is very similar to the steps in this guide, but requires some additional steps once the USRP is accessible via networking. We do not cover this scenario in this guide. If you need assistance under this scenario, please contact Ettus Support for assistance and we will provide you with the extra note steps.

If you do not have the FPGA images downloaded for your current host UHD install, you can obtain them by executing the command:

sudo uhd_images_downloader

Verify you have the FPGA images downloaded by running the command:

ls -alh /usr/local/share/uhd/images/usrp_x3*

[[File:1 x300 device recovery 2026.jpg|700px|center]]

==Installing Xilinx Vivado Lab Edition==

You will need to have an install of Xilinx Vivado Lab Edition, Xilinx Vivado Design Edition, or Xilinx Vivado System Edition. If you have none of those installed, then the minimum install is via Xilinx Vivado Lab Edition -- and that's what we cover in this guide. If you are using the Xilinx Vivado Design or System Edition then the paths may differ slightly from those described herein but the basic steps and process are the same; you can skip this section and go to the next one.

Xilinx Vivado Lab Edition can be downloaded from one the following links:

* [https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/vivado-design-tools.html current version]

* [https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/vivado-design-tools/archive.html legacy versions for older OSs]

===Steps to Install Vivado Lab Edition (License Free)===

After the download is complete, you can verify the MD5 sum of the file if you choose to do so, since Xilinx provides a MD5 SUM Value for each download:

cd ~/Downloads
md5sum Xilinx_Vivado_Lab_Lin_2015.4_1118_2.tar.gz

'''Note:''' The filename and MD5 hash may differ from the screen capture shown. Verify the MD5 sum against the hash listed on the Xilinx download page.

[[File:2 x300 device recovery 2026.jpg|700px|center]]

Next, decompress the downloaded tarball:

tar -xvf Vivado_Lab_Lin_2025.2_1114_2157.tar

This creates:

Vivado_Lab_Lin_2025.2_1114_2157/

[[File:3 x300 device recovery 2026.jpg|700px|center]]

Next, go into the new directory and run the <code>xsetup</code> installer using superuser <code>sudo</code> permissions:

cd Vivado_Lab_Lin_2025.2_1114_2157
sudo ./xsetup

The installer will then be at a Welcome screen, click Next.

[[File:4 x300 device recovery 2026.jpg|700px|center]]

Check the following Check Box and click <code>Next</code>.

[[File:5 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted to accept the various License Agreements, select all of the "I Agree" boxes then click <code>Next</code>.

[[File:6 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted with the installation locations. The default value for older Xilinx Vivado Lab is <code>/opt/Xilinx</code> while for newer versions it is <code>/tools/Xilinx</code>. We will be using the latter here; what you use is your choice, but please note the install directory so that you can make sure to use it correctly later in this guide.

If the install directory does not exist, you will be prompted immediately to create it. Click <code>Yes</code>.

[[File:7 x300 device recovery 2026.jpg|700px|center]]

Finally, you will be at the Installation Summary prompt. Click <code>Install</code>.

[[File:8 x300 device recovery 2026.jpg|700px|center]]

The installer has to download files from the internet, but they are not large and hence the installation process typically takes only a few minutes.

[[File:9 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted that the installation was successful. Click <code>Ok</code>, and the installer will close.

[[File:10 x300 device recovery 2026.jpg|700px|center]]

==Installing the Digilent Cable Driver==

In order to use the JTAG interface built into the USRP X300/X310 front panel, you will need to install the Digilent Cable Driver. It is included with the Xilinx Vivado Lab Edition package.

Navigate to the folder <code>/tools/Xilinx/2025.2/data/xicom/cable_drivers/lin64/install_script/install_drivers</code>, and run the installer script.

cd /tools/Xilinx/2025.2/data/xicom/cable_drivers/lin64/install_script/install_drivers

Verify contents in the directory:

ls

Expected Output:

install_digilent.sh
52-xilinx-digilent-usb.rules

[[File:11 x300 device recovery 2026.jpg|700px|center]]

Now run the installer script:

# The installer requires RDI_BINROOT to be set manually.

export RDI_BINROOT=$(pwd)
sudo -E ./install_digilent.sh

[[File:12 x300 device recovery 2026.jpg|700px|center]]

Next, reload the UDEV rules:

sudo udevadm control --reload
sudo udevadm trigger

[[File:13 x300 device recovery 2026.jpg|700px|center]]

Verify:

ls /etc/udev/rules.d | grep digilent

Expected Output:

52-xilinx-digilent-usb.rules

==Configuring Network Interface==

You will need to set your ethernet interface that will be connected to the USRP X300/X310 to a static IP address of <code>192.168.10.1</code> along with setting a MTU of <code>1500</code>.

Attach the SFP+/RJ45 adapter to Port 0 and connect your computer via ethernet.

{| style="width:100%;"
| style="width:50%; text-align:left;" |
[[File:14 x300 device recovery 2026.jpg|300px]]

| style="width:50%; text-align:right;" |
[[File:15 x300 device recovery 2026.jpg|500px]]
|}

==Prepare the X300/X310==

Connect the host computer where Xilinx Vivado was installed to the USRP X300/X310 via a USB2 cable. On the USRP X300/X310, plug the USB2 cable into the JTAG port on the front face plate. Once the USB cable is connected on both sides, power on the USRP X300/X310.

[[File:16 x300 device recovery 2026.jpg|700px|center]]

==Starting Xilinx Vivado Lab Edition==

Start by navigating back to your home directory:

cd ~/

Next, start Xilinx Vivado Lab via the command line:

/tools/Xilinx/2025.2/Vivado_Lab/bin/vivado_lab

You can also add Vivado Lab to the path so that you can open it from any directory:

echo 'source /tools/Xilinx/2025.2/Vivado_Lab/settings64.sh' >> ~/.bashrc
source ~/.bashrc

[[File:17 x300 device recovery 2026.jpg|700px|center]]

Now, go to any directory (for example <code>cd ~/</code>) and run:

vivado_lab

This will bring up the main Vivado Lab window.

[[File:18 x300 device recovery 2026.jpg|700px|center]]

Open the Hardware Manager by selecting <code>Open Hardware Manager</code>.

[[File:19 x300 device recovery 2026.jpg|700px|center]]

Next, within the menu of the Hardware Manager select <code>Tools</code> -> <code>Auto Connect</code>.

[[File:20 x300 device recovery 2026.jpg|700px|center]]

The details of the FPGA should populate the window on the left side of the Hardware Manager. Right click on the FPGA listed, and select <code>Program Device</code>.

[[File:21 x300 device recovery 2026.jpg|700px|center]]

This will popup a new window. Click on the file selection button and navigate to the location of the UHD FPGA images, and select the correct FPGA image for your device (<code>/usr/local/share/uhd/images</code>).

'''Note:''' Select the correct FPGA image that matches your USRP (either <code>_x300</code> or <code>_x310</code>) with the <code>.bit</code> file extension. It is recommended to select the <code>_HG</code> FPGA image, which will initialize Port 0 as 1 GbE and Port 1 as 10 GbE. Advanced users operating with dual 10 GbE may select the <code>_XG</code> image, however you will need to adjust the instructions listed within this document to match the dual 10GbE configuration (IP Addresses, MTU settings, etc).

[[File:22 x300 device recovery 2026.jpg|700px|center]]

Next, click <code>Program</code>.

[[File:23 x300 device recovery 2026.jpg|700px|center]]

A progress bar will popup as the FPGA is programmed.

[[File:24 x300 device recovery 2026.jpg|700px|center]]

Once the programming is completed, close Vivado Lab.

'''Note:''' If Vivado is actively attached to the USRP (<code>auto-connect</code> is enabled for the specific target), then at USRP power cycle Vivado ''will stop'' the USRP from auto-loading whatever FPGA image is stored on it.

[[File:25 x300 device recovery 2026.jpg|700px|center]]

'''Note:''' Do NOT power-cycle the device at this stage since it’s the temporary image. Flashing the FPGA image via JTAG only does not write the FPGA image to EEPROM, you must run the <code>uhd_image_loader</code> to write the FPGA image to the internal EEPROM.

Now, remove the JTAG cable from X310 and try to ping X310 using the command:

ping 192.168.10.2

(It should work if IP configuration step is performed correctly.)

At this point, if you're able to ping the USRP X300/X310, attempt to run the UHD utility <code>uhd_usrp_probe</code>.

uhd_usrp_probe

Example output from <code>uhd_usrp_probe</code>:

[[File:26 x300 device recovery 2026.jpg|700px|center]]

If running <code>uhd_usrp_probe</code> is successful, proceed with flashing the FPGA image with the UHD utility <code>uhd_image_loader</code>.

'''Note:''' Flashing the FPGA image via JTAG only does not write the FPGA image to EEPROM, you must run the <code>uhd_image_loader</code> to write the FPGA image to the internal EEPROM.

uhd_image_loader --args "type=x300,addr=192.168.10.2,fpga=HG"

When <code>uhd_image_loader</code> has completed the flashing process, it will recommend to power cycle the USRP X300/X310.

[[File:27 x300 device recovery 2026.jpg|700px|center]]

Power off the USRP X300/X310, and then power on the USRP X300/X310.

The USRP X300/X310 is now recovered. You should be able to <code>ping</code>, run <code>uhd_usrp_probe</code> and any other UHD utility/application as normal.

[[File:26 x300 device recovery 2026.jpg|700px|center]]

[[Category:Application Notes]]

X300/X310 Device Recovery

2026-06-16T17:12:55Z

SiddhantDhawan:

==Application Note Information==
'''AN-305''' by Neel Pandeya, Michael Dickens and Siddhant Dhawan

==Overview==

This application note covers the process of recovering the USRP X300/X310 by flashing the FPGA image via the JTAG interface.

Note: This guide is written for Linux only. In theory it can be made to work on any OS that supports Xilinx Vivado.

==Manual==

For reference, please refer to the [https://files.ettus.com/manual/page_usrp_x3x0.html user manual page for the X300/X310].

==Required Tools==

* Host Computer
:- USB2/3 port
:- 1 GbE or 10 GbE network interface (NIC)
:- Supports Xilinx Vivado Lab installation
:- Supports UHD installation

* Connections from host to the X3x0 USRP via
:- USB2 cable
:- One of the following, depending on the host computer's NIC
:* SFP+ / RJ45 Adapter and Ethernet cable
:* SFP+ DAC cable

==Prerequisites==

This guide assumes you have a Linux-based host computer that supports Xilinx Vivado, with UHD installed into the default prefix <code>/usr/local</code>; for example we are using Ubuntu Linux and installed UHD from source using the default <code>CMAKE_INSTALL_PREFIX</code>. If you do not have UHD installed, please install it, for example via the [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on Linux]] Application Note.

We recommend using an X310 FPGA image provided by the host computer's UHD install, so that their versions match up. During runtime, UHD checks its version against that of all target USRPs' FPGA versions, and if they are too different then UHD prints a note about the mismatch and errors out.

There are circumstances where using different versions for the host UHD and FPGA image is necessary; performing this scenario is very similar to the steps in this guide, but requires some additional steps once the USRP is accessible via networking. We do not cover this scenario in this guide. If you need assistance under this scenario, please contact Ettus Support for assistance and we will provide you with the extra note steps.

If you do not have the FPGA images downloaded for your current host UHD install, you can obtain them by executing the command:

sudo uhd_images_downloader

Verify you have the FPGA images downloaded by running the command:

ls -alh /usr/local/share/uhd/images/usrp_x3*

[[File:1 x300 device recovery 2026.jpg|700px|center]]

==Installing Xilinx Vivado Lab Edition==

You will need to have an install of Xilinx Vivado Lab Edition, Xilinx Vivado Design Edition, or Xilinx Vivado System Edition. If you have none of those installed, then the minimum install is via Xilinx Vivado Lab Edition -- and that's what we cover in this guide. If you are using the Xilinx Vivado Design or System Edition then the paths may differ slightly from those described herein but the basic steps and process are the same; you can skip this section and go to the next one.

Xilinx Vivado Lab Edition can be downloaded from one the following links:

* [https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/vivado-design-tools.html current version]

* [https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/vivado-design-tools/archive.html legacy versions for older OSs]

===Steps to Install Vivado Lab Edition (License Free)===

After the download is complete, you can verify the MD5 sum of the file if you choose to do so, since Xilinx provides a MD5 SUM Value for each download:

cd ~/Downloads
md5sum Xilinx_Vivado_Lab_Lin_2015.4_1118_2.tar.gz

'''Note:''' The filename and MD5 hash may differ from the screen capture shown. Verify the MD5 sum against the hash listed on the Xilinx download page.

[[File:2 x300 device recovery 2026.jpg|700px|center]]

Next, decompress the downloaded tarball:

tar -xvf Vivado_Lab_Lin_2025.2_1114_2157.tar

This creates:

Vivado_Lab_Lin_2025.2_1114_2157/

[[File:3 x300 device recovery 2026.jpg|700px|center]]

Next, go into the new directory and run the <code>xsetup</code> installer using superuser <code>sudo</code> permissions:

cd Vivado_Lab_Lin_2025.2_1114_2157
sudo ./xsetup

The installer will then be at a Welcome screen, click Next.

[[File:4 x300 device recovery 2026.jpg|700px|center]]

Check the following Check Box and click <code>Next</code>.

[[File:5 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted to accept the various License Agreements, select all of the "I Agree" boxes then click <code>Next</code>.

[[File:6 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted with the installation locations. The default value for older Xilinx Vivado Lab is <code>/opt/Xilinx</code> while for newer versions it is <code>/tools/Xilinx</code>. We will be using the latter here; what you use is your choice, but please note the install directory so that you can make sure to use it correctly later in this guide.

If the install directory does not exist, you will be prompted immediately to create it. Click <code>Yes</code>.

[[File:7 x300 device recovery 2026.jpg|700px|center]]

Finally, you will be at the Installation Summary prompt. Click <code>Install</code>.

[[File:8 x300 device recovery 2026.jpg|700px|center]]

The installer has to download files from the internet, but they are not large and hence the installation process typically takes only a few minutes.

[[File:9 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted that the installation was successful. Click <code>Ok</code>, and the installer will close.

[[File:10 x300 device recovery 2026.jpg|700px|center]]

==Installing the Digilent Cable Driver==

In order to use the JTAG interface built into the USRP X300/X310 front panel, you will need to install the Digilent Cable Driver. It is included with the Xilinx Vivado Lab Edition package.

Navigate to the folder <code>/tools/Xilinx/2025.2/data/xicom/cable_drivers/lin64/install_script/install_drivers</code>, and run the installer script.

cd /tools/Xilinx/2025.2/data/xicom/cable_drivers/lin64/install_script/install_drivers

Verify contents in the directory:

ls

Expected Output:

install_digilent.sh
52-xilinx-digilent-usb.rules

[[File:11 x300 device recovery 2026.jpg|700px|center]]

Now run the installer script:

# The installer requires RDI_BINROOT to be set manually.

export RDI_BINROOT=$(pwd)
sudo -E ./install_digilent.sh

[[File:12 x300 device recovery 2026.jpg|700px|center]]

Next, reload the UDEV rules:

sudo udevadm control --reload
sudo udevadm trigger

[[File:13 x300 device recovery 2026.jpg|700px|center]]

Verify:

ls /etc/udev/rules.d | grep digilent

Expected Output:

52-xilinx-digilent-usb.rules

==Configuring Network Interface==

You will need to set your ethernet interface that will be connected to the USRP X300/X310 to a static IP address of <code>192.168.10.1</code> along with setting a MTU of <code>1500</code>.

Attach the SFP+/RJ45 adapter to Port 0 and connect your computer via ethernet.

{| style="width:100%;"
| style="width:50%; text-align:left;" |
[[File:14 x300 device recovery 2026.jpg|300px]]

| style="width:50%; text-align:right;" |
[[File:15 x300 device recovery 2026.jpg|500px]]
|}

==Prepare the X300/X310==

Connect the host computer where Xilinx Vivado was installed to the USRP X300/X310 via a USB2 cable. On the USRP X300/X310, plug the USB2 cable into the JTAG port on the front face plate. Once the USB cable is connected on both sides, power on the USRP X300/X310.

[[File:16 x300 device recovery 2026.jpg|700px|center]]

==Starting Xilinx Vivado Lab Edition==

Start by navigating back to your home directory:

cd ~/

Next, start Xilinx Vivado Lab via the command line:

/tools/Xilinx/2025.2/Vivado_Lab/bin/vivado_lab

You can also add Vivado Lab to the path so that you can open it from any directory:

echo 'source /tools/Xilinx/2025.2/Vivado_Lab/settings64.sh' >> ~/.bashrc
source ~/.bashrc

[[File:17 x300 device recovery 2026.jpg|700px|center]]

Now, go to any directory (for example <code>cd ~/</code>) and run:

vivado_lab

[[File:18 x300 device recovery 2026.jpg|700px|center]]

This will bring up the main Vivado Lab window.

Open the Hardware Manager by selecting <code>Open Hardware Manager</code>.

[[File:19 x300 device recovery 2026.jpg|700px|center]]

This will bring up the main Vivado Lab window. Open the Hardware Manager by selecting <code>Open Hardware Manager</code> :

[[File:20 x300 device recovery 2026.jpg|700px|center]]

Next, within the menu of the Hardware Manager select <code>Tools</code> -> <code>Auto Connect</code>.

[[File:21 x300 device recovery 2026.jpg|700px|center]]

The details of the FPGA should populate the window on the left side of the Hardware Manager. Right click on the FPGA listed, and select <code>Program Device</code>.

[[File:22 x300 device recovery 2026.jpg|700px|center]]

This will popup a new window. Click on the file selection button and navigate to the location of the UHD FPGA images, and select the correct FPGA image for your device (<code>/usr/local/share/uhd/images</code>).

'''Note:''' Select the correct FPGA image that matches your USRP (either <code>_x300</code> or <code>_x310</code>) with the <code>.bit</code> file extension. It is recommended to select the <code>_HG</code> FPGA image, which will initialize Port 0 as 1 GbE and Port 1 as 10 GbE. Advanced users operating with dual 10 GbE may select the <code>_XG</code> image, however you will need to adjust the instructions listed within this document to match the dual 10GbE configuration (IP Addresses, MTU settings, etc).

[[File:23 x300 device recovery 2026.jpg|700px|center]]

Next, click <code>Program</code>.

[[File:24 x300 device recovery 2026.jpg|700px|center]]

A progress bar will popup as the FPGA is programmed.

[[File:25 x300 device recovery 2026.jpg|700px|center]]

Once the programming is completed, close Vivado Lab.

'''Note:''' If Vivado is actively attached to the USRP (<code>auto-connect</code> is enabled for the specific target), then at USRP power cycle Vivado ''will stop'' the USRP from auto-loading whatever FPGA image is stored on it.

[[File:26 x300 device recovery 2026.jpg|700px|center]]

'''Note:''' Do NOT power-cycle the device at this stage since it’s the temporary image. Flashing the FPGA image via JTAG only does not write the FPGA image to EEPROM, you must run the <code>uhd_image_loader</code> to write the FPGA image to the internal EEPROM.

Now, remove the JTAG cable from X310 and try to ping X310 using the command:

ping 192.168.10.2

(It should work if IP configuration step is performed correctly.)

At this point, if you're able to ping the USRP X300/X310, attempt to run the UHD utility <code>uhd_usrp_probe</code>.

uhd_usrp_probe

Example output from <code>uhd_usrp_probe</code>:

[[File:27 x300 device recovery 2026.jpg|700px|center]]

If running <code>uhd_usrp_probe</code> is successful, proceed with flashing the FPGA image with the UHD utility <code>uhd_image_loader</code>.

'''Note:''' Flashing the FPGA image via JTAG only does not write the FPGA image to EEPROM, you must run the <code>uhd_image_loader</code> to write the FPGA image to the internal EEPROM.

uhd_image_loader --args "type=x300,addr=192.168.10.2,fpga=HG"

When <code>uhd_image_loader</code> has completed the flashing process, it will recommend to power cycle the USRP X300/X310.

[[File:28 x300 device recovery 2026.jpg|700px|center]]

Power off the USRP X300/X310, and then power on the USRP X300/X310.

The USRP X300/X310 is now recovered. You should be able to <code>ping</code>, run <code>uhd_usrp_probe</code> and any other UHD utility/application as normal.

[[File:27 x300 device recovery 2026.jpg|700px|center]]

[[Category:Application Notes]]

X300/X310 Device Recovery

2026-06-16T17:10:47Z

SiddhantDhawan:

==Application Note Information==
'''AN-305''' by Neel Pandeya, Michael Dickens and Siddhant Dhawan

==Overview==

This application note covers the process of recovering the USRP X300/X310 by flashing the FPGA image via the JTAG interface.

Note: This guide is written for Linux only. In theory it can be made to work on any OS that supports Xilinx Vivado.

==Manual==

For reference, please refer to the [https://files.ettus.com/manual/page_usrp_x3x0.html user manual page for the X300/X310].

==Required Tools==

* Host Computer
:- USB2/3 port
:- 1 GbE or 10 GbE network interface (NIC)
:- Supports Xilinx Vivado Lab installation
:- Supports UHD installation

* Connections from host to the X3x0 USRP via
:- USB2 cable
:- One of the following, depending on the host computer's NIC
:* SFP+ / RJ45 Adapter and Ethernet cable
:* SFP+ DAC cable

==Prerequisites==

This guide assumes you have a Linux-based host computer that supports Xilinx Vivado, with UHD installed into the default prefix <code>/usr/local</code>; for example we are using Ubuntu Linux and installed UHD from source using the default <code>CMAKE_INSTALL_PREFIX</code>. If you do not have UHD installed, please install it, for example via the [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on Linux]] Application Note.

We recommend using an X310 FPGA image provided by the host computer's UHD install, so that their versions match up. During runtime, UHD checks its version against that of all target USRPs' FPGA versions, and if they are too different then UHD prints a note about the mismatch and errors out.

There are circumstances where using different versions for the host UHD and FPGA image is necessary; performing this scenario is very similar to the steps in this guide, but requires some additional steps once the USRP is accessible via networking. We do not cover this scenario in this guide. If you need assistance under this scenario, please contact Ettus Support for assistance and we will provide you with the extra note steps.

If you do not have the FPGA images downloaded for your current host UHD install, you can obtain them by executing the command:

sudo uhd_images_downloader

Verify you have the FPGA images downloaded by running the command:

ls -alh /usr/local/share/uhd/images/usrp_x3*

[[File:1 x300 device recovery 2026.jpg|700px|center]]

==Installing Xilinx Vivado Lab Edition==

You will need to have an install of Xilinx Vivado Lab Edition, Xilinx Vivado Design Edition, or Xilinx Vivado System Edition. If you have none of those installed, then the minimum install is via Xilinx Vivado Lab Edition -- and that's what we cover in this guide. If you are using the Xilinx Vivado Design or System Edition then the paths may differ slightly from those described herein but the basic steps and process are the same; you can skip this section and go to the next one.

Xilinx Vivado Lab Edition can be downloaded from one the following links:

* [https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/vivado-design-tools.html current version]

* [https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/vivado-design-tools/archive.html legacy versions for older OSs]

===Steps to Install Vivado Lab Edition (License Free)===

After the download is complete, you can verify the MD5 sum of the file if you choose to do so, since Xilinx provides a MD5 SUM Value for each download:

cd ~/Downloads
md5sum Xilinx_Vivado_Lab_Lin_2015.4_1118_2.tar.gz

'''Note:''' The filename and MD5 hash may differ from the screen capture shown. Verify the MD5 sum against the hash listed on the Xilinx download page.

[[File:2 x300 device recovery 2026.jpg|700px|center]]

Next, decompress the downloaded tarball:

tar -xvf Vivado_Lab_Lin_2025.2_1114_2157.tar

This creates:

Vivado_Lab_Lin_2025.2_1114_2157/

[[File:3 x300 device recovery 2026.jpg|700px|center]]

Next, go into the new directory and run the <code>xsetup</code> installer using superuser <code>sudo</code> permissions:

cd Vivado_Lab_Lin_2025.2_1114_2157
sudo ./xsetup

The installer will then be at a Welcome screen, click Next.

[[File:4 x300 device recovery 2026.jpg|700px|center]]

Check the following Check Box and click <code>Next</code>.

[[File:5 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted to accept the various License Agreements, select all of the "I Agree" boxes then click <code>Next</code>.

[[File:6 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted with the installation locations. The default value for older Xilinx Vivado Lab is <code>/opt/Xilinx</code> while for newer versions it is <code>/tools/Xilinx</code>. We will be using the latter here; what you use is your choice, but please note the install directory so that you can make sure to use it correctly later in this guide.

If the install directory does not exist, you will be prompted immediately to create it. Click <code>Yes</code>.

[[File:7 x300 device recovery 2026.jpg|700px|center]]

Finally, you will be at the Installation Summary prompt. Click <code>Install</code>.

[[File:8 x300 device recovery 2026.jpg|700px|center]]

The installer has to download files from the internet, but they are not large and hence the installation process typically takes only a few minutes.

[[File:9 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted that the installation was successful. Click <code>Ok</code>, and the installer will close.

[[File:10 x300 device recovery 2026.jpg|700px|center]]

==Installing the Digilent Cable Driver==

In order to use the JTAG interface built into the USRP X300/X310 front panel, you will need to install the Digilent Cable Driver. It is included with the Xilinx Vivado Lab Edition package.

Navigate to the folder <code>/tools/Xilinx/2025.2/data/xicom/cable_drivers/lin64/install_script/install_drivers</code>, and run the installer script.

cd /tools/Xilinx/2025.2/data/xicom/cable_drivers/lin64/install_script/install_drivers

Verify contents in the directory:

ls

Expected Output:

install_digilent.sh
52-xilinx-digilent-usb.rules

[[File:11 x300 device recovery 2026.jpg|700px|center]]

Now run the installer script:

# The installer requires RDI_BINROOT to be set manually.

export RDI_BINROOT=$(pwd)
sudo -E ./install_digilent.sh

[[File:12 x300 device recovery 2026.jpg|700px|center]]

Next, reload the UDEV rules:

sudo udevadm control --reload
sudo udevadm trigger

[[File:13 x300 device recovery 2026.jpg|700px|center]]

Verify:

ls /etc/udev/rules.d | grep digilent

Expected Output:

52-xilinx-digilent-usb.rules

==Configuring Network Interface==

You will need to set your ethernet interface that will be connected to the USRP X300/X310 to a static IP address of <code>192.168.10.1</code> along with setting a MTU of <code>1500</code>.

Attach the SFP+/RJ45 adapter to Port 0 and connect your computer via ethernet.

{| style="width:100%;"
| style="width:50%; text-align:left;" |
[[File:14 x300 device recovery 2026.jpg|300px]]

| style="width:50%; text-align:right;" |
[[File:15 x300 device recovery 2026.jpg|500px]]
|}

==Prepare the X300/X310==

Connect the host computer where Xilinx Vivado was installed to the USRP X300/X310 via a USB2 cable. On the USRP X300/X310, plug the USB2 cable into the JTAG port on the front face plate. Once the USB cable is connected on both sides, power on the USRP X300/X310.

[[File:16 x300 device recovery 2026.jpg|700px|center]]

==Starting Xilinx Vivado Lab Edition==

Start by navigating back to your home directory:

cd ~/

Next, start Xilinx Vivado Lab via the command line:

/tools/Xilinx/2025.2/Vivado_Lab/bin/vivado_lab

You can also add Vivado Lab to the path so that you can open it from any directory:

echo 'source /tools/Xilinx/2025.2/Vivado_Lab/settings64.sh' >> ~/.bashrc
source ~/.bashrc

[[File:16 x300 device recovery 2026.jpg|700px|center]]

Now, go to any directory (for example <code>cd ~/</code>) and run:

vivado_lab

[[File:17 x300 device recovery 2026.jpg|700px|center]]

This will bring up the main Vivado Lab window.

Open the Hardware Manager by selecting <code>Open Hardware Manager</code>.

[[File:18 x300 device recovery 2026.jpg|700px|center]]

This will bring up the main Vivado Lab window. Open the Hardware Manager by selecting <code>Open Hardware Manager</code> :

[[File:19 x300 device recovery 2026.jpg|700px|center]]

Next, within the menu of the Hardware Manager select <code>Tools</code> -> <code>Auto Connect</code>.

[[File:20 x300 device recovery 2026.jpg|700px|center]]

The details of the FPGA should populate the window on the left side of the Hardware Manager. Right click on the FPGA listed, and select <code>Program Device</code>.

[[File:21 x300 device recovery 2026.jpg|700px|center]]

This will popup a new window. Click on the file selection button and navigate to the location of the UHD FPGA images, and select the correct FPGA image for your device (<code>/usr/local/share/uhd/images</code>).

'''Note:''' Select the correct FPGA image that matches your USRP (either <code>_x300</code> or <code>_x310</code>) with the <code>.bit</code> file extension. It is recommended to select the <code>_HG</code> FPGA image, which will initialize Port 0 as 1 GbE and Port 1 as 10 GbE. Advanced users operating with dual 10 GbE may select the <code>_XG</code> image, however you will need to adjust the instructions listed within this document to match the dual 10GbE configuration (IP Addresses, MTU settings, etc).

[[File:22 x300 device recovery 2026.jpg|700px|center]]

Next, click <code>Program</code>.

[[File:23 x300 device recovery 2026.jpg|700px|center]]

A progress bar will popup as the FPGA is programmed.

[[File:24 x300 device recovery 2026.jpg|700px|center]]

Once the programming is completed, close Vivado Lab.

'''Note:''' If Vivado is actively attached to the USRP (<code>auto-connect</code> is enabled for the specific target), then at USRP power cycle Vivado ''will stop'' the USRP from auto-loading whatever FPGA image is stored on it.

[[File:25 x300 device recovery 2026.jpg|700px|center]]

'''Note:''' Do NOT power-cycle the device at this stage since it’s the temporary image. Flashing the FPGA image via JTAG only does not write the FPGA image to EEPROM, you must run the <code>uhd_image_loader</code> to write the FPGA image to the internal EEPROM.

Now, remove the JTAG cable from X310 and try to ping X310 using the command:

ping 192.168.10.2

(It should work if IP configuration step is performed correctly.)

At this point, if you're able to ping the USRP X300/X310, attempt to run the UHD utility <code>uhd_usrp_probe</code>.

uhd_usrp_probe

Example output from <code>uhd_usrp_probe</code>:

[[File:26 x300 device recovery 2026.jpg|700px|center]]

If running <code>uhd_usrp_probe</code> is successful, proceed with flashing the FPGA image with the UHD utility <code>uhd_image_loader</code>.

'''Note:''' Flashing the FPGA image via JTAG only does not write the FPGA image to EEPROM, you must run the <code>uhd_image_loader</code> to write the FPGA image to the internal EEPROM.

uhd_image_loader --args "type=x300,addr=192.168.10.2,fpga=HG"

When <code>uhd_image_loader</code> has completed the flashing process, it will recommend to power cycle the USRP X300/X310.

[[File:27 x300 device recovery 2026.jpg|700px|center]]

Power off the USRP X300/X310, and then power on the USRP X300/X310.

The USRP X300/X310 is now recovered. You should be able to <code>ping</code>, run <code>uhd_usrp_probe</code> and any other UHD utility/application as normal.

[[File:26 x300 device recovery 2026.jpg|700px|center]]

[[Category:Application Notes]]

X300/X310 Device Recovery

2026-06-16T17:06:44Z

SiddhantDhawan:

==Application Note Information==
'''AN-305''' by Neel Pandeya, Michael Dickens and Siddhant Dhawan

==Overview==

This application note covers the process of recovering the USRP X300/X310 by flashing the FPGA image via the JTAG interface.

Note: This guide is written for Linux only. In theory it can be made to work on any OS that supports Xilinx Vivado.

==Manual==

For reference, please refer to the [https://files.ettus.com/manual/page_usrp_x3x0.html user manual page for the X300/X310].

==Required Tools==

* Host Computer
:- USB2/3 port
:- 1 GbE or 10 GbE network interface (NIC)
:- Supports Xilinx Vivado Lab installation
:- Supports UHD installation

* Connections from host to the X3x0 USRP via
:- USB2 cable
:- One of the following, depending on the host computer's NIC
:* SFP+ / RJ45 Adapter and Ethernet cable
:* SFP+ DAC cable

==Prerequisites==

This guide assumes you have a Linux-based host computer that supports Xilinx Vivado, with UHD installed into the default prefix <code>/usr/local</code>; for example we are using Ubuntu Linux and installed UHD from source using the default <code>CMAKE_INSTALL_PREFIX</code>. If you do not have UHD installed, please install it, for example via the [[Building and Installing the USRP Open-Source Toolchain (UHD and GNU Radio) on Linux]] Application Note.

We recommend using an X310 FPGA image provided by the host computer's UHD install, so that their versions match up. During runtime, UHD checks its version against that of all target USRPs' FPGA versions, and if they are too different then UHD prints a note about the mismatch and errors out.

There are circumstances where using different versions for the host UHD and FPGA image is necessary; performing this scenario is very similar to the steps in this guide, but requires some additional steps once the USRP is accessible via networking. We do not cover this scenario in this guide. If you need assistance under this scenario, please contact Ettus Support for assistance and we will provide you with the extra note steps.

If you do not have the FPGA images downloaded for your current host UHD install, you can obtain them by executing the command:

sudo uhd_images_downloader

Verify you have the FPGA images downloaded by running the command:

ls -alh /usr/local/share/uhd/images/usrp_x3*

[[File:1 x300 device recovery 2026.jpg|700px|center]]

==Installing Xilinx Vivado Lab Edition==

You will need to have an install of Xilinx Vivado Lab Edition, Xilinx Vivado Design Edition, or Xilinx Vivado System Edition. If you have none of those installed, then the minimum install is via Xilinx Vivado Lab Edition -- and that's what we cover in this guide. If you are using the Xilinx Vivado Design or System Edition then the paths may differ slightly from those described herein but the basic steps and process are the same; you can skip this section and go to the next one.

Xilinx Vivado Lab Edition can be downloaded from one the following links:

* [https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/vivado-design-tools.html current version]

* [https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/vivado-design-tools/archive.html legacy versions for older OSs]

===Steps to Install Vivado Lab Edition (License Free)===

After the download is complete, you can verify the MD5 sum of the file if you choose to do so, since Xilinx provides a MD5 SUM Value for each download:

cd ~/Downloads
md5sum Xilinx_Vivado_Lab_Lin_2015.4_1118_2.tar.gz

'''Note:''' The filename and MD5 hash may differ from the screen capture shown. Verify the MD5 sum against the hash listed on the Xilinx download page.

[[File:2 x300 device recovery 2026.jpg|700px|center]]

Next, decompress the downloaded tarball:

tar -xvf Vivado_Lab_Lin_2025.2_1114_2157.tar

This creates:

Vivado_Lab_Lin_2025.2_1114_2157/

[[File:3 x300 device recovery 2026.jpg|700px|center]]

Next, go into the new directory and run the <code>xsetup</code> installer using superuser <code>sudo</code> permissions:

cd Vivado_Lab_Lin_2025.2_1114_2157
sudo ./xsetup

The installer will then be at a Welcome screen, click Next.

[[File:4 x300 device recovery 2026.jpg|700px|center]]

Check the following Check Box and click <code>Next</code>.

[[File:5 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted to accept the various License Agreements, select all of the "I Agree" boxes then click <code>Next</code>.

[[File:6 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted with the installation locations. The default value for older Xilinx Vivado Lab is <code>/opt/Xilinx</code> while for newer versions it is <code>/tools/Xilinx</code>. We will be using the latter here; what you use is your choice, but please note the install directory so that you can make sure to use it correctly later in this guide.

If the install directory does not exist, you will be prompted immediately to create it. Click <code>Yes</code>.

[[File:7 x300 device recovery 2026.jpg|700px|center]]

Finally, you will be at the Installation Summary prompt. Click <code>Install</code>.

[[File:8 x300 device recovery 2026.jpg|700px|center]]

The installer has to download files from the internet, but they are not large and hence the installation process typically takes only a few minutes.

[[File:9 x300 device recovery 2026.jpg|700px|center]]

You will then be prompted that the installation was successful. Click <code>Ok</code>, and the installer will close.

[[File:10 x300 device recovery 2026.jpg|700px|center]]

==Installing the Digilent Cable Driver==

In order to use the JTAG interface built into the USRP X300/X310 front panel, you will need to install the Digilent Cable Driver. It is included with the Xilinx Vivado Lab Edition package.

Navigate to the folder <code>/tools/Xilinx/2025.2/data/xicom/cable_drivers/lin64/install_script/install_drivers</code>, and run the installer script.

cd /tools/Xilinx/2025.2/data/xicom/cable_drivers/lin64/install_script/install_drivers

Verify contents in the directory:

ls

Expected Output:

install_digilent.sh
52-xilinx-digilent-usb.rules

[[File:11 x300 device recovery 2026.jpg|700px|center]]

Now run the installer script:

# The installer requires RDI_BINROOT to be set manually.

export RDI_BINROOT=$(pwd)
sudo -E ./install_digilent.sh

[[File:12 x300 device recovery 2026.jpg|700px|center]]

Next, reload the UDEV rules:

sudo udevadm control --reload
sudo udevadm trigger

[[File:13 x300 device recovery 2026.jpg|700px|center]]

Verify:

ls /etc/udev/rules.d | grep digilent

Expected Output:

52-xilinx-digilent-usb.rules

==Configuring Network Interface==

You will need to set your ethernet interface that will be connected to the USRP X300/X310 to a static IP address of <code>192.168.10.1</code> along with setting a MTU of <code>1500</code>.

Attach the SFP+/RJ45 adapter to Port 0 and connect your computer via ethernet.

{| style="width:100%;"
| style="width:50%; text-align:left;" |
[[File:13 x300 device recovery 2026.jpg|300px]]

| style="width:50%; text-align:right;" |
[[File:14 x300 device recovery 2026.jpg|500px]]
|}

==Prepare the X300/X310==

Connect the host computer where Xilinx Vivado was installed to the USRP X300/X310 via a USB2 cable. On the USRP X300/X310, plug the USB2 cable into the JTAG port on the front face plate. Once the USB cable is connected on both sides, power on the USRP X300/X310.

[[File:15 x300 device recovery 2026.jpg|700px|center]]

==Starting Xilinx Vivado Lab Edition==

Start by navigating back to your home directory:

cd ~/

Next, start Xilinx Vivado Lab via the command line:

/tools/Xilinx/2025.2/Vivado_Lab/bin/vivado_lab

You can also add Vivado Lab to the path so that you can open it from any directory:

echo 'source /tools/Xilinx/2025.2/Vivado_Lab/settings64.sh' >> ~/.bashrc
source ~/.bashrc

[[File:16 x300 device recovery 2026.jpg|700px|center]]

Now, go to any directory (for example <code>cd ~/</code>) and run:

vivado_lab

[[File:17 x300 device recovery 2026.jpg|700px|center]]

This will bring up the main Vivado Lab window.

Open the Hardware Manager by selecting <code>Open Hardware Manager</code>.

[[File:18 x300 device recovery 2026.jpg|700px|center]]

This will bring up the main Vivado Lab window. Open the Hardware Manager by selecting <code>Open Hardware Manager</code> :

[[File:19 x300 device recovery 2026.jpg|700px|center]]

Next, within the menu of the Hardware Manager select <code>Tools</code> -> <code>Auto Connect</code>.

[[File:20 x300 device recovery 2026.jpg|700px|center]]

The details of the FPGA should populate the window on the left side of the Hardware Manager. Right click on the FPGA listed, and select <code>Program Device</code>.

[[File:21 x300 device recovery 2026.jpg|700px|center]]

This will popup a new window. Click on the file selection button and navigate to the location of the UHD FPGA images, and select the correct FPGA image for your device (<code>/usr/local/share/uhd/images</code>).

'''Note:''' Select the correct FPGA image that matches your USRP (either <code>_x300</code> or <code>_x310</code>) with the <code>.bit</code> file extension. It is recommended to select the <code>_HG</code> FPGA image, which will initialize Port 0 as 1 GbE and Port 1 as 10 GbE. Advanced users operating with dual 10 GbE may select the <code>_XG</code> image, however you will need to adjust the instructions listed within this document to match the dual 10GbE configuration (IP Addresses, MTU settings, etc).

[[File:22 x300 device recovery 2026.jpg|700px|center]]

Next, click <code>Program</code>.

[[File:23 x300 device recovery 2026.jpg|700px|center]]

A progress bar will popup as the FPGA is programmed.

[[File:24 x300 device recovery 2026.jpg|700px|center]]

Once the programming is completed, close Vivado Lab.

'''Note:''' If Vivado is actively attached to the USRP (<code>auto-connect</code> is enabled for the specific target), then at USRP power cycle Vivado ''will stop'' the USRP from auto-loading whatever FPGA image is stored on it.

[[File:25 x300 device recovery 2026.jpg|700px|center]]

'''Note:''' Do NOT power-cycle the device at this stage since it’s the temporary image. Flashing the FPGA image via JTAG only does not write the FPGA image to EEPROM, you must run the <code>uhd_image_loader</code> to write the FPGA image to the internal EEPROM.

Now, remove the JTAG cable from X310 and try to ping X310 using the command:

ping 192.168.10.2

(It should work if IP configuration step is performed correctly.)

At this point, if you're able to ping the USRP X300/X310, attempt to run the UHD utility <code>uhd_usrp_probe</code>.

uhd_usrp_probe

Example output from <code>uhd_usrp_probe</code>:

[[File:26 x300 device recovery 2026.jpg|700px|center]]

If running <code>uhd_usrp_probe</code> is successful, proceed with flashing the FPGA image with the UHD utility <code>uhd_image_loader</code>.

'''Note:''' Flashing the FPGA image via JTAG only does not write the FPGA image to EEPROM, you must run the <code>uhd_image_loader</code> to write the FPGA image to the internal EEPROM.

uhd_image_loader --args "type=x300,addr=192.168.10.2,fpga=HG"

When <code>uhd_image_loader</code> has completed the flashing process, it will recommend to power cycle the USRP X300/X310.

[[File:27 x300 device recovery 2026.jpg|700px|center]]

Power off the USRP X300/X310, and then power on the USRP X300/X310.

The USRP X300/X310 is now recovered. You should be able to <code>ping</code>, run <code>uhd_usrp_probe</code> and any other UHD utility/application as normal.

[[File:26 x300 device recovery 2026.jpg|700px|center]]

[[Category:Application Notes]]

File:27 x300 device recovery 2026.jpg

2026-06-16T16:31:10Z

SiddhantDhawan:

File:26 x300 device recovery 2026.jpg

2026-06-16T16:30:49Z

SiddhantDhawan:

File:25 x300 device recovery 2026.jpg

2026-06-16T16:30:27Z

SiddhantDhawan:

File:24 x300 device recovery 2026.jpg

2026-06-16T16:30:07Z

SiddhantDhawan:

File:23 x300 device recovery 2026.jpg

2026-06-16T16:29:44Z

SiddhantDhawan:

File:22 x300 device recovery 2026.jpg

2026-06-16T16:29:19Z

SiddhantDhawan:

File:21 x300 device recovery 2026.jpg

2026-06-16T16:29:02Z

SiddhantDhawan:

File:20 x300 device recovery 2026.jpg

2026-06-16T16:28:39Z

SiddhantDhawan:

File:19 x300 device recovery 2026.jpg

2026-06-16T16:28:16Z

SiddhantDhawan:

File:18 x300 device recovery 2026.jpg

2026-06-16T16:27:57Z

SiddhantDhawan:

File:17 x300 device recovery 2026.jpg

2026-06-16T16:27:11Z

SiddhantDhawan:

File:16 x300 device recovery 2026.jpg

2026-06-16T16:26:53Z

SiddhantDhawan:

File:15 x300 device recovery 2026.jpg

2026-06-16T16:26:27Z

SiddhantDhawan:

File:14 x300 device recovery 2026.jpg

2026-06-16T16:26:01Z

SiddhantDhawan:

File:13 x300 device recovery 2026.jpg

2026-06-16T16:25:41Z

SiddhantDhawan:

File:12 x300 device recovery 2026.jpg

2026-06-16T16:25:16Z

SiddhantDhawan:

File:11 x300 device recovery 2026.jpg

2026-06-16T16:24:51Z

SiddhantDhawan:

File:10 x300 device recovery 2026.jpg

2026-06-16T16:24:25Z

SiddhantDhawan:

File:9 x300 device recovery 2026.jpg

2026-06-16T16:23:59Z

SiddhantDhawan:

File:8 x300 device recovery 2026.jpg

2026-06-16T16:23:41Z

SiddhantDhawan:

File:7 x300 device recovery 2026.jpg

2026-06-16T16:23:13Z

SiddhantDhawan:

File:6 x300 device recovery 2026.jpg

2026-06-16T16:22:48Z

SiddhantDhawan:

File:5 x300 device recovery 2026.jpg

2026-06-16T16:22:23Z

SiddhantDhawan: