iio_stresstest(1)

πŸ’– iio_stresstest(1) πŸ’–

okay bestie, so this is a page from the LibIIO Utilities manual set, and it's about a lil program called iio_stresstest. No manual-name line copy, we're folding it in like a ✨vibe✨. Let's go πŸ’…


🌸 NAME 🌸

iio_stresstest β€” the stress test program for Libiio 🫢


✨ SYNOPSIS ✨

iio_stresstest [ options ] -u <uri>

like... you give it some options, you give it a uri, it goes feral. that's the whole deal πŸ’€


πŸ¦‹ DESCRIPTION πŸ¦‹

so iio_stresstest is a stress-testing program. its whole personality is: poke at Libiio (or the Libiio daemon, aka IIOD) over and over until bugs fall out. it's giving chaos gremlin but, like, professionally. if there's a bug hiding in there, this is the friend who'll find it πŸ”₯


πŸ‘‘ OPTIONS πŸ‘‘

  • -h, --help β€” tells iio_stresstest to show you some help, and then dip. short and sweet, we love a clean exit πŸ’–
  • -V, --version β€” prints the version info for this copy of iio_stresstest plus the version of the libiio library it's using. super useful for vibe-checking whether the library and iio_stresstest on your system are up to date. also iconic when you're filing a bug report 🌟
  • -S, --scan [backends] β€” scans for available IIO contexts. the optional arg lets you pick specific backend(s): 'ip', 'usb' or 'ip:usb'. USB has extra specific options like Vendor ID and Product ID so you can limit the scan to specific devices: 'usb=0456,b673'. both vid and pid are hexadecimal numbers (no prefix needed), and "*" matches any (that one's for pid only). no argument at all? she checks all that are available, periodt πŸ’…
  • -u, --uri β€” the Uniform Resource Identifier (uri) for connecting to devices. she can be one of these:
    • ip:[address] β€” a network address, either numeric (192.168.0.1) or a network hostname 🌐
    • ip: β€” blanks, babes. if it was compiled with zeroconf support, this'll find an IIO device on the network 🧚
    • usb:[device:port:instance] β€” normally this is what gets returned from iio_stresstest -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. mismatched vibes = no connection 😭
      • [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 (that's the default ✨), 128000 or 256000 β€” but lowkey it can vary system to system.
      • [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 🏠
  • -a, --auto β€” scans for available contexts, and if there's only one available, she uses it. no decisions required, main character energy 😌
  • -T, --timeout <arg> β€” context timeout in milliseconds. 0 = no timeout, i.e. wait forever πŸ•°οΈ
  • -b, --buffer-size <arg> β€” size of the capture buffer. default is 256 πŸ“¦
  • -s, --samples <arg> β€” number of samples to capture, 0 = infinite. default is 0 ♾️
  • -d, --duration <arg> β€” time to wait (in seconds) before stopping all threads ⏳
  • -t, --threads <arg> β€” number of threads to use 🧡
  • -v, --verbose β€” increase verbosity (-vv and -vvv for more) πŸ—£οΈ

πŸŽ€ RETURN VALUE πŸŽ€

if the specified device isn't found, a non-zero exit code is returned. she's telling you something's off, ngl πŸ™ˆ


🌈 SEE ALSO 🌈

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/


πŸ’€ BUGS πŸ’€

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


bestie reminder: this whole thing is from libiio-0.26, dated 06 February 2026 β€” that's the <rainbow>source/version and date</rainbow> of this page, so cite it like that and you're golden πŸ’œ

k bye, go stress test something responsibly, ily 🫢✨

πŸ“¦ where this page comes from