Airspy HF+ not found

[patrickomatik]

I get this error, having built tools from source, on a Raspberry Pi 3:

$sudo airspyhf_info
AirSpy HF library version: 1.8.0
No devices attached.

lsusb shows the device as expected:
Bus 001 Device 006: ID 03eb:800c Atmel Corp. Airspy HF+

airspy_info also gives a similar error. I'm at a loss for what do next in terms of troubleshooting/fixing. The airspy hf+ is correctly seen by SDR sharp on a Windows machine when directly connected.

Possibly relevant - this is apparently a 'recently enhanced' version of the Airspy HF+, purchased last week from an authorised distributor.

Many thanks in advance for any pointers!

[markjfine]

Sounds like you may have skipped a step when building and it's not talking correctly to USB.

First, the code requires libusb-1.0-0 and libusb-1.0-0-dev to build properly with USB (as well as cmake, pkg-config, and build-essential). Make sure those packages are installed before starting the build process.

Second, cmake needs to be run using the -DINSTALL_UDEV_RULES=ON switch, per the instructions.

Double check to see there are no errors or warnings when configuring with cmake, and then building with make.

[patrickomatik]

Thanks for the quick response! I did follow the build process from the readme, and I have checked, and libusb-1.0-0-dev and libusb are both installed. The only warning that shows up with make is: ``` -- Found libusb-1.0, version 1.0.26 CMake Warning (dev) at /usr/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:438 (message): The package name passed to `find_package_handle_standard_args` (LIBUSB) does not match the name of the calling package (USB1). This can lead to problems in calling code that expects `find_package` result variables (e.g., `_FOUND`) to follow a certain pattern. Call Stack (most recent call first): cmake/modules/FindUSB1.cmake:33 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) libairspyhf/CMakeLists.txt:77 (find_package) This warning is for project developers. Use -Wno-dev to suppress it.

…

-- Found LIBUSB: /usr/lib/aarch64-linux-gnu/libusb-1.0.so ``` I still can't find the device, presumably I need to fix the underlying cause of the cmake warning, but I'm not sure what's required to do that? Thanks again, most appreciated

On Tue, 26 Nov 2024 at 00:04, markjfine ***@***.***> wrote: Sounds like you may have skipped a step when building and it's not talking correctly to USB. First, the code requires libusb-1.0-0 and libusb-1.0-0-dev to build properly with USB (as well as cmake, pkg-config, and build-essential). Make sure those packages are installed before starting the build process. Second, cmake needs to be run using the -DINSTALL_UDEV_RULES=ON switch, per the instructions. Double check to see there are no errors or warnings when configuring with cmake, and then building with make. — Reply to this email directly, view it on GitHub <#50 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGE25C3ZVGHDL27JIQU4GKT2CO3IVAVCNFSM6AAAAABSOHOHM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJZGI4DEMJVGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[markjfine]

Interesting. I get the same warning when running cmake but my library isn't affected.

The only other thing I can think of is there may be something with the libairspyhf being used. I'm assuming you've run make install as su (or in sudo) and ran sudo ldconfig -v afterwards (making sure that libairspyhf is listed somewhere).

Mine is located at /usr/local/lib (your's might be elsewhere) and libairspyhf.0.lib is aliased to point to v1.8. Is that what you're seeing?

[patrickomatik]

ldconfig -v|grep air gives me a sane looking: libairspy.so.0 -> libairspy.so.1.0.11 libairspyhf.so.0 -> libairspyhf.so.1.8.0 libairspy.so.0 -> libairspy.so.1.0.12 Aha! sudo airspyhf_info now works, it did not before. (As an aside, it looks like the cmake udev rules do not apply the group setting for plugdev, so my default user, who is a member of plugdev group, can't see it.) However... spyserver can't acquire the device, even when spyserver is run as root (which I'm not wild about, but small bites of the elephant and all that). I guess I need to build spyserver from source? Thanks again, Patrick

…

On Tue, 26 Nov 2024 at 17:36, markjfine ***@***.***> wrote: Interesting. I get the same warning when running cmake but my library isn't affected. The only other thing I can think of is there may be something with the libairspyhf being used. I'm assuming you've run make install as su (or in sudo) and ran sudo ldconfig -v afterwards (making sure that libairspyhf is listed somewhere). Mine is located at /usr/local/lib (your's might be elsewhere) and libairspyhf.0.lib is aliased to point to v1.8. Is that what you're seeing? — Reply to this email directly, view it on GitHub <#50 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGE25CYHJGCMMG6YGBR6T6T2CSWTPAVCNFSM6AAAAABSOHOHM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBRGU2TMNBWGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[markjfine]

Glad I could help get you this far, though I hadn't thought to run the tools as root.
Unfortunately I have zero experience with spyserver.

Good luck.