Using multiple serial drivers from yaml environment #1259
Replies: 4 comments 11 replies
-
|
This is unfortunately not very clear from the documentation, but each driver supports a targets:
resources:
RemotePlace:
name: remote1
drivers:
SerialDriver:
name: 's1'
bindings:
port: default
SerialDriver:
name: 's2'
bindings:
port: secondWhere the named My example already contains a recent change to labgrid, namely that if Futher information for binding and driver activation is available inside the docs here. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Emantor, I followed your comment and used "add-named-match" to add two named NetworkSerialPort. But, the target.get_driver(‘SerialDriver’, name=name) still could not find the first named SerialDriver in the project yaml file. We have labgrid version 23.0.3 The resource “show" command output looks as follows: My project yaml file looks as follows: SerialDriver:
name: ‘a_uart_driver'
bindings:
port: ‘a_uart'
SerialDriver:
name: ‘b_uart_driver'
bindings:
port: ‘b_uart’ |
Beta Was this translation helpful? Give feedback.
-
|
@Emantor's configuration is incorrect. You need to specify the drivers as a yaml list, not as a yaml dictionary (the second SerialDriver would overwrite the first, due to duplicate keys). See the documentation about Environment configuration. It contains an example with multiple SerialDrivers. |
Beta Was this translation helpful? Give feedback.
-
|
@Bastian-Krause: Thanks for your help. I am following up on the configuration discussion for using one project YAML file for two serial port configurations. I did some more experiments. Labgrid accepts the project YAML file as follows (only for experiment purposes) targets:
main:
resources:
- RawSerialPort:
name: 'ca55_uart'
port: '/dev/ttys001'
- RawSerialPort:
name: 'cr5_uart'
port: '/dev/ttys002'
drivers:
- SerialDriver:
name: 'ca55_uart_driver'
bindings:
port: 'ca55_uart'
- SerialDriver:
name: 'cr5_uart_driver'
bindings:
port: 'cr5_uart'However, Labgrid would not take it if I add a ShellDriver entry in the file (it doesn’t matter if it is a list type or dictionary type): targets:
main:
resources:
- RawSerialPort:
name: 'ca55_uart'
port: '/dev/ttys001'
- RawSerialPort:
name: 'cr5_uart'
port: '/dev/ttys002'
drivers:
- SerialDriver:
name: 'ca55_uart_driver'
bindings:
port: 'ca55_uart'
- SerialDriver:
name: 'cr5_uart_driver'
bindings:
port: ‘cr5_uart'
ShellDriver:
prompt: '# '
login_prompt: ' login: '
username: 'root'
login_timeout: 30——————— - ShellDriver:
prompt: '# '
login_prompt: ' login: '
username: 'root'
login_timeout: 30My questions are as follows (Please correct me if I did not ask the right questions): For project YAML:
For exporter yaml
Project YAML resources:
RemotePlace:
name: L711
drivers:
- SerialDriver:
name: 'ca55_uart_driver'
bindings:
port: 'ca55_uart'
- SerialDriver:
name: 'cr5_uart_driver'
bindings:
port: 'cr5_uart'Exporter YAML file L711:
location: lab
ca55_uart:
cls: USBSerialPort
match:
ID_SERIAL_SHORT: FT4XSQFX
cr5_uart:
cls: USBSerialPort
match:
ID_SERIAL_SHORT: FT55R8PX
< some other resources>Please let me know and correct me if there are any missing setups on the exporter or project side. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, somehow the format of YAML was changed after clicking on the reply. |
Beta Was this translation helpful? Give feedback.
-
|
I think the real question we have is just this. If this is our exporter config: And our place is: And our test target yaml is: The How do we bind the ShellDriver to the ca55_uart_driver? |
Beta Was this translation helpful? Give feedback.
-
|
After much stepping through the labgrid code, I figured it out. The Strategy has both a console and a serial binding that are needed. This is the target yaml that works for the strategy now: It would sure be nice if the error messages from labgrid made this more clear! |
Beta Was this translation helpful? Give feedback.
-
|
Could you please provide a way to reproduce the error message that should be improved? |
Beta Was this translation helpful? Give feedback.
-
|
I guess to reproduce it you'd need a target env that has two SerialDrivers, and a driver or strategy that binds to a serial protocol. Then make sure you don't add It would be nice if it told me which driver or strategy is looking for the SerialDriver. Knowing what to look for now, I can see the strategy in the middle of the big traceback that is shown before the above message, but that was not obvious to me when first looking at this. |
Beta Was this translation helpful? Give feedback.
-
|
See #1270 for improved target error messages. |
Beta Was this translation helpful? Give feedback.
-
|
That looks like it will much more helpful, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Maybe it is of help to someone here. I have created a sample self-contained labgrid setup based on docker compose that uses two serial ports. There is just one Repository: https://github.com/honeytreelabs/labgrid-compose-sample Note: the |
Beta Was this translation helpful? Give feedback.
-
|
I am also trying to configure different My attempt with only the serials looks like this: targets:
main:
resources:
RemotePlace:
name: 'ex1-dut1'
drivers:
SerialDriver:
name: 'dbg_console'
bindings:
port: 'dbg'
SerialDriver:
name: 'tty_console'
bindings:
port: 'tty'
DemoStrategy: {}
imports:
- demo-strategy.pydemo_strategy.py: I get the following error: If I only use the following binding: or it works. As soon as I try to bind the HttpGpios, nothing works anymore. Can anyone help me with this? |
Beta Was this translation helpful? Give feedback.
-
For our labgrid configuration, we are running tests and hoping to use two serial connections on a remote lab host.
We would like to be able to run shell commands via the ShellDriver on each of these serial ports.
Our configuration is specified in our environment yaml file:
Reading through the documentation, it seems that labgrid supports multiple drivers with the same type, via the name parameter, and the
target.get_driver('SerialDriver', name=name)method can be used to get them individually.However, it is not stated how the underlying resources should be configured. We currently export two USBSerialPort resources with different paths from our RemotePlace, but when our Target is initialized, the second SerialDriver overwrites the first. We could also initialize these drivers in our code, as opposed to our yaml file, but there doesn't seem to be a way to distinguish between the resources they are using.
What should the configuration be to access two serial drivers on different ports from the same project?
Beta Was this translation helpful? Give feedback.
All reactions