This directory contains directly usable tools installable via go get periph.io/x/periph/cmd/....
Try first periph-info. It will print out if any driver failed to run, for
example if you have to run as root to access certain drivers.
Then run headers-list to list all the headers on your board and confirm that
you get the expected output. If your board is missing, you can contribute
it.
- apa102: Writes to a LED strip of APA-102 (sometimes called Dotstar). Can show an image animating on the Y axis.
- bme280: Reads the temperature, pressure and humidity off a bme280.
- ir: Reads codes (button presses) on an InfraRed remote sensor.
- led: Reads the state of on-board LEDs.
- ssd1306: Writes text, an image or an animated GIF to an OLED display.
- tm1637: Writes to a segment digits display.
- gpio-list: Looking for the GPIO pins per functionality? Prints the state of each GPIO pin.
- gpio-read: Read the input value of a GPIO pin and change input resistor.
- gpio-write: Change the output value of a GPIO pin.
- headers-list: Pinrts the location of the pin on the header to connect your GPIO. This is the perfect tool to know where to connect the wires.
- i2c-io: Reads and/or writes to an I²C device.
- i2c-list: Lists which I²C buses are enabled and where the pins are.
- spi-io: Reads and/or writes to an SPI device.
- spi-list: Lists which SPI buses are enabled and where the pins are.
- periph-info: Lists which periph drivers loaded and which failed.
- periph-smoketest: Runs one of the smoke test for the drivers. The smoke test differs from unit tests as they require real hardware to confirm that the driver being tested works.
Having getting the tools to run? See users/ for more documentation.