Release 0.3.4 (released Apr 1, 2021)

Bug Fixes in 0.3.4

  • Fix inclusion of the README file to support PyPi Uploads

Release 0.3.3 (released Apr 1, 2021)

Bug Fixes in 0.3.3

  • limit twisted version within crossbar-requirements.txt

  • the EthernetPort and SerialPort resources now properly raise their exceptions instead of only creating them

  • fixed docker cryptography failure during build

  • remove ports configuration from docker-compose.yml

  • add rsync to docker-client image

Known issues in 0.3.3

  • There are several reports of sshpass used within the SSHDriver not working in call cases or only on the first connection.

  • Some client commands return 0 even if the command failed.

  • Currently empty passwords are not well supported by the ShellDriver

Release 0.3.2 (released Mar 14, 2021)

Bug Fixes in 0.3.2

  • Fix for exporter baud rate handling which prevented ser2net from starting.

Known issues in 0.3.2

  • There are several reports of sshpass used within the SSHDriver not working in call cases or only on the first connection.

  • Some client commands return 0 even if the command failed.

  • Currently empty passwords are not well supported by the ShellDriver

Release 0.3.1 (released Feb 5, 2021)

Bug Fixes in 0.3.1

  • Fixes a typo in labgrid-bound-connect, which should re-enable connection proxying for SSH.

  • Man-Pages have been correctly regenerated.

  • The exporter correctly handles the configured baud-rate for serial ports again.

  • Various tests have been marked with skips if the modules are not available.

  • Docker files have been moved to from the docker directory to the dockerfiles directory, which prevents the tests from incorrectly assuming a docker module is available.

Release 0.3.0 (released Jan 22, 2021)

New Features in 0.3.0

  • All CommandProtocol drivers support the poll_until_success method.

  • The new FileDigitalOutputDriver respresents a digital signal with a file.

  • The new GpioDigitalOutputDriver controls the state of a GPIO via the sysfs interface.

  • Crossbar and autobahn have been updated to 19.3.3 and 19.3.5 respectively.

  • The InfoDriver was removed. The functions have been integrated into the labgridhelper library, please use the library for the old functionality.

  • labgrid-client write-image subcommand: labgrid client now has a write-image command to write images onto block devices.

  • labgrid-client ssh now also uses port from NetworkService resource if available

  • The PLACE and STATE variables used by labgrid-client are replaced by LG_PLACE and LG_STATE, the old variables are still supported for the time being.

  • The SSHDriver’s keyfile attribute is now specified relative to the config file just like the images are.

  • The ShellDriver’s keyfile attribute is now specified relative to the config file just like the images are.

  • labgrid-client -P <PROXY> and the LG_PROXY enviroment variable can be used to access the coordinator and network resources via that SSH proxy host. Drivers which run commands via SSH to the exporter still connect directly, allowing custom configuration in the user’s .ssh/config as needed. Note that not all drivers have been updated to use the ProxyManager yet.

  • Deditec RELAIS8 devices are now supported by the DeditecRelaisDriver.

  • The RKUSBDriver was added to support the rockchip serial download mode.

  • The USBStorageDriver gained support for BMAP.

  • Flashrom support added, by hard-wiring e.g. an exporter to the DUT, the ROM on the DUT can be written directly. The flashrom driver implements the bootstrap protocol.

  • AndroidFastbootDriver now supports ‘getvar’ and ‘oem getenv’ subcommands.

  • The coordinator now updates the resource acquired state at the exporter. Accordingly, the exporter now starts ser2net only when a resources is aquired. Furthermore, resource conflicts between places are now detected.

  • Labgrid now uses the ProcessWrapper for externally called processes. This should include output from these calls better inside the test runs.

  • The binding dictionary can now supports type name strings in addition to the types themselves, avoiding the need to import a specific protocol or driver in some cases.

  • The remote infrastructure gained support for place reservations, for further information check the section in the documentation.

  • The SigrokDriver gained support for the Manson HCS-2302, it allows enabling and disabling channels, measurement and setting the current and voltage limit.

  • labgrid-client write-image gained new arguments: --partition, --skip, --seek.

  • Support for Sentry PDUs has been added.

  • Strategies now implement a force method, to force a strategy state irrespective of the current state.

  • SSH Connections can now be proxied over the exporter, used by adding a device suffix to the NetworkService address.

  • UBootDriver now allows overriding of default boot command (run bootcmd) via new boot_command argument.

  • The config file supports per-target options, in addition to global options.

  • Add power driver to support GEMBIRD SiS-PM implementing SiSPMPowerDriver.

  • A cleanup of the cleanup functions was performed, labgrid should now clean up after itself and throws an error if the user needs to handle it himself.

  • labgrid-client now respects the LG_HOSTNAME and LG_USERNAME environment variables to set the hostname and username when accessing resources.

  • PyVISA support added, allowing to use PyVISA controlled test equipment from Labgrid.

  • labgrid-client write-image gained a new argument --mode to specify which tool should be used to write the image (either dd or bmaptool)

  • Exporter configuration file exporter.yaml now allows use of environment variables.

Breaking changes in 0.3.0

  • ManagedFile now saves the files in a different directory on the exporter. Previously /tmp was used, labgrid now uses /var/cache/labgrid. A tmpfiles example configuration for systemd is provided in the /contrib directory. It is also highly recommended to enable fs.protected_regular=1 and fs.protected_fifos=1 for kernels>=4.19. This requires user intervention after the upgrade to create the directory and setup the cleanup job.

  • @attr.s(cmp=False) is deprecated and all classes have been moved to @attr.s(eq=False), this release requires attrs version 19.2.0

  • Coordinator work dir is now set to the same dir as the crossbar configuration dir. Hence coordinator specific files like places.yaml and resources.yaml are now also stored in the crossbar configuration folder. Previously it would use ...

  • The HawkbitTestClient and USBStick classes have been removed

  • The original USBStorageDriver was removed, NetworkUSBStorageDriver was renamed to USBStorageDriver. A deprecated NetworkUSBStorageDriver exists temporarily for compatibility reasons.

Known issues in 0.3.0

  • There are several reports of sshpass used within the SSHDriver not working in call cases or only on the first connection.

  • Some client commands return 0 even if the command failed.

  • Currently empty passwords are not well supported by the ShellDriver

Release 0.2.0 (released Jan 4, 2019)

New Features in 0.2.0

  • A colored StepReporter was added and can be used with pytest --lg-colored-steps.

  • labgrid-client can now use the last changed information to sort listed resources and places.

  • labgrid-client ssh now uses ip/user/password from NetworkService resource if available

  • The pytest plugin option --lg-log enables logging of the serial traffic into a file (see below).

  • The environement files can contain feature flags which can be used to control which tests are run in pytest.

  • LG_* variables from the OS environment can be used in the config file with the !template directive.

  • The new “managed file” support takes a local file and synchronizes it to a resource on a remote host. If the resource is not a NetworkResource, the local file is used instead.

  • ProxyManager: a class to automatically create ssh forwardings to proxy connections over the exporter

  • SSHManager: a global manager to multiplex connections to different exporters

  • The target now saves it’s attached drivers, resources and protocols in a lookup table, avoiding the need of importing many Drivers and Protocols (see Syntactic sugar for Targets)

  • When multiple Drivers implement the same Protocol, the best one can be selected using a priority (see below).

  • The new subcommand labgrid-client monitor shows resource or places changes as they happen, which is useful during development or debugging.

  • The environment yaml file can now list Python files (under the ‘imports’ key). They are imported before constructing the Targets, which simplifies using custom Resources, Drivers or Strategies.

  • The pytest plugin now stores metadata about the environment yaml file in the junit XML output.

  • The labgrid-client tool now understands a --state option to transition to the provided state using a Strategy. This requires an environment yaml file with a RemotePlace Resources and matching Drivers.

  • Resource matches for places configured in the coordinator can now have a name, allowing multiple resources with the same class.

  • The new Target.__getitem__ method makes writing using protocols less verbose.

  • Experimental: The labgrid-autoinstall tool was added (see below).

New and Updated Drivers

  • The new DigitalOutputResetDriver adapts a driver implementing the DigitalOutputProtocol to the ResetProtocol.

  • The new ModbusCoilDriver support outputs on a ModbusTCP device.

  • The new NetworkUSBStorageDriver allows writing to remote USB storage devices (such as SD cards or memory sticks connected to a mux).

  • The new QEMUDriver runs a system image in QEmu and implements the ConsoleProtocol and PowerProtocol. This allows using labgrid without any real hardware.

  • The new QuartusHPSDriver controls the “Quartus Prime Programmer and Tools” to flash a target’s QSPI.

  • The new SerialPortDigitalOutputDriver controls the state of a GPIO using the control lines of a serial port.

  • The new SigrokDriver uses a (local or remote) device supported by sigrok to record samples.

  • The new SmallUBootDriver supports the extremely limited U-Boot found in cheap WiFi routers.

  • The new USBSDMuxDriver controls a Pengutronix USB-SD-Mux device.

  • The new USBTMCDriver can fetch measurements and screenshots from the “Keysight DSOX2000 series” and the “Tektronix TDS 2000 series”.

  • The new USBVideoDriver can stream video from a remote H.264 UVC (USB Video Class) camera using gstreamer over SSH. Currently, configuration for the “Logitech HD Pro Webcam C920” exists.

  • The new XenaDriver allows interacting with Xena network testing equipment.

  • The new YKUSHPowerDriver and USBPowerDriver support software-controlled USB hubs.

  • The bootloader drivers now have a reset method.

  • The BareboxDriver’s boot string is now configurable, which allows it to work with the quiet Linux boot parameter.

  • The IMXUSBLoader now recognizes more USB IDs.

  • The OpenOCDDriver is now more flexible with loading configuration files.

  • The NetworkPowerDriver now additionally supports:

    • 24 port “Gude Expert Power Control 8080”

    • 8 port “Gude Expert Power Control 8316”

    • NETIO 4 models (via telnet)

    • a simple REST interface

  • The SerialDriver now supports using plain TCP instead of RFC 2217, which is needed from some console servers.

  • The ShellDriver has been improved:

    • It supports configuring the various timeouts used during the login process.

    • It can use xmodem to transfer file from and to the target.

Incompatible Changes

  • When using the coordinator, it must be upgrade together with the clients because of the newly introduce match names.

  • Resources and Drivers now need to be created with an explicit name parameter. It can be None to keep the old behaviour. See below for details.

  • Classes derived from Resource or Driver now need to use @attr.s(cmp=False) instead of @attr.s because of a change in the attrs module version 17.1.0.

Syntactic sugar for Targets

Targets are now able to retrieve requested drivers, resources or protocols by name instead of by class. This allows removing many imports, e.g.

from labgrid.driver import ShellDriver

shell = target.get_driver(ShellDriver)


shell = target.get_driver("ShellDriver")

Also take a look at the examples, they have been ported to the new syntax as well.

Multiple Driver Instances

For some Protocols, it is useful to allow multiple instances.


A board may have two jumpers to control the boot mode in addition to a reset GPIO. Previously, it was not possible to use these on a single target.


Some boards have multiple console interfaces or expose a login prompt via a USB serial gadget.


In some cases, multiple power ports need to be controlled for one Target.

To support these use cases, Resources and Drivers must be created with a name parameter. When updating your code to this version, you can either simply set the name to None to keep the previous behaviour. Alternatively, pass a string as the name.


>>> t = Target("MyTarget")
>>> SerialPort(t)
SerialPort(target=Target(name='MyTarget', env=None), state=<BindingState.bound: 1>, avail=True, port=None, speed=115200)
>>> SerialDriver(t)
SerialDriver(target=Target(name='MyTarget', env=None), state=<BindingState.bound: 1>, txdelay=0.0)

New (with name=None):

>>> t = Target("MyTarget")
>>> SerialPort(t, None)
SerialPort(target=Target(name='MyTarget', env=None), name=None, state=<BindingState.bound: 1>, avail=True, port=None, speed=115200)
>>> SerialDriver(t, None)
SerialDriver(target=Target(name='MyTarget', env=None), name=None, state=<BindingState.bound: 1>, txdelay=0.0)

New (with real names):

>>> t = Target("MyTarget")
>>> SerialPort(t, "MyPort")
SerialPort(target=Target(name='MyTarget', env=None), name='MyPort', state=<BindingState.bound: 1>, avail=True, port=None, speed=115200)
>>> SerialDriver(t, "MyDriver")
SerialDriver(target=Target(name='MyTarget', env=None), name='MyDriver', state=<BindingState.bound: 1>, txdelay=0.0)


Each driver supports a priorities class variable. This allows drivers which implement the same protocol to add a priority option to each of their protocols. This way a NetworkPowerDriver can implement the ResetProtocol, but if another ResetProtocol driver with a higher protocol is available, it will be selected instead. See the documentation for details.

ConsoleLogging Reporter

The ConsoleLoggingReporter can be used with the pytest plugin or the library. It records the Data send from a DUT to the computer running labgrid. The logfile contains a header with the name of the device from the environment configuration and a timestamp.

When using the library, the reporter can be started with:

from labgrid.consoleloggingreporter import ConsoleLoggingReporter


where “.” is the output directory.

The pytest plugin accepts the --lg-log commandline option, either with or without an output path.

Auto-Installer Tool

To simplify using labgrid for provisioning several boards in parallel, the labgrid-autoinstall tool was added. It reads a YAML file defining several targets and a Python script to be run for each board. Interally, it spawns a child process for each target, which waits until a matching resource becomes available and then executes the script.

For example, this makes it simple to load a bootloader via the BootstrapProtocol, use the AndroidFastbootDriver to upload a kernel with initramfs and then write the target’s eMMC over a USB Mass Storage gadget.


labgrid-autoinstall is still experimental and no documentation has been written.

Contributions from: Ahmad Fatoum, Bastian Krause, Björn Lässig, Chris Fiege, Enrico Joerns, Esben Haabendal, Felix Lampe, Florian Scherf, Georg Hofmann, Jan Lübbe, Jan Remmet, Johannes Nau, Kasper Revsbech, Kjeld Flarup, Laurentiu Palcu, Oleksij Rempel, Roland Hieber, Rouven Czerwinski, Stanley Phoong Cheong Kwan, Steffen Trumtrar, Tobi Gschwendtner, Vincent Prince

Release 0.1.0 (released May 11, 2017)

This is the initial release of labgrid.