iMX8QM Android Automotive OS 12.0.0_2.1.0 XEN U-Boot Error

[cbl]

Hello,

I want to run Android Automotive OS 12.0.0_2.1.0 and my Yocto image on XEN Hypervisor.

Android I compiled the Android OS 12.0.0_2.1.0 image.

I wrote the image to my iMX8QM MEK EVK board with the command "sudo ./uuu_imx_android_flash.sh -f imx8qm -u xen -d xen -e -y imx-image-full.wic".

When I enter "run xenmmcboot" command in U-Boot, I get "unknown command" error.

The U-Boot log is as follows.

U-Boot Log:
U-Boot SPL 2022.04 (Dec 07 2022 - 13:05:45 +0300)
Normal Boot
Trying to boot from MMC2_2
Primary set selected
Load image from MMC/SD 0x6d800
RPMB key is not set.
MMC: block number 0x4000 exceeds max(0x0)
Failed to read rpmbkeyblob.UU
boot args 0x2000000 0xfe000000 0x2000 0x0
initializing trusty (Project: imx8qm, Built: 10:11:37 May 30 2022)
Core: 183 devices, 29 uclasses, devicetree: separate
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... *** Warning - bad CRC, using default environment

[*]-Video Link 0it6263_i2c_reg_read, read err 3
faill to read from it6263 revision, ret 3
(1280 x 720)
[0] dpu@56180000, video
[1] lvds-channel@0, display
[2] lvds-to-hdmi-bridge@4c, video_bridge
In: serial
Out: serial
Err: serial

BuildInfo:
- SCFW 8172eaea, SECO-FW c9de51c0, IMX-MKIMAGE a8bb8edb, ATF 44c44f0
- U-Boot 2022.04

flash target is MMC:1
Net:
Warning: ethernet@5b040000 (eth0) using random MAC address - d6:0f:25:55:43:87
eth0: ethernet@5b040000 [PRIME]
Warning: ethernet@5b050000 (eth1) using random MAC address - c2:69:ed:80:81:e5
, eth1: ethernet@5b050000
INFO Initializing Trusty device
INFO selected trusty api version: 3 (requested 3)
INFO Initializing Trusty IPC device
INFO Initializing RPMB storage proxy service
read counter: Bad response type, 0x2, expected 0x200
read counter: Bad response type, 0x2, expected 0x200
read counter: Bad response type, 0x2, expected 0x200
failed to read rpmb write counter
read data: Bad response type, 0x4, expected 0x400
ss: block_device_tipc_init: bad static rpmb size, 2048
ss: proxy_connect: block_device_tipc_init failed (-1)
INFO Initializing Trusty Hardware Crypto client
cannot get the partion info for misc
idx 0, ptn 0 name='gpt' start=0 len=2048
idx 1, ptn 0 name='' start=0 len=0
idx 2, ptn 0 name='all' start=0 len=62333952
idx 3, ptn 0 name='bootloader0' start=64 len=8192
Cannot find partition 4080
do_raw_read failed, ret 1
read_bootctl, bcb_rw_block read failed
read command failed
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
=> printenv
baudrate=115200
board_name=MEK
board_rev=iMX8QM
bootcmd=boota mmc1
bootdelay=3
commit_atf=44c44f0
commit_mkimage=a8bb8edb
commit_scfw=8172eaea
commit_secofw=c9de51c0
eth1addr=c2:69:ed:80:81:e5
ethact=ethernet@5b040000
ethaddr=d6:0f:25:55:43:87
ethprime=eth0
fastboot_dev=mmc1
fdt_high=0xffffffffffffffff
fdtcontroladdr=fb1f4e90
initrd_high=0xffffffffffffffff
loadaddr=0x80200000
sec_boot=no
serial#=0514200e82964887
soc_rev=revb
soc_type=imx8qm
splashpos=m,m

Environment size: 460/8188 bytes
=>

I don't know how to activate XEN with Android Automotive OS 12.0.0_2.1.0.

Could you please help with this issue?

Best regards,

Efecan

[hector_delgado]

Hi @cbl ,

For running Xen on Android Automotive 12, please review Section 6 Booting from the Android Auto User's Guide. Specifically Section 6.2.2 where Kernel Boot Parameters are described. You must set the bootargs parameter that enables xen (androidboot.xen_boot).

androidboot.xen_boot must be set like this:

androidboot.xen_boot=xen

to switch the environment in which Android Automotive works at to Xen environment.

Let me know if this was of any help.

Best regards,
Hector.

[cbl]

Hello @hector_delgado,

I added the "BOARD_KERNEL_CMDLINE += androidboot.xen_boot=xen" parameter to the "BoardConfig.mk" file located in the "imx-automotive-12.0.0_2.1.0/android_build/device/nxp/imx8q/mek_8q" directory and got the build again.

However, there was no change.

I still get "unknown command" error when I run "run xenmmcboot" on U-Boot.

What else should I do to integrate XEN in Android Automotive OS 12.0.0_2.1.0?

Best regards,

Efecan

[hector_delgado · Accepted solution]

Hi @cbl ,

XEN is currently only tested in Android 13 (non-Auto) and U-Boot doesn't have the appropriate XEN commands, which is why you're getting the errors mentioned earlier. I'd suggest changing the U-Boot or migrating from Android completely to ensure XEN compatibility.

Best regards,
Hector.