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. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
