iio_info(1)

📦
version 0.26 · 8 versions
, in ubuntu resolute, ubuntu stonking

👑 iio_info, but make it make sense 👑

okay bestie, so this little cutie lives in the LibIIO Utilities collection — the manual page calls it iio_info(1) — and it's basically the ✨main character✨ of "wait, what devices do I actually have plugged in?" 💅

🌸 NAME 🌸

iio_info — it lists your IIO devices and all their device attributes. that's it. that's the job. and it ate. 🔥

✨ SYNOPSIS ✨

iio_info [ options ] -u <uri>

💖 DESCRIPTION 💖

iio_info is a utility for showing you info about local or remote IIO devices. local on your own machine? remote over the network? it does not care, it will happily spill the tea about either one 🫖💜

🎀 OPTIONS 🎀

  • -h, --help — tells iio_info to show you some help, and then it dips. bye! 👋
  • -V, --version — prints the version info for this particular copy of iio_info, plus the version of the libiio library it's running on. this is your go-to when you wanna know if the library and iio_info on your system are up to date. also lowkey essential when you're filing a bug report. 🐛
  • -S, --scan [backends] — scans for available IIO contexts. you can hand it an optional arg naming specific backend(s): 'ip', 'usb' or 'ip:usb'. specific options for USB include Vendor ID and Product ID, so you can limit the scan to specific devices like 'usb=0456,b673'. vid,pid are hexadecimal numbers (no prefix needed), and "*" matches any — for pid only. if you give it no argument at all, it checks all the ones that are available. ⭐
  • -u, --uri — the Uniform Resource Identifier (uri) you use to connect to devices. it can be one of these:
    • ip:[address] — a network address, either numeric (192.168.0.1) or a network hostname.
    • ip: — blank. if it was compiled with zeroconf support, it'll go find an IIO device on the network for you 🦋
    • usb:[device:port:instance] — normally this is the thing you got handed back from iio_info -S.
    • serial:[port],[baud],[settings] — these are controlled, and they need to match the iiod (or tinyiiod) on the other end of the serial port. no cap, they have to line up. 💀
      • [port] is something like '/dev/ttyUSB0' on Linux, and 'COM4' on Windows.
      • [baud] is normally one of 110, 300, 600, 1200, 2400, 4800, 9600, 14400, 19200, 38400, 57600, 115200 [default], 128000 or 256000 — but it can vary from system to system, so vibe check your own setup. 🌈
      • [settings] would normally be configured as '8n1', and it's controlled by:
        • data_bits: — (5, 6, 7, 8 [default], or 9)
        • parity_bits: — ('n' none [default], 'o' odd, 'e' even, 'm' mark, or 's' space)
        • stop_bits: — (1 [default, or 2)
        • flow_control: — ('0' none [default], 'x' Xon Xoff, 'r' RTSCTS, or 'd' DTRDSR)
    • local: — with no address part. just vibes, right there on your machine. 🏠
  • -a, --auto — scans for available contexts, and if there's only one available, it just uses it. convenient queen energy 👑

🫶 RETURN VALUE 🫶

if the device you specified isn't found, a non-zero exit code gets returned. so like, check your exit statuses bestie, that's the whole point 😭

🌟 SEE ALSO 🌟

🙈 BUGS 🙈

all bugs are tracked at: https://github.com/analogdevicesinc/libiio/issues

not me telling you to actually go file the bug instead of just complaining in the group chat 💀 do it, the maintainers are nice, fr fr.

and that's the whole page, periodt 💅 this was libiio-0.26, dated 06 February 2026, straight from the LibIIO Utilities crew — mwah, go plug something in and ask iio_info about it 🎀✨🦋

📦 where this page comes from