On Tue, 6 Aug 2019 at 09:55, kingboli lijinbohehe@163.com wrote:

Hello LAVA experts,

I have a device which can boot up to android/linux. The device is connected with two USB cables. One USB cable is used for flashing images (fastboot flash) and doing some adb shell commands. Via another USB cable, I can use minicom to check uart logs and directly interact with the device (/dev/ttyUSB0).

This is how most of the fastboot devices are setup. Example device dict for hikey: https://validation.linaro.org/scheduler/device/hi6220-hikey-r2-01/devicedict Please note that per_power and pre_os commands are used to disconnect the OTG port (the one used for fastboot flashing) before booting the board.

Can you share some examples (jobs, job definitions) or configurations (like ser2net conf) or any suggestion for doing below test steps on my device with LAVA?

Scenario 1:

1. Flash images using fastboot
2. After android boots up or linux boots up, reboot and then stop at uboot

why would you boot to android if you want to test u-boot? In this case simply use 'bootloader' [1] type boot and run your u-boot tests using interactive test shell. Example job can be found here: https://validation.linaro.org/scheduler/job/1925569/definition

3. Do some tests in uboot.

Scenario 2:

1. Flash images using fastboot
2. After android boots up or linux boots up, interact with the device via uart (/dev/ttyUSB0) (suppose adb is disconnected)
3. Do some tests via uart.

This is default LAVA behavior. LAVA assumes there is some shell available in your OS. It will attempt to create proper overlay (set of shell scripts and test definitions) and execute tests on the target.

[1] https://master.lavasoftware.org/static/docs/v2/actions-boot.html?highlight=b...

milosz

Best regards, Kingboli

---

Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users