diff options
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 10 |
1 files changed, 8 insertions, 2 deletions
@@ -56,7 +56,7 @@ You will see it in the "All Jobs" list: http://localhost:10080/scheduler/alljobs To add a board you need to find its device-type, standard naming is to use the same as the official kernel DT name. (But a very few DUT differ from that) -You could check in https://github.com/Linaro/lava-server/tree/release/lava_scheduler_app/tests/device-types if you find yours. +You could check in https://github.com/Linaro/lava/tree/master/etc/dispatcher-config/device-types if you find yours. Example: For a beagleboneblack, the device-type is beaglebone-black (Even if official DT name is am335x-boneblack) @@ -332,7 +332,7 @@ boards: interfacenum: (optional) The interfacenumber of the serial. (Used with two serial in one device) use_conmux: True/False (Use conmux-console instead of ser2net) use_ser2net: True/False (Deprecated, ser2net is the default uart handler) - ser2net_options (optional) A list of ser2net options to add + ser2net_options: (optional) A list of ser2net options to add - option1 - option2 use_screen: True/False (Use screen via ssh instead of ser2net) @@ -355,6 +355,12 @@ Example: Bus 001 Device 054: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC ``` This device must use "0403" for idvendor and 6001 for idproduct. +* Some boards reset serial on power on. This can cause ser2net/telnet to disconnect resulting in the LAVA Worker being unable to program the board. This may be mitigated by passing LOCAL as an option to ser2net in the boards.yaml. +Example: +``` + ser2net_options: + - LOCAL +``` Note on connection_command: connection_command is for people which want to use other custom way than ser2net to handle the console. |