Got it.
But, let me make the problem more generic not just for adb fastboot.
If I have two methods to burn one device, and I have two device types, if possible for user to dynamic switch between two device types with only one device?
Regards, Larry
-----Original Message----- From: Neil Williams [mailto:neil.williams@linaro.org] Sent: Monday, December 10, 2018 4:47 PM To: Larry Shen larry.shen@nxp.com Cc: lava-users@lists.lavasoftware.org Subject: Re: [Lava-users] How to switch device-type base jinja with only one device?
On Mon, 10 Dec 2018 at 08:39, Larry Shen larry.shen@nxp.com wrote:
Dear all,
I have a question when use lava.
Background:
I have only one hardware device with android.I have a device-type jinja2 file start with “{% extends 'base-fastboot.jinja2' %}”Here, I use “adb reboot bootloader” to enter in to fastboot.
Avoid that at all costs. adb is not safe as a means of rebooting the device because it completely relies on the previous test job getting to the point where adb is even available *AND* is relies on the previous test job leaving adb even enabled in the deployed image. That kind of assumption will fail.
I have another device-type jinja2 file start with “{% extends 'base-uboot.jinja2' %}”Here, I use “fastboot 0” in uboot to enter in to fastboot.
You need remote power control which does not rely on adb.
Now, we have a scenario which need to test with above both methods, but we just have one device, if possible user can define some parameter in job.yaml, then can switch between the two methods just for one device? Any suggestion?
Drop the reliance on adb.
See the x15.jinja2 for a device-type which uses U-Boot to get to fastboot.