analogdevicesinc / libiio

A cross platform library for interfacing with local and remote Linux IIO devices
http://analogdevicesinc.github.io/libiio/
GNU Lesser General Public License v2.1
484 stars 313 forks source link

iio_info generates "Unable to create Local IIO context : No such file or directory (2)" message #916

Closed warnes closed 1 year ago

warnes commented 1 year ago

On Ubuntu 22.04, with libiio installed from the current github master branch:

$ sudo iio_info -s
Library version: 0.24 (git tag: e598e4b)
Compiled with backends: local xml ip usb
Unable to create Local IIO context : No such file or directory (2)
Available contexts:
    0: 192.168.2.1 (Analog Devices PlutoSDR Rev.C (Z7010-AD9363A)), serial=1044734c9605000211000700b41b503492 [ip:pluto-green.local]
    1: 0456:b673 (Analog Devices Inc. PlutoSDR (ADALM-PLUTO)), serial=1044734c9605000211000700b41b503492 [usb:3.39.5]
tfcollins commented 1 year ago

That warning is expected if you have no local iio devices. It can be ignored.

warnes commented 1 year ago

@tfcollins That's what's odd. I do have a local iio device connected, as you can see in the output I included. Here it is with two attached PlutoSDR's:

$ iio_info -s
Library version: 0.24 (git tag: e598e4b)
Compiled with backends: local xml ip usb
Unable to create Local IIO context : No such file or directory (2)
Available contexts:
    0: 192.168.2.1 (Analog Devices PlutoSDR Rev.C (Z7010-AD9363A)), serial=1044734c9605000211000700b41b503492 [ip:pluto-green.local]
    1: 0456:b673 (Analog Devices Inc. PlutoSDR (ADALM-PLUTO)), serial=1044734c9605000211000700b41b503492 [usb:3.59.5]
    2: 0456:b673 (Analog Devices Inc. PlutoSDR (ADALM-PLUTO)), serial=1044734c9605000315000600a42c505f26 [usb:3.60.5]

(There is a second issue, that only one of the two PlutoSDRs show up with IP addresses, even though I have both configured with different IP addresses and hostnames. See https://github.com/analogdevicesinc/plutosdr-fw/issues/73)

tfcollins commented 1 year ago

A local context means the driver is running in your host's kernel. In your case the drivers are running inside the ARM of the Plutos

warnes commented 1 year ago

Ahh. Thanks for the clarification.