Unable to fastboot Android image
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
LAVA Dispatcher |
New
|
Undecided
|
Unassigned |
Bug Description
Hi,
I'm trying to bring up a standalone Lava instance to run tests on an OEM Android device. My first effort is to try and flash a local boot.img and system.img. From the bootloader trace in cn51-bootloader.txt I think that Lava can talk to the device using fastboot, but I don't think that all the actions in first.json are taken, or that Lava is aware when flashing the system partition has completed. If you take a look at first.json you'll see that there is an action to flash boot.img, but I don't see this being accomplished in the bootloader trace. The bootloader trace also shows that system.img flashed successfully, but Lava doesn't seem to be aware of this.
Can you please review the nexus01.conf and first.json. Perhaps something is just misconfigured.
Is there a way to increase the debug level?
I put the device into fastboot mode manually before starting the test.
If it helps, the Lava instance is able to run qemu.json successfully.
Thanks,
Bryan
<email address hidden>
Hi Bryan,
Your job looks file as well as your configuration. Two things to check here:
1) Does it take longer than 600 seconds to flash your system partition? There is a timeout of 600 second on each fastboot call.
2) Check dmesg for any usb related errors when flashing the system partition.
Cheers!