On Wed, 16 Mar 2016 17:02:25 +0800 "C.H Wu" <kkbom...@gmail.com> wrote:
> Dear Neil and Linaro validation support team, > > > > The tools you use will depend on your particular lab. ser2net is > > common and flexible for serial connections, many labs would find it > > much better than using sg or screen. tftp transmission typically > > does not need to be configured - the tftpd-hpa package is installed > > by lava-dispatcher dependencies and can be used as-installed. > > > > Thank you for provided these tutorial video, and I've installed > virtual device (e.g. kvm ) in my lava instance and some basic yaml > test file in lava_test_shell. Can you submit and run test jobs on that device? > But I still could not install these test into physical devices, What devices? what type of devices are you trying to test? Are you using V1 dispatcher (JSON jobs)? Do you have any devices which are currently supported by LAVA, e.g. beaglebone-black, pandaboard or cubietruck? > I wonder could it possible to bypass the deploy_image / boot steps, > and run test directly. This is usually a bad idea. > To test the ser2net connection, I've edited the /etc/ser2net.conf and > device.conf > , and connected to the device via lava connect <device> successfully. So the device configuration for connecting to the device is correct. > And other actions reminded to deploy the image, > so I've tried 'dummy_deploy' in the job definition, but it still > could not install 'test' into device. What do you mean by 'test' - a test definition YAML file from a git repository? > I'm not sure is there anything that I forgot to notice.. You can attach your job definition and device configuration to a reply to this list. > And could you provide some basic device.conf and job definition that > could bypass the deploy / boot image steps . "put file" and "get file" are not useful, you need to use LAVA to deploy files onto the device - these are *not* sent over the serial line, it is just too unreliable and slow. e.g. A UBoot device would get these files via TFTP. Working with TFTP in LAVA means using a bootloader type device and passing the URL of the kernel, dtb & rootfs to a deploy stage, followed by a boot stage which passes the commands to UBoot. Something like this: https://staging.validation.linaro.org/scheduler/job/142365/definition or this: https://staging.validation.linaro.org/scheduler/job/142390/definition The device type configuration for this device is: https://git.linaro.org/lava/lava-lab.git/blob/HEAD:/staging.validation.linaro.org/lava/device-types/beaglebone-black.conf The device configuration for a device like this is: https://git.linaro.org/lava/lava-lab.git/blob/HEAD:/staging.validation.linaro.org/lava/devices/staging01.lavalab/staging-black01.conf -- Neil Williams ============= http://www.linux.codehelp.co.uk/
pgp0S55MVJUmt.pgp
Description: OpenPGP digital signature
_______________________________________________ linaro-validation mailing list linaro-validation@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-validation
