iio_attr - list IIO devices, and read/write device attributes
iio_attr [ options ] -d [device] [attr] [value]
iio_attr [ options ] -c [device] [channel] [attr] [value]
iio_attr [ options ] -D [device] [attr] [value]
iio_attr [ options ] -C [attr]
iio_attr -S <arg>
iio_attr -h
iio_attr is a utility for displaying information about
local or remote IIO devices. By providing an optional value, iio_attr
will attempt to write the new value to the attribute.
- The iio_attr utility has a few
main options, which control what the main utility of the application
is.
- -d, --device-attr
- Read and Write IIO device attributes
- -c --channel-attr
- Read and Write IIO channel attributes
- -B --buffer-attr
- Read and Write IIO Buffer attributes
- -C --context-attr
- Read and Write IIO Context attributes
- -D --debug-attr
- Read and Write IIO Debug attributes
- -h, --help
- Tells iio_attr to display some help, and then quit.
- -V, --version
- Prints the version information for this particular copy of iio_attr
and the version of the libiio library it is using. This is useful for
knowing if the version of the library and iio_attr on your system
are up to date. This is also useful when reporting bugs.
- -S, --scan
[backends]
- Scan for available IIO contexts, optional arg of specific backend(s) 'ip',
'usb' or 'ip:usb'. Specific options for USB include Vendor ID, Product ID
to limit scanning to specific devices 'usb=0456,b673'. vid,pid are
hexadecimal numbers (no prefix needed), "*" (match any for pid
only) If no argument is given, it checks all that are available.
- -u, --uri
- The Uniform Resource Identifier (uri) for connecting to devices,
can be one of:
- ip:[address]
- network address, either numeric (192.168.0.1) or network hostname
- ip:
- blank, if compiled with zeroconf support, will find an IIO device on
network
- usb:[device:port:instance]
- normally returned from iio_attr -S
- serial:[port],[baud],[settings]
- which are controlled, and need to match the iiod (or tinyiiod) on the
other end of the serial port.
- [port]
- is something like '/dev/ttyUSB0' on Linux, and 'COM4' on Windows.
- [baud]
- is is normally one of 110, 300, 600, 1200, 2400, 4800, 9600, 14400, 19200,
38400, 57600, 115200 [default], 128000 or 256000, but can vary system to
system.
- [settings]
- would normally be configured as '8n1' this is 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.
- -i,
--input-channel
- Filters channels by input channels only
- -o,
--output-channel
- Filters channels by output channels only
- -s, --scan-channel
- Filters channels by scan channels only
- -I, --ignore-case
- When pattern matching devices, channels or attributes, ignore case
- -g, --generate-code
<arg>
- Generate small C or python snippets that emulate what you are doing on the
command line. Argument is a file name 'foo.c' or 'foo.py'
If the specified device is not found, a non-zero exit code is
returned.
iio_attr(1), iio_info(1), iio_readdev(1),
iio_reg(1), iio_writedev(1), libiio(3)
libiio home page:
https://wiki.analog.com/resources/tools-software/linux-software/libiio
libiio code: https://github.com/analogdevicesinc/libiio
Doxygen for libiio
https://analogdevicesinc.github.io/libiio/
All bugs are tracked at:
https://github.com/analogdevicesinc/libiio/issues