[imx8qmmek ][Jailhouse] Boot up with jh_mmcboot fail?

[WolsYang]

Image and u-boot file come from LF_v5.10.72-2.2.0_images_IMX8QMMEK.zip.

 BuildInfo: 
  - SCFW 549b1e18, SECO-FW 2f7f6f59, IMX-MKIMAGE 7a277c8a, ATF 5782363
  - U-Boot 2021.04-lf_v2021.04+g263b27e076 

Flash to imx8qmmek :

sudo ~/mfgtools/uuu/uuu -b emmc_all ~/Downloads/imx8/imx-boot-imx8qmmek-sd.bin-flash_linux_m4 ~/Downloads/imx8/imx-image-full-imx8qmmek.wic

Success 1    Failure 0                                                                                                                                                                                                                                                                                                                                     
3:4      8/ 8 [Done                                  ] FB: done    

 Go to u-boot:

Normal Boot
Hit any key to stop autoboot:  
jh_mmcboot=setenv fdt_file imx8qm-mek-root.dtb;setenv boot_os 'scu_rm dtb ${fdt_addr}; booti ${loadaddr} - ${fdt_addr};'; run mmcboot;
=> run jh_mmcboot

 And got fail:

Booting from mmc ...
106496 bytes read in 3 ms (33.9 MiB/s)
Loading hdp firmware from 0x000000009c000000 offset 0x0000000000002000
Loading hdp firmware Complete
136386 bytes read in 4 ms (32.5 MiB/s)
fdt addr 0000000083000000
partition_alloc: os_part, 7: parent_part, 6
sc_pm_set_resource_power_mode: resource:59 mode:0: res:4
Moving Image from 0x80280000 to 0x80400000, end=82150000
## Flattened Device Tree blob at 83000000
   Booting using the fdt blob at 0x83000000
   Using Device Tree in place at 0000000083000000, end 00000000830244c1
Disable jr@40000 rsrc 502 not owned
Disable mu@31580000 rsrc 505 not owned
Disable i2c@3b230000 rsrc 308 not owned
Disable clock-controller@3b630000 rsrc 308 not owned
Disable intmux@3b400000 rsrc 309 not owned
Disable clock-controller@5a480000 rsrc 59 not owned
Disable can@5a8d0000 rsrc 105 not owned
Disable can@5a8e0000 rsrc 106 not owned
Disable can@5a8f0000 rsrc 107 not owned
Disable clock-controller@5acd0000 rsrc 105 not owned
Disable clock-controller@5ace0000 rsrc 106 not owned
Disable clock-controller@5acf0000 rsrc 107 not owned
Disable mmc@5b010000 rsrc 248 not owned
Disable clock-controller@5b200000 rsrc 248 not owned
Disable spi@5d120000 rsrc 237 not owned
Disable imx8qm_cm4@0 rsrc 278 not owned
Disable imx8qm_cm4@0 rsrc 297 not owned
Disable imx8x_cm4@1 rsrc 298 not owned
Disable imx8x_cm4@1 rsrc 317 not owned

Starting kernel ...

"Synchronous Abort" handler, esr 0x02000000
elr: 000000007a65e000 lr : 0000000080021d08 (reloc)
elr: 0000000081c60000 lr : 0000000087623d08
x0 : 0000000083000000 x1 : 0000000000000000
x2 : 0000000000000000 x3 : 0000000000000000
x4 : 0000000080400000 x5 : 0000000000000001
x6 : 0000000000000008 x7 : 0000000000000000
x8 : 0000000084e0cf88 x9 : 0000000000000002
x10: 000000000a200023 x11: 0000000000000002
x12: 0000000000000002 x13: 0000000084e1fd76
x14: 0000000084e0dea0 x15: 000000008762322c
x16: 000000008765de54 x17: 0000000000000000
x18: 0000000084e1fd60 x19: 00000000876ea608
x20: 0000000000000000 x21: 0000000000000400
x22: 0000000000000003 x23: 0000000084e69e78
x24: 0000000000000003 x25: 0000000084e69e78
x26: 00000000876d3f98 x27: 0000000000000000
x28: 0000000084e69ea0 x29: 0000000084e0cfc0

Code: 676e696c 73657420 49282074 25205152 (000a2964) 
Resetting CPU ...

### ERROR ### Please RESET the board ###

 I also try yocto image, also got the same fail, anyone can help me?

[Bio_TICFSL]

Hello WolsYang,

Apparently you have problem with your board or there is no ready to boot form eMMC. Check if the boot switch is in correct position and download the correct images:

https://www.nxp.com/document/guide/get-started-with-the-i-mx-8quadmax-mek:GS-iMX-8QM-MEK

Regards

[WolsYang]

When I run normally boot it work fine.

Hit any key to stop autoboot:  0 
=>boot
switch to partitions #0, OK
mmc0(part 0) is current device
Failed to load 'boot.scr'
30118400 bytes read in 108 ms (266 MiB/s)
Booting from mmc ...
106496 bytes read in 3 ms (33.9 MiB/s)
Loading hdp firmware from 0x000000009c000000 offset 0x0000000000002000
Loading hdp firmware Complete
135667 bytes read in 4 ms (32.3 MiB/s)
Moving Image from 0x80280000 to 0x80400000, end=82150000
## Flattened Device Tree blob at 83000000
   Booting using the fdt blob at 0x83000000
   Using Device Tree in place at 0000000083000000, end 00000000830241f2
Disable jr@40000 rsrc 502 not owned
Disable mu@31580000 rsrc 505 not owned

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.10.72-lts-5.10.y+ga68e31b63f86 (oe-user@oe-host) (aarch64-poky-linux-gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.36.1.20210209) #1 SMP PREEMPT Tue Nov 23 06:02:20 UTC 2021
[    0.000000] Machine model: Freescale i.MX8QM MEK
[    0.000000] efi: UEFI not found.
[    0.000000] OF: fdt: Reserved memory: failed to reserve memory for node 'm4@0x88000000': base 0x0000000088000000, size 128 MiB
[    0.000000] Reserved memory: created CMA memory pool at 0x00000000c0000000, size 960 MiB

What I want to do is flash Root cell and inmates(JainHouse) or Dom0 and DomU(Xen) in the same emmc.

I think I have to do partition in UUU fastboot or  SCFW, but I can't find any doc.

I notice that  i.MX Linux® User's Guide, Rev. LF5.10.9_1.0.0, 31 March 2021 has Chapter 12
Virtualization but in i.MX Linux® User's Guide, Rev. LF5.10.72_2.2.0, 17 December 2021 did not show anymore, is that mean 5.10.72 does not support Virtualization？

[WolsYang]

Also, I notice that I don't have xl or jailhouse.

root@imx8qmmek:~# xl
-sh: xl: command not found
root@imx8qmmek:~# jailhouse
-sh: jailhouse: command not found
root@imx8qmmek:~# ls /lib/modules/5.10.72-lts-5.10.y+ga68e31b63f86/extra/
cryptodev.ko

But I have already added the following line in my build/local.conf

DISTRO_FEATURES_append = " jailhouse"
DISTRO_FEATURES_append = " xen"

[Bio_TICFSL · Accepted solution]

Hi,

Correct the 5.10.72 does not support virtualization, this already know form the developers and will fixed in next version.

Regards

[Peng_Fan]

Not very accurate. Jailhouse on i.MX8M* family is supported.

For the dump issue above on i.MX8QM, I could give a few suggestions to debug:

elr: 000000007a65e000 lr : 0000000080021d08 (reloc)
elr: 0000000081c60000 lr : 0000000087623d08
x0 : 0000000083000000 x1 : 0000000000000000
x2 : 0000000000000000 x3 : 0000000000000000
x4 : 0000000080400000 x5 : 0000000000000001
x6 : 0000000000000008 x7 : 0000000000000000
x8 : 0000000084e0cf88 x9 : 0000000000000002
x10: 000000000a200023 x11: 0000000000000002
x12: 0000000000000002 x13: 0000000084e1fd76
x14: 0000000084e0dea0 x15: 000000008762322c
x16: 000000008765de54 x17: 0000000000000000
x18: 0000000084e1fd60 x19: 00000000876ea608
x20: 0000000000000000 x21: 0000000000000400
x22: 0000000000000003 x23: 0000000084e69e78
x24: 0000000000000003 x25: 0000000084e69e78
x26: 00000000876d3f98 x27: 0000000000000000
x28: 0000000084e69ea0 x29: 0000000084e0cfc0

Code: 676e696c 73657420 49282074 25205152 (000a2964) 
Resetting CPU ...

 From the upper log, elr shows where the issue triggers, aarch64-poky-linux-objdump -D u-boot > u.s. find out the instruction, then see what the instruciton is doing, accessing which address, then locate to which registers, then see if it is scu_rm create partition cause this issue or not.