Peripherals
A bench learns what's attached to it from one YAML file, peripherals.yaml.
Each entry in the file declares one peripheral: which driver talks to it (its
kind), where to find it, and which interfaces to expose.
The configuration file page covers the structure every entry shares: the fields common to all drivers, how interfaces get their addresses, configs and setups, and validation. Each driver page below then lists the settings that one driver accepts. To deploy the file or switch setups, see Peripherals & interfaces.
Drivers
kind | Hardware | Interfaces |
|---|---|---|
linux-tty | USB-to-serial adapters, USB CDC devices, and on-board UARTs | UART, raw character device, interactive terminal (TTY) |
ftdi-ft232h | FTDI FT232H, FT2232H and FT4232H USB chips | SPI, GPIO, relay, UART, interactive terminal (TTY) |
mimick-hwi | MIMICK HWI v1 and v2 hardware interface boards | GPIO, relay, and on an HWI v2, UART and TTY |
relay-usb | CH340-based 4-channel USB relay board | Relay |
relay-esphome | Network relay board running ESPHome | Relay |
stepper-pd1180 | Trinamic PD-1180 (TMCM-1180) stepper motor module | Stepper |
network-interface | The bench's own Ethernet ports and WiFi radios | Ethernet, WiFi |
network-bridge | Two or more bench network ports joined into one network | Ethernet |
software | A container you supply that stands in for a hardware bus | Software (scripted read and write) |
One physical board can need more than one driver. The MIMICK HWI v1 board, for
example, carries its GPIO controller and three USB-to-UART bridges on one USB
hub: mimick-hwi drives the GPIO, and each UART is its own linux-tty entry.
The HWI v2 is a single USB device, so one mimick-hwi entry covers both its
GPIO and its DUT console.