Unable to fastboot Android image

Bug #1329616 reported by Bryan Bavaro
6
This bug affects 1 person
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>

Revision history for this message
Bryan Bavaro (bryan-bavaro) wrote :
Revision history for this message
Tyler Baker (tyler-baker) wrote :

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!

Revision history for this message
Bryan Bavaro (bryan-bavaro) wrote : Re: [Bug 1329616] Unable to fastboot Android image

Thanks Tyler!

I tried flashing outside of Lava and the dmesg is showing a USB related error from fastboot when trying the system partition. Any idea why the boot partition doesn’t even download?

Bryan

On Jun 14, 2014, at 2:17 AM, Tyler Baker <email address hidden> wrote:

> 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!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1329616
>
> Title:
> Unable to fastboot Android image
>
> Status in LAVA Dispatcher:
> New
>
> 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>
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/lava-dispatcher/+bug/1329616/+subscriptions

This message is intended only for the named recipient. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action based on the contents of this information is strictly prohibited.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.