[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] RT Xen on ARM - R-Car series

Andrii,

YEY!

I have finally got an error message!

The rest of the mail is inline.

2019年1月28日(月) 17:25 Andrii Anisov <andrii.anisov@xxxxxxxxx>:
Hello Jairo,

On 28.01.19 19:20, LOPEZ, FUENTES NACARINO Jairo Eduardo wrote:

> I was able to compile the Xen image with earlyprintk without issue.

Cool.

> It is comforting to get some sort of feedback from the device, even if it is failing.

Indeed:)

> When attempting to boot the Xen image created I did get print messages but I get the following:
...

I see you have freshly built BL2:

> [    0.120591] NOTICE:  BL2: v1.4(release):15dba6b
> [    0.125081] NOTICE:  BL2: Built : 11:34:26, Jan 21 2019
...
> - UART enabled -
> - CPU 00000000 booting -
> - Current EL 00000004 -
> - Xen must be entered in NS EL2 mode -

But something went wrong, and your BL2 did not start u-boot in EL2. Consequently, hypervisor is not started in EL2 and can not do its work.
Please verify you have your ATF built with ` RCAR_BL33_EXECUTION_EL=BL33_EL2` as it is stated in the correspondent recipe [1].
You can search for it in <yocto dir>/build/tmp/work/<board name>-poky-linux/v1.4+renesas+<revision>/tmp/* .
And if it is compiled with the flag, then take care to reflash all bootloader images on your board.

[1] https://github.com/xen-troops/meta-demo/blob/master/meta-rcar-gen3-xen/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_git.bbappend

--
Sincerely,
Andrii Anisov.


As you mentioned, I checked the ATF build at the following path:

<yocto dir>/build/tmp/work/<board name>-poky-linux/arm-trusted-firmware/v1.4+renesas+<revision>/temp

Much to my surprise I found no trace of thr RCAR_BL33_EXECUTION_EL=BL33_EL2.

It seems that at some point in time I removed the Xen troops meta-demo layer which nullified the ATFW_OPT_append in that layer.

I was able to readjust the layers and check that the compilation included the necessary ATF option.

After a successful u-boot firmware update, I was met with the following information on the R-Car M3:

[    0.000191] NOTICE:  BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.21
[    0.005753] NOTICE:  BL2: PRR is R-Car M3 Ver.1.0
[    0.010422] NOTICE:  BL2: Board is Starter Kit Rev.1.0
[    0.015534] NOTICE:  BL2: Boot device is HyperFlash(80MHz)
[    0.020960] NOTICE:  BL2: LCM state is CM
[    0.025002] NOTICE:  BL2: AVS setting succeeded. DVFS_SetVID=0x53
[    0.030989] NOTICE:  BL2: DDR3200(rev.0.33)NOTICE:  [COLD_BOOT]NOTICE:  ..0
[    0.086113] NOTICE:  BL2: DRAM Split is 2ch
[    0.089998] NOTICE:  BL2: QoS is default setting(rev.0.19)
[    0.095502] NOTICE:  BL2: Lossy Decomp areas
[    0.099675] NOTICE:       Entry 0: DCMPAREACRAx:0x80000540 DCMPAREACRBx:0x570
[    0.106760] NOTICE:       Entry 1: DCMPAREACRAx:0x40000000 DCMPAREACRBx:0x0
[    0.113672] NOTICE:       Entry 2: DCMPAREACRAx:0x20000000 DCMPAREACRBx:0x0
[    0.120586] NOTICE:  BL2: v1.4(release):15dba6b
[    0.125076] NOTICE:  BL2: Built : 14:48:12, Jan 29 2019
[    0.130264] NOTICE:  BL2: Normal boot
[    0.133909] NOTICE:  BL2: dst=0xe6320d00 src="" len=512(0x200)
[    0.140292] NOTICE:  BL2: dst=0x43f00000 src="" len=6144(0x1800)
[    0.146913] NOTICE:  BL2: dst=0x44000000 src="" len=65536(0x10000)
[    0.154144] NOTICE:  BL2: dst=0x44100000 src="" len=1048576(0x100000)
[    0.168967] NOTICE:  BL2: dst=0x50000000 src="" len=1048576(0x100000)


U-Boot 2015.04 (Jan 21 2019 - 20:33:02)

CPU: Renesas Electronics R8A7796 rev 1.0
Board: M3ULCB
I2C:   ready
DRAM:  1.9 GiB
Bank #0: 0x048000000 - 0x07fffffff, 896 MiB
Bank #1: 0x600000000 - 0x63fffffff, 1 GiB

MMC:   sh-sdhi: 0, sh-sdhi: 1
In:    serial
Out:   serial
Err:   serial
Net:   ravb

First, it is nice to know where to look for the build time for the BL2!

After loading earlyprintk enabled Xen and the 4.14 Linux kernel from Yocto 3.9, I was met with the following output:

Starting kernel ...

- UART enabled -
- CPU 00000000 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Zero BSS -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) Checking for initrd in /chosen
(XEN) RAM: 0000000048000000 - 000000007fffffff
(XEN) RAM: 0000000600000000 - 000000063fffffff
(XEN) RAM: 0000000600000000 - 000000063fffffff
(XEN)
(XEN) MODULE[0]: 0000000048000000 - 0000000048011000 Device Tree
(XEN) MODULE[1]: 000000007a000000 - 000000007c000000 Kernel     
(XEN)  RESVD[0]: 0000000048000000 - 0000000048011000
(XEN)
(XEN)
(XEN) Command line: dom0_mem=752M console=dtuart dtuart=serial0 dom0_max_vcpus=4
(XEN) PFN compression on bits 19...20
(XEN) Xen BUG at page_alloc.c:274
(XEN) ----[ Xen-4.12.0-rc  arm64  debug=y   Not tainted ]----
(XEN) CPU:    0
(XEN) PC:     000000000028b310 page_alloc.c#bootmem_region_add+0x188/0x198
(XEN) LR:     000000000028b370
(XEN) SP:     00000000002d7d00
(XEN) CPSR:   800003c9 MODE:64-bit EL2h (Hypervisor, handler)
(XEN)      X0: 0000000000600000  X1: 0000000000000003  X2: 0000000000000004
(XEN)      X3: 0000000000640000  X4: 0000800008011000  X5: 0000000000000028
(XEN)      X6: 0000000000600000  X7: 0000000000000004  X8: 0000000000000001
(XEN)      X9: 000000000000000a X10: 00000000002d7afa X11: 0000000000000032
(XEN)     X12: 0000000000000002 X13: 000000000026e5d8 X14: 0000000000000020
(XEN)     X15: 0000000000400000 X16: 0000000000000000 X17: 0000000000000000
(XEN)     X18: 000000007fe5ae30 X19: 0000000000600000 X20: 0000000000640000
(XEN)     X21: 0000000640000000 X22: 0000000600000000 X23: 0000000640000000
(XEN)     X24: 000000000028b320 X25: 00000000002b83e0 X26: 0000000048000000
(XEN)     X27: 0000000640000000 X28: 0000000000000002  FP: 00000000002d7d00
(XEN)
(XEN)   VTCR_EL2: 80000000
(XEN)  VTTBR_EL2: 0000000000000000
(XEN)
(XEN)  SCTLR_EL2: 30cd183d
(XEN)    HCR_EL2: 000000000078663f
(XEN)  TTBR0_EL2: 0000000078194000
(XEN)
(XEN)    ESR_EL2: f2000001
(XEN)  HPFAR_EL2: 0000000000000000
(XEN)    FAR_EL2: 0000000000000000
(XEN)
(XEN) Xen stack trace from sp=00000000002d7d00:
(XEN)    00000000002d7d40 000000000028b370 0000000000000001 0000000600000000
(XEN)    0000000640000000 0000000600000000 0000000640000000 00000000002d7d90
(XEN)    00000000002d7d90 000000000029c81c 0000000000000001 0000000600000000
(XEN)    0000000640000000 0000000600000000 0000000640000000 0000000000000001
(XEN)    00000000002e0000 0000000600000000 00000000002d7de0 000000000029d9e8
(XEN)    0000000640000000 0000000600000000 0000000640000000 00000000002b83c0
(XEN)    ffffffffffffffff 00000000002b83d8 0000000048000000 0000000048011000
(XEN)    000000007fe5a940 0000000000200608 0000000078080000 0000000077e80000
(XEN)    0000000048000000 0000000000000000 0000000000400000 0000000000000000
(XEN)    0000000000000001 0000000000000000 0000000078080000 0000000000000400
(XEN)    0000000000000000 0000000000011000 0000000048000000 00000000b8000000
(XEN)    00000000002b83c0 000000000028b320 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000300000000 ffffffff00000000 0000040000000040
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) Xen call trace:
(XEN)    [<000000000028b310>] page_alloc.c#bootmem_region_add+0x188/0x198 (PC)
(XEN)    [<000000000028b370>] init_boot_pages+0x50/0x17c (LR)
(XEN)    [<000000000028b370>] init_boot_pages+0x50/0x17c
(XEN)    [<000000000029c81c>] dt_unreserved_regions+0xc8/0xdc
(XEN)    [<000000000029d9e8>] start_xen+0xbec/0xc5c
(XEN)    [<0000000000200608>] arm64/head.o#paging+0x60/0x98
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Xen BUG at page_alloc.c:274
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...

I am using a 4.12.0-rc Xen, specifically from commit 08b908ba63dee8bc313983c5e412852cbcbcda85 dated Jan 16, 16:16:56 2019.

Do you have any idea what could be the matter?

Thank you very much for all the support.

Best regards,

Jairo

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.