bladeRF icon indicating copy to clipboard operation
bladeRF copied to clipboard

Error probing device: SoapySDR::Device::make() no match

Open wudave opened this issue 4 years ago • 11 comments

I am a newbie in SDR. Recently purchased bladeRF 2.0 micro xA4. Following the instructions to install SoapySDR bladeRF plugin from https://github.com/pothosware/SoapyBladeRF/wiki, everything seemed to be installing well but when tried to detect bladeRF, got below error. Does SoapySDR support bladeRF 2.0 micro xA4? Did I miss any critical steps?

$ SoapySDRUtil --probe="driver=bladerf" ######################################################

Soapy SDR -- the SDR abstraction library

######################################################

Probe device driver=bladerf Error probing device: SoapySDR::Device::make() no match

Here are bladeRF info. bladeRF> version

bladeRF-cli version: 1.8.0-MacPorts-20191001-f03d8433 libbladeRF version: 2.2.1-MacPorts-20191001-f03d8433

Firmware version: 2.3.2 FPGA version: 0.11.0 (configured by USB host)

bladeRF> info

Board: Nuand bladeRF 2.0 (bladerf2) Serial #: f4897f2dd81745fca98a93f0ed81571a VCTCXO DAC calibration: 0x1fb1 FPGA size: 49 KLE FPGA loaded: yes Flash size: 32 Mbit USB bus: 1 USB address: 2 USB speed: SuperSpeed Backend: libusb Instance: 0

wudave avatar Oct 13 '19 07:10 wudave

Got the same issue....i'm looking for a solution

vbursucianu avatar Feb 01 '20 20:02 vbursucianu

The solution for me was to install the Soapy Plugin for Bladerf: https://github.com/pothosware/SoapyBladeRF/wiki

git clone https://github.com/pothosware/SoapyOsmo.git
cd SoapyOsmo
mkdir build
cd build
cmake ..
make
sudo make install

When calling : SoapySDRUtil --find

######################################################
##     Soapy SDR -- the SDR abstraction library     ##
######################################################

Found device 0
  backend = libusb
  device = 0x02:0x04
  driver = bladerf
  instance = 0
  label = BladeRF #0 [310b77a1..95529a6c]
  serial = 310b77a1fc67404780de2c5395529a6c

vbursucianu avatar Feb 01 '20 20:02 vbursucianu

Hello,

We have the same error with et HackRF however we tried installing the plugins as you said but the problem is still not fixed.

When calling SoapySDRUtil, we can see that the drivers are installed correctty :

##     Soapy SDR -- the SDR abstraction library     ##
######################################################

Found device 0
  device = HackRF One
  driver = hackrf
  label = HackRF One #0 88869dc3352821b
  part_id = a000cb3c006a4767
  serial = 0000000000000000088869dc3352821b
  version = 2017.02.1

Do you have any insights on how we could fix our issue ?

Have a good day :)

MartinPolytech avatar Feb 03 '21 09:02 MartinPolytech

you have to connect the BladeRF through the DEVICE tab on the Ubuntu (if its ubuntu) , i got the same error, then when i connect thorough Devices, it worked

surangis avatar May 13 '21 06:05 surangis

My issue is I am still very new to SoapySDR, I have installed SoapySDR and then SoapyRTLSDR. i can check using the command SOapySDRUtil --probe, it identifies the rtl drivers and everything is fine. my question is now how can i connect and load the samples from the SDR to a file using SOapySDR. is there is command line. like for eg- rtl_sdr to read the samples.

surangis avatar May 13 '21 06:05 surangis

I have the same problem with you, but my device is LimeSDR Mini. When I ran the program in physical machine Ubuntu 20.04 LTS, not in the VMware, it worked normally. I don't know why.

yangfan852219770 avatar May 26 '21 08:05 yangfan852219770

I am also experiencing this problem using the Python API and an Airspy HF+.

SoapySDRUtil --probe and --find both see the AirspyHF.

I saw a reference elsewhere to the possibility that it is a problem with inconsistent case expectations. driver AirspyHF is what is reported by --probe but driver airspyhf is what is reported by --info

patja avatar Jan 01 '22 03:01 patja