Hi LAVA folks,
I'm working on using LAVA to boot boards in my own board farm, and for
starters, am trying to use a job without a 'deploy' step (so I can use
the existing on-board u-boot, and control it via boot_cmds.)
Currently, the dispatcher assumes that a 'deploy' step has happened
before a 'boot_linaro_image' step, which is not needed for my case, so
here's a patch to set some defaults so a deploy step is not needed:
=== modified file 'lava_dispatcher/device/master.py'
--- lava_dispatcher/device/master.py 2013-04-30 11:45:15 +0000
+++ lava_dispatcher/device/master.py 2013-05-02 18:00:49 +0000
@@ -86,6 +86,10 @@
self.master_ip = None
self.device_version = None
+ # These defaults are needed in case no 'deploy' step is used
+ self.deployment_data['boot_cmds'] = 'boot_cmds'
+ self.deployment_data['TESTER_PS1_PATTERN'] = '# '
+
if config.pre_connect_command:
self.context.run_command(config.pre_connect_command)
For the curious, I've created a new "u-boot" device-type, Here's the config:
# Always hard reset to enter on-board u-boot
soft_boot_cmd = ~$hardreset
# u-boot commands
boot_cmds = version,
printenv,
boot,
# Default is 'Uncompressing Linux', but that doesn't exist anymore upstream
# The default should be probably be updated in
# default-config/lava-dispatcher/device-defaults.conf
image_boot_msg = Booting Linux
And added some devices with that device type.
Then I created a simple job to just boot my board using the u-boot
commands:
{
"device_type": "u-boot",
"actions": [
{
"command": "boot_linaro_image",
"parameters": {
"options": []
}
}
],
"timeout": 20000,
"job_name": "KJH dummy test"
}
The next step is to figure out how to use lava_test_shell on my targets
(not running a linaro master image) so I can run my tests.
Any pointers on how the requirements/setup for lava_test_shell on a non
master-image (also not android/OE/ubuntu/fedora.)
Kevin
_______________________________________________
linaro-validation mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/linaro-validation
