SPI(8)

πŸ“¦ version 15.1, in freebsd 14.5, freebsd 15.1

✨ SPI(8) ✨

okay bestie so this is spi, the OpenBSD System Manager's Manual page for talking to SPI bus slave devices, and honestly? it's giving "small tool, huge power" πŸ’… let's get into it.


🌸 NAME 🌸

spi β€” communicate on SPI bus with slave devices


πŸ¦‹ SYNOPSIS πŸ¦‹

spi [-A] [-b] [-L] [-v] [-C command-bytes] [-c count] [-d r|w|rw]
    [-f device] [-m mode] [-s max-speed]
spi [-i] [-v] [-f device]
spi [-h]

three whole forms, no cap. pick your fighter. πŸŽ€


πŸ’– DESCRIPTION πŸ’–

so the spi utility is literally your bestie for doing raw data transfers (read, write, or simultaneous read/write) with devices on the SPI bus, and it does this through the spigen(4) device. iconic.

every spigen(4) device is tied to one specific "chip select" (cs) pin on the spibus, so like… you gotta say which one you want. and if you don't specify a device name on the command line, spi just assumes spigen0.0. default behavior, main character energy. πŸ‘‘

for more deets on the spigen device, go read spigen(4) β€” it's right there in SEE ALSO, iykyk.

the options are as follows:


🌈 OPTIONS 🌈

  • -A β€” Specifies ASCII mode. both read and write data is input and output as 2-character hexadecimal values, optionally separated by white space, like 00 01 02 etc. and when you combine it with the -b flag? the data on stdin stays a sequence of ASCII hexadecimal byte values, but the output reverts to binary mode. slay.
  • -b β€” Binary (output) mode. this only has an effect when -A has been specified. it reverts the output back to binary (rather than ASCII) while leaving the input format as-is. so use it in combination with -A to allow using something like echo to pass hexadecimal values to the SPI device, but output the received data on stdout as binary. chef's kiss. πŸ”₯
  • -C command-bytes β€” Sends one or more command bytes, skipping any bytes read-in during the transfer. the byte values should be specified as a quoted parameter, similar to the format for data on stdin for -A, that is, 2 character hexadecimal values, optionally separated by white space. an SPI device will typically require that a command be sent, followed by bytes of data. you can use this option to send the command without receiving any data bytes during the command sequence. no notes. ✨
  • -c count β€” The total number of bytes to transfer as a decimal integer. if a write or a read/write transaction is being performed, and fewer than this number of bytes are read in from stdin, the remaining bytes will be sent with a value of 0. and if the length can be determined from the input file size, you can use a count value of -1 to base the transfer on the input file's size. πŸ’–
  • -d r|w|rw β€” Transfer direction: use r for read, w for write, and rw for simultaneous read and write. pick your vibe. πŸ¦‹
  • -f device β€” SPI device to use (default is /dev/spigen0).
  • -h β€” Print help text to stderr, explaining the command line options. your little emergency exit. πŸ™ˆ
  • -i β€” Displays information about the SPI device to stderr. whenever this flag is specified, no data is read or written, and the mode and clock speed are not changed. so it's purely a vibe check, nothing more. πŸ‘€
  • -L β€” LSB bit order. the default is MSB, i.e., the highest order bit is transmitted first. specifying -L caused the LSB to be transmitted and read first. flip the script, literally. πŸ’…
  • -m 0|1|2|3 β€” SPI mode, 0 through 3. this defines the clock phase and timing with respect to reading and writing data, as per the SPI specification. ⭐
  • -s speed β€” Specify the maximum speed, in Hz, for the SPI clock. the bus will operate at its highest available speed which does not exceed this maximum. so it's a ceiling, not a promise. πŸŽ€
  • -v β€” Specifies Verbose mode. diagnostics and information are written to stderr. you can specify -v more than once to increase verbosity. πŸ—£οΈ

🌸 EXAMPLES 🌸

here are a few examples of using the spi utility, and honestly they eat:

  • Get information about the default SPI device
spi -i
  • Set the maximum clock speed to 200Khz and the mode to 3 on spigen0.1, but do not transmit nor receive any data
spi -f spigen0.1 -s 200000 -m 3
  • Send a command sequence consisting of 2 bytes, and read 2 additional bytes from the SPI device, using the current mode and speed on the default device
spi -d r -C "00 01" -c 2
  • Transmit a byte value of 5, and receive 2 bytes, displaying their values as 2-byte ASCII hexadecimal, with mode 2, and a maximum clock speed of 500khz.
echo "05" | spi -A -d rw -m 2 -s 500000 -c 2
  • Send a binary file, and output the SPI result through od(1) as hexadecimal bytes, using the current maximum clock speed and SPI mode.
spi -d rw -c -1 <input_file.bin | od -An -t x1
  • Send 2 bytes of data, receive a total of 4 bytes, and output the SPI result as binary data, piped through od(1), displaying it as two hexadecimal unsigned short integer values.
echo "00 01" | spi -A -b -d rw -c 4 | od -t x2
  • Query the manufacturer ID and size from a standard spiflash device, by sending the command byte 0x9f and displaying the 3-byte reply in ASCII hex.
spi -f spigen0.0 -m 0 -s 1000000 -d r -c 3 -A -C 9f

πŸ”₯ SEE ALSO πŸ”₯

spigen(4)


πŸ’œ HISTORY πŸ’œ

the spi utility appeared in FreeBSD 11.3. a little vintage moment, we love to see it. 🫢


and that's the whole page bestie!! this one's from the Debian manual set, dated August 21, 2020, and it's SPI(8) from the System Manager's Manual β€” go talk to your SPI devices, they're waiting πŸ’…βœ¨

πŸ“¦ where this page comes from