-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SoapySDRUtil doesn't detect SDRPlay RSP2 #43
Comments
https://github.com/pothosware/SoapySDRPlay - Requires the API from SDRPlay, you have that installed already? "Get SDR Play driver binaries 'API/HW driver v2.x' (not v3.x) from - http://sdrplay.com/downloads" |
Yes, those drivers are installed. It wouldn't even build without them. Happy to post in the group - I was told to log an issue in #pothos on freenode... |
@rich0 I was under the impression that SoapySDRUtil --probe was printing the output for the sdr play, its basically just calling into the null device and printing diddly. Ex, if you SoapySDRUtil --probe="driver=sdrplay", I think you will get a error message. That doesnt help much, but its consistently not working, rather than ambiguously instantiating/not enumerating like I thought. So something must be up with the binaries. |
Here is the output of --probe with the driver. I don't think it is actually enumerating the device, but just displaying the capabilities of the driver itself? SoapySDRUtil --probe="driver=sdrplay" Soapy SDR -- the SDR abstraction library###################################################### Probe device driver=sdrplay -- Device identificationdriver=SDRPlay -- Peripheral summaryChannels: 1 Rx, 0 Tx -- RX Channel 0Full-duplex: YES If I detach the RSP2 and run the command, I get the same output, though there is a pause of about a second at the start which doesn't happen when the device is attached. |
Oh there you go, nice output. @SDRplay what would cause the device instantiation to work, but enumeration shows no devices? |
Can I see the output of lsusb - i.e. what does the system think is connected? The command should be SoapySDRUtil --probe=sdrplay or SoapySDRUtil --find=sdrplay |
lsusb SoapySDRUtil --find=sdrplay Soapy SDR -- the SDR abstraction library###################################################### No devices found! SoapySDRUtil --probe=sdrplay Soapy SDR -- the SDR abstraction library###################################################### Probe device sdrplay -- Device identificationdriver=null -- Peripheral summaryChannels: 0 Rx, 0 Tx |
Something doesn't seem right there - I would... "sudo service udev restart" and then disconnect and reconnect the RSP2 - then try again please. |
I ran (as root) systemctl restart systemd-udevd There was no change in behavior for --find=sdrplay or --probe=sdrplay |
and you physically disconnected and reconnected the RSP? |
Yes - other than the output in dmesg nothing changed: [ 4748.741722] usb 3-3: USB disconnect, device number 4 |
Actually, one second - that's version 0.6 - that's pretty old - where did you get that from? 0.6 probably only works with 2.11 of the API - have you tried building from the latest published source? |
I'm using the Gentoo package for soapysdr-0.6.1. It should be using the tagged tarball from github for that version. Do you want me to build from master? |
I'm pretty sure 0.6 will only work with 2.11 API - 2.13 API will require the latest version of SoapySDRPlay master |
Indeed, that was it. Built against master for both sdrplay and soapysdrplay, and got this output: SoapySDRUtil --find Soapy SDR -- the SDR abstraction library###################################################### libusb: error [udev_hotplug_event] ignoring udev action bind I'm not sure if that libusb error matters. It looks like cubicsdr is doing something also - will do some testing but I'm not anticipating further issues. Sounds like we just need another release. :) |
I've followed most of the troubleshooting steps I've found online and chatted a bit on freenode but haven't been able to figure out why my RSP2 isn't being enumerated. I'm using:
SoapySDRUtil --info
######################################################
Soapy SDR -- the SDR abstraction library
######################################################
Lib Version: v0.6.1-unknown
API Version: v0.6.0
ABI Version: v0.6
Install root: /usr
Search path: /usr/lib64/SoapySDR/modules0.6
Search path: /usr/local/lib64/SoapySDR/modules0.6
Module found: /usr/lib64/SoapySDR/modules0.6/libsdrPlaySupport.so
Loading modules... done
Available factories...null, sdrplay,
SoapySDRUtil --probe
######################################################
Soapy SDR -- the SDR abstraction library
######################################################
Probe device
-- Device identification
driver=null
hardware=null
-- Peripheral summary
Channels: 0 Rx, 0 Tx
Timestamps: NO
SoapySDRUtil --check=sdrplay
######################################################
Soapy SDR -- the SDR abstraction library
######################################################
Loading modules... done
Checking driver 'sdrplay'... PRESENT
Linux ham1 4.17.14 #1 SMP Thu Aug 9 09:45:34 EDT 2018 x86_64 AMD Ryzen 3 2200G with Radeon Vega Graphics AuthenticAMD GNU/Linux
I'm happy to attach kernel configs or whatever you're interested in (strace/etc), or try patches/etc. This is on Gentoo, but my kernel is custom, and I packaged soapysdrplay and the sdrplay libraries myself (soapysdr is the repository version). If I get it working I'll likely add the packages to the main repo.
I have enabled just about all the USB-related options in the kernel except gadget-related options. Also, "lsmod | grep msi" returns nothing. The usb device does show up in /dev/bus/usb with 0666 permissions so the udev rule seems to be working fine.
Is there anything else you can think of that I can do to troubleshoot, or can you think of any kernel-related config settings that might be relevant?
The text was updated successfully, but these errors were encountered: