-
Notifications
You must be signed in to change notification settings - Fork 29
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
suscli exceptions on Mac OSX #59
Comments
I have the same issue, in addition I can see that the "Dummy device" is unavailable if that helps
The same issue is also present in the
I have built this from scratch on two different Mac Book M1, but the issue is only present on one of them so I suspect there is an issue with one of the dependencies or build environment. |
The issue is definitely related to SoapySDR. I rebuilt it from scratch (as opposed to install it from brew) and the suscan library now works without error messages:
|
Nah, it was actually an improper exception handling from my part. By the way, what is the output when you plug any SDR (e.g. HackRF) and run suscli devices again? |
This is what it looks like with a USRP B205 connected:
Not sure why the "Dummy device" is "unavailable" though, but not sure if it matters. |
Don't worry about that. The dummy device, although seen by Suscan, it is not instantiable by SoapySDR (hence its unavailability). Think of it as some kind of placeholder when there are no connected devices whatsoever. |
Any idea why these exceptions print when running
suscli devices
The text was updated successfully, but these errors were encountered: