labgrid icon indicating copy to clipboard operation
labgrid copied to clipboard

embedded systems control library for development, testing and installation

Results 195 labgrid issues
Sort by recently updated
recently updated
newest added

**Description** - what do you use the feature for? Interactive use with `labgrid-client`. It's useful for bootloader development for processors with bootroms that load code from file systems (e.g. EFI...

enhancement
needs author info

**Description** Add dev-requirements and lib onewire to the labgrid-client image - [x] PR has been tested

enhancement
needs author info

**Description** Provides support for accessing Xilinx devices via JTAG: - `XilinxUSBJTAG` resource describing a Xilinx-compatible USB JTAG adapter - `VivadoHWServerExport` resource export, spawning a Vivado hardware server for each `XilinxUSBJTAG`...

enhancement

**Description** As discussed in #490 move `get_target_features()` from `Environment` to `Config`. Also add helpers for target options and features to `Target`. The pytest plugin uses the now deprecated `Environment.get_target_features()`. I...

**Description** The new SerialLoggingReporter and StepLoggingReporter output step information using the logging framework. This allows the user to configure the logging output and filtering by himself using the python logging...

Hi Labgrid, When connecting a coordinator from a far network location (i.e cloud instance), some times, a connection timeout happens producing test failures: > WARNING: dropping connection to peer tcp4:192.168.1.1:20408...

**Description** This pull requests has two important changes. 1) The ykush pypip implementation [2] lacks basic functionality like for example connect to several Yepkits via the serial number. Make sure...

needs author info

Closes https://github.com/labgrid-project/labgrid/issues/543 Rebased on: https://github.com/labgrid-project/labgrid/pull/575 Will rebase on master once that is merged. **Description** An iteration of the `getting started` page. The goal is to provide a step by step...

**Description** Make method args of `CommandProtocol`, `FileTransferProtocol` consistent/reflect driver reality. Now let drivers implementing protocols follow them strictly. This PR includes converting `run()`'s/`run_check()`'s `codec`/`decodeerrors` kwargs to driver attributes. **Checklist** -...

enhancement

**Description** The _CommandProtocol_ allows executing commands on the target. `CommandProtocol.run()` blocks until the process terminated and stdout/stderr/exit code are returned. Some use cases require non-blocking communication with the process because...

work in progress