Although we can't opt-out A/B (because bootloader is built with
CONFIG_ANDROID_AB), but we can delete the unused 'b' slot as the update
of microdroid is not done by writing into the disk, but updating the
virt APEX that has the microdroid image.
Bug: N/A
Test: atest MicrodroidHostTestCases
Change-Id: Ie5871bf1b665e2cc564af54338043ae482ca01bb
misc.img was needed by the uboot bootloader that microdroid is using.
The bootloader uses the partition to read the boot mode (normal,
recovery, and bootloader) that is set during the previous boot.
However, boot mode doesn't make sense for microdroid. So we delete it.
Unfortunately, deleting it is not trivial because uboot demands us to
anyway provide the location of the misc partition with the
`boot_android` command.
This change works around the restriction by letting the bootloader use
the first partition (which currently is the boot_a partition) as the
misc partition. We do that by giving only the disk number (0) and not
the partition name (as in 0#misc). Then uboot by default chooses the
first partition as the misc partition, and find that it is not a correct
misc partition. In that case, it falls back to the 'normal' boot which
we want.
Bug: 191131043
Test: atest MicrodroidHostTestCases
Change-Id: If2e49d1da9f75c805bc0d0f33e3f221b12dd220e
This CL includes x86_64 specific changes that are required to run
microdroid on cuttlefish_x86_64.
1) Unsigned bootloader is used. (b/185115783)
2) androidboot.boot_devices is correctly set for the architecture
3) uboot-env.txt is customized to set loadaddr
4) MicrodroidTestCase is revised to handle the case when multiple
devices are connected.
Bug: 185115783
Bug: 185082754
Test: atest MicrodroidHostTests with aosp_cf_x86_64_phone
Change-Id: I1baebedd392f742f9a9cd064d63a8c3741e46daa
Jiyong Park