labgrid-project / labgrid-project/labgrid
Labgrid for parallel target testing
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 528
- Forks
- 278
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 4
Description
I've been evaluating labgrid for use in a new parallel hardware testing system. Unfortunately there are two main features that don't seem to be currently supported that would be required for our project:
- Multiple driver/resource instances on a single target
This is listed as planned feature in the docs so I assume it's already being looked into. The use case I've been looking at is using a serial port for communication with the UUT and a second serial port for communication with a separate power control board. It might be possible to work around this by creating new resource/driver classes for the second device, but this does not seem like a good solution. - Shared driver instances between multiple targets
The power control board I mentioned above has multiple relays to control multiple target boards. I do not think it is currently possible to share a single serial device between boards like this, since bound resources/drivers cannot be controlled by another target.
Are these features planned to be supported?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the documentation's planned feature for multiple driver/resource instances, then trace how bound resources and drivers relate to targets. Determine whether the design can support multiple instances on one target and shared driver instances across targets; done requires a documented decision or implementation plan for both use cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- embedded-iot, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100