Andrii,
I went through the instructions again and found the instructions for what you call Yocto 3.9 here [1].
I attempted following the initial Xen ARM instructions found here [2]
The biggest difference is in the commit revisions for meta-selinux and meta-virtualization that I didn't know if going with jethro and morty respectively was still necessary.I went for rocko. Since the system compiled, I continued with this revision.
The full compile output is shown below:
Loading cache: 100% |############################################| Time: 0:00:00
Loaded 2895 entries from dependency cache.
Parsing recipes: 100% |##########################################| Time: 0:00:01
Parsing of 2088 .bb files complete (2082 cached, 6 parsed). 2901 targets, 87 skipped, 4 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: Multiple providers are available for iasl-native (iasl-native, acpica-native)
Consider defining a PREFERRED_PROVIDER entry to match iasl-native
Build Configuration:
BB_VERSION = "1.36.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal-4.9"
TARGET_SYS = "aarch64-poky-linux"
MACHINE = "m3ulcb"
DISTRO = "poky"
DISTRO_VERSION = "2.4.2"
TUNE_FEATURES = "aarch64 cortexa57-cortexa53"
TARGET_FPU = ""
SOC_FAMILY = "rcar-gen3:r8a7796"
meta
meta-poky
meta-yocto-bsp = "tmp:342fbd6a3e57021c8e28b124b3adb241936f3d9d"
meta-rcar-gen3 = "tmp:fd078b6ece537d986852cb827bd21e022a797b2f"
meta-optee = "tmp:75dfb67bbb14a70cd47afda9726e2e1c76731885"
meta-oe
meta-python
meta-networking = "tmp:dacfa2b1920e285531bec55cd2f08743390aaf57"
meta-selinux = "rocko:d855c624f32c5e599bf27e06cb8f5b25b3aae12d"
meta-virtualization = "rocko:b704c689b67639214b9568a3d62e82df27e9434f"
meta-rcar-gen3-xen = "lastest_xen:cc6e6e1c07197207769331b0532fc88a9165a855"
Initialising tasks: 100% |#######################################| Time: 0:00:08
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 6243 tasks of which 5052 didn't need to be rerun and all succeeded.
I followed the R-Car M3 firmware update instructions without issue from [3]. I was confused with the ascii part, but when I realized that the instructions were for use with the minicom program, things were relatively smooth sailing.
After the firmware update, I attempted to boot the Linux created from running bitbake and was able to boot the following without issue:
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
... <redacted because it felt like unimportant data>
Poky (Yocto Project Reference Distro) 2.4.2 m3ulcb ttySC0
m3ulcb login: root
root@m3ulcb:~# uname -a
Linux m3ulcb 4.14.35-yocto-standard #2 SMP PREEMPT Mon Jan 21 23:44:14 JST 2019x
Which means that at least my Linux build is fine.
The U-Boot version is back to 2015.04 so I am guessing that this is the version you were expected for a Yocto 3.9 build.
The final step to load Xen brings me back to the initial issue which is that I obtain absolutely no output.
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
Hit any key to stop autoboot: 0
=> dhcp
ravb Waiting for PHY auto negotiation to complete........ done
ravb: 1000Base/Full
BOOTP broadcast 1
BOOTP broadcast 2
DHCP client bound to address 192.168.1.10 (256 ms)
*** Warning: no boot file name; using 'C0A8010A.img'
Using ravb device
TFTP from server 192.168.1.100; our IP address is 192.168.1.10
Filename 'C0A8010A.img'.
Load address: 0x48080000
Loading: *
TFTP error: 'File not found' (1)
Not retrying...
=> setenv bootargs
=> tftp 0x48080000 xen-m3ulcb.uImage
ravb:0 is connected to ravb. Reconnecting to ravb
ravb Waiting for PHY auto negotiation to complete... done
ravb: 1000Base/Full
Using ravb device
TFTP from server 192.168.1.100; our IP address is 192.168.1.3
Filename 'xen-m3ulcb.uImage'.
Load address: 0x48080000
Loading: #############################################################
171.9 KiB/s
done
Bytes transferred = 886160 (d8590 hex)
=> tftp 0x48000000 Image-r8a7796-m3ulcb-xen-local.dtb
ravb:0 is connected to ravb. Reconnecting to ravb
ravb Waiting for PHY auto negotiation to complete... done
ravb: 1000Base/Full
Using ravb device
TFTP from server 192.168.1.100; our IP address is 192.168.1.3
Filename 'Image-r8a7796-m3ulcb-xen-local.dtb'.
Load address: 0x48000000
Loading: #####
12.7 KiB/s
done
Bytes transferred = 68545 (10bc1 hex)
=> tftp 0x7a000000 Image-m3ulcb.bin
ravb:0 is connected to ravb. Reconnecting to ravb
ravb Waiting for PHY auto negotiation to complete... done
ravb: 1000Base/Full
Using ravb device
TFTP from server 192.168.1.100; our IP address is 192.168.1.3
Filename 'Image-m3ulcb.bin'.
Load address: 0x7a000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
################################
2.4 MiB/s
done
Bytes transferred = 18588160 (11ba200 hex)
=> bootm 0x48080000 - 0x48000000
## Booting kernel from Legacy Image at 48080000 ...
Image Name: XEN
Image Type: AArch64 Linux Kernel Image (uncompressed)
Data Size: 886096 Bytes = 865.3 KiB
Load Address: 78080000
Entry Point: 78080000
Verifying Checksum ... OK
## Flattened Device Tree blob at 48000000
Booting using the fdt blob at 0x48000000
Loading Kernel Image ... OK
Using Device Tree in place at 0000000048000000, end 0000000048013bc0
Starting kernel ...
Obtaining no output is still a little unsettling. I am still a little worried that my dtb configuration is wrong but since the only thing I should need to modify is the chosen section, I place that below:
chosen {
stdout-path = "serial0:115200n8";
xen,xen-bootargs = "dom0_mem=752M console=dtuart dtuart=serial0 dom0_max_vcpus=4";
xen,dom0-bootargs = "console=hvc0 clk_ignore_unused root=/dev/mmcblk1p2 rw rootwait ignore_loglevel cma=128M";
#address-cells = <2>;
#size-cells = <2>;
modules {
module@0 {
compatible = "xen,linux-zimage", "xen,multiboot-module";
reg = <0x0 0x7a000000 0x0 0x02000000>;
};
};
};
Since I am using the sd-card to attempt to boot various versions, I have chosen the second partition for Linux.
Last time there was a mention of modifying the internal build scripts for Xen.
If there is any additional information I can obtain for you let me know.
For now I think I am finally in Yocto 3.9 running a 4.14 Linux kernel and attempting to run and unstable Xen with the following modified xen_git.bbappend from the Xen troops meta-demo repository [4].
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
DEPENDS += "u-boot-mkimage-native"
XEN_REL="unstable"
XEN_BRANCH = "master"
SRCREV = "${AUTOREV}"
EXTRA_OEMAKE += " CONFIG_QEMU_XEN=n"
DEFAULT_PREFERENCE = "1"
do_deploy_append () {
if [ -f ${D}/boot/xen ]; then
uboot-mkimage -A arm64 -C none -T kernel -a 0x78080000 -e 0x78080000 -n "XEN" -d ${D}/boot/xen ${DEPLOYDIR}/xen-${MACHINE}.uImage
fi
}
FILES_${PN}-xencommons_remove += " \
${systemd_unitdir}/system/xenstored.socket \
${systemd_unitdir}/system/xenstored_ro.socket \
"
FILES_${PN}-xencommons += " \
${systemd_unitdir}/system/xendriverdomain.service \
"
SYSTEMD_SERVICE_${PN}-xencommons_remove += " \
xenstored.socket \
xenstored_ro.socket \
"
#FILES_${PN}-libxendevicemodel = "${libdir}/libxendevicemodel.so.*"
#FILES_${PN}-libxendevicemodel-dev = "${libdir}/libxendevicemodel.so"
FILES_${PN}-libxentoolcore = "${libdir}/libxentoolcore.so.*"
FILES_${PN}-libxentoolcore-dev = "${libdir}/libxentoolcore.so"
FILES_${PN}-pkgconfig = "\
${datadir}/pkgconfig \
"
FILES_${PN}-xendiag += " \
${sbindir}/xen-diag \
"
PACKAGES_append = "\
${PN}-libxentoolcore \
${PN}-libxentoolcore-dev \
${PN}-pkgconfig \
${PN}-xendiag \
"
RDEPENDS_${PN}-base_remove = "\
${PN}-blktap \
${PN}-libblktapctl \
${PN}-libvhd \
"
FILES_${PN}-staticdev += "\
${libdir}/libxenforeignmemory.a \
${libdir}/libxentoollog.a \
${libdir}/libxengnttab.a \
${libdir}/libxendevicemodel.a \
${libdir}/libxenevtchn.a \
${libdir}/libxencall.a \
${libdir}/libxentoolcore.a \
"
FILES_${PN}-libxencall-dev += " \
${libdir}/libxencall.so \
${datadir}/pkgconfig/xencall.pc \
"
FILES_${PN}-libxenctrl-dev += " \
${libdir}/libxenctrl.so \
${datadir}/pkgconfig/xencontrol.pc \
"
FILES_${PN}-libxendevicemodel += "${libdir}/libxendevicemodel.so.*"
FILES_${PN}-libxendevicemodel-dev += " \
${libdir}/libxendevicemodel.so \
${datadir}/pkgconfig/xendevicemodel.pc \
"
FILES_${PN}-libxenevtchn-dev += " \
${libdir}/libxenevtchn.so \
${datadir}/pkgconfig/xenevtchn.pc \
"
FILES_${PN}-libxenforeignmemory-dev += "\
${libdir}/libxenforeignmemory.so \
${datadir}/pkgconfig/xenforeignmemory.pc \
"
FILES_${PN}-libxengnttab-dev += " \
${libdir}/libxengnttab.so \
${datadir}/pkgconfig/xengnttab.pc \
"
FILES_${PN}-libxenguest-dev += " \
${libdir}/libxenguest.so \
${datadir}/pkgconfig/xenguest.pc \
"
FILES_${PN}-libxenstat-dev += " \
${libdir}/libxenstat.so \
${datadir}/pkgconfig/xenstat.pc \
"
FILES_${PN}-libxenstore-dev += " \
${libdir}/libxenstore.so \
${datadir}/pkgconfig/xenstore.pc \
"
FILES_${PN}-libxentoolcore += "${libdir}/libxentoolcore.so.*"
FILES_${PN}-libxentoolcore-dev += " \
${libdir}/libxentoolcore.so \
${datadir}/pkgconfig/xentoolcore.pc \
"
FILES_${PN}-libxentoollog-dev += " \
${libdir}/libxentoollog.so \
${datadir}/pkgconfig/xentoollog.pc \
"
FILES_${PN}-libxenvchan-dev += " \
${libdir}/libxenvchan.so \
${datadir}/pkgconfig/xenvchan.pc \
"
FILES_${PN}-misc += "\
${sbindir}/xen-diag \
${libdir}/xen/bin/depriv-fd-checker \
"
FILES_${PN}-efi = "\
${exec_prefix}/lib64/efi/xen* \
"
FILES_${PN}-xenmon += "\
${sbindir}/xenmon \
"
FILES_${PN}-fsimage += "\
${libdir}/xenfsimage/*/fsimage.so \
"
FILES_${PN}-libfsimage += "\
${libdir}/libxenfsimage.so.* \
"
FILES_${PN}-libfsimage-dev += "\
${libdir}/libxenfsimage.so \
"
Best regards,
Jairo
Jairo,
On 11.01.19 22:12, LOPEZ, FUENTES NACARINO Jairo Eduardo wrote:
> I followed your initial advice and updated my environment to a newer version, opting to stick to the rocko version for the m3ulcb.
I'm a bit confused are you using Renesas Yocto 3.9 or the latest 3.13?
>
> The Yocto build configuration is shown below:
>
> Build Configuration:
> BB_VERSION = "1.36.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "universal-4.9"
> TARGET_SYS = "aarch64-poky-linux"
> MACHINE = "m3ulcb"
> DISTRO = "poky"
> DISTRO_VERSION = "2.4.2"
Looks like 3.9, but why do you have u-boot 2018.09 below?
> TUNE_FEATURES = "aarch64 cortexa57-cortexa53"
> TARGET_FPU = ""
> SOC_FAMILY = "rcar-gen3:r8a7796"
> meta
> meta-poky
> meta-yocto-bsp = "HEAD:342fbd6a3e57021c8e28b124b3adb241936f3d9d"
> meta-rcar-gen3 = "rocko:8af0b7d6e445b532088a068dc012757001be3a1f"
> meta-optee = "rocko:75dfb67bbb14a70cd47afda9726e2e1c76731885"
> meta-oe
> meta-python
> meta-networking = "rocko:eae996301d9c097bcbeb8046f08041dc82bb62f8"
> meta-selinux = "rocko:d855c624f32c5e599bf27e06cb8f5b25b3aae12d"
> meta-virtualization = "rocko:b704c689b67639214b9568a3d62e82df27e9434f"
> meta-rcar-gen3-xen = "master:60699c631d541aeeaebaeec9a087efed9385ee42"
>
> I had to modify the dtb to the version shown below:
>
> // SPDX-License-Identifier: GPL-2.0
> /*
> * Device Tree Source for the M3ULCB (R-Car Starter Kit Pro) board
> *
> * Copyright (C) 2016-2018 Renesas Electronics Corp.
> * Copyright (C) 2016 Cogent Embedded, Inc.
> */
>
> /dts-v1/;
> #include "r8a7796.dtsi"
> #include "ulcb.dtsi"
>
> / {
> model = "Renesas M3ULCB board based on r8a7796";
> compatible = "renesas,m3ulcb", "renesas,r8a7796";
>
> cpus {
> idle-states {
> /delete-node/ cpu-sleep-1;
> };
> };
>
> memory@48000000 {
> device_type = "memory";
> /* first 128MB is reserved for secure area. */
> reg = <0x0 0x48000000 0x0 0x38000000>;
> };
>
> memory@600000000 {
> device_type = "memory";
> reg = <0x6 0x00000000 0x0 0x40000000>;
> };
Merge memory nodes to be sure u-boot do not duplicate memory ranges.
>
> reserved-memory {
> #address-cells = <2>;
> #size-cells = <2>;
> ranges;
>
> /* device specific region for Lossy Decompression */
> lossy_decompress: linux,lossy_decompress@54000000 {
> no-map;
> reg = <0x00000000 0x54000000 0x0 0x03000000>;
> };
>
> /* global autoconfigured region for contiguous allocations */
> linux,cma@57000000 {
> compatible = "shared-dma-pool";
> reusable;
> reg = <0x00000000 0x57000000 0x0 0x19000000>;
> linux,cma-default;
> };
>
> /* device specific region for contiguous allocations */
> mmp_reserved: linux,multimedia@70000000 {
> compatible = "shared-dma-pool";
> reusable;
> reg = <0x00000000 0x70000000 0x0 0x10000000>;
> };
> };
>
> chosen {
> stdout-path = "serial0:115200n8";
> xen,xen-bootargs = "dom0_mem=752M console=dtuart dtuart=serial0 dom0_max_vcpus=4";
> xen,dom0-bootargs = "console=hvc0 clk_ignore_unused root=/dev/mmcblk1p2 rw rootwait ignore_loglevel cma=128M";
>
> #address-cells = <2>;
> #size-cells = <2>;
> modules {
> module@0 {
> compatible = "xen,linux-zimage", "xen,multiboot-module";
> reg = <0x0 0x7a000000 0x0 0x02000000>;
> };
> };
> };
>
> mmngr {
> compatible = "renesas,mmngr";
> memory-region = <&mmp_reserved>, <&lossy_decompress>;
> };
>
> mmngrbuf {
> compatible = "renesas,mmngrbuf";
> };
>
> vspm_if {
> compatible = "renesas,vspm_if";
> };
>
> versaclock5_out3: versaclk-3 {
> compatible = "fixed-clock";
> #clock-cells = <0>;
> /* Initial value of versaclock out3 */
> clock-frequency = <33000000>;
> };
> };
>
> &a53_0 {
> /delete-property/ cpu-idle-states;
> };
>
> &a53_1 {
> /delete-property/ cpu-idle-states;
> };
>
> &a53_2 {
> /delete-property/ cpu-idle-states;
> };
>
> &a53_3 {
> /delete-property/ cpu-idle-states;
> };
>
> &du {
> clocks = <&cpg CPG_MOD 724>,
> <&cpg CPG_MOD 723>,
> <&cpg CPG_MOD 722>,
> <&versaclock5 1>,
> <&versaclock5_out3>,
> <&versaclock5 2>;
> clock-names = "du.0", "du.1", "du.2",
> "dclkin.0", "dclkin.1", "dclkin.2";
> };
>
> &vspb {
> status = "okay";
> };
>
> &vspi0 {
> status = "okay";
> };
> With the new information, I finally got some output for Xen, but was met with a completely different issue for which I can't find any information for the error I am receiving.
>
> I realize that I may have an issue with the version of the board I am using, but a simple online search doesn't throw any red flags. The serial console output is below:
>
> [ 0.000177] NOTICE: BL2: R-Car M3 Initial Program Loader(CA57)
> [ 0.004613] NOTICE: BL2: Initial Program Loader(Rev.2.0.0)
> [ 0.010147] NOTICE: BL2: PRR is R-Car M3 Ver.1.0
Your M3 revision is really old. We did not use something older than M3 1.1. But for the start it might be OK. You would not have IPMMU functional, though you do not need it now.
> [ 0.014815] NOTICE: BL2: Board is Starter Kit Rev.1.0
> [ 0.019928] NOTICE: BL2: Boot device is HyperFlash(80MHz)
> [ 0.025354] NOTICE: BL2: LCM state is CM
> [ 0.029395] NOTICE: BL2: AVS setting succeeded. DVFS_SetVID=0x53
> [ 0.035383] NOTICE: BL2: DDR3200(rev.0.34)
> [ 0.046779] NOTICE: BL2: [COLD_BOOT]
> [ 0.085117] NOTICE: BL2: DRAM Split is 2ch
> [ 0.087812] NOTICE: BL2: QoS is default setting(rev.0.19)
> [ 0.093315] NOTICE: BL2: Lossy Decomp areas
> [ 0.097489] NOTICE: Entry 0: DCMPAREACRAx:0x80000540 DCMPAREACRBx:0x570
> [ 0.104573] NOTICE: Entry 1: DCMPAREACRAx:0x40000000 DCMPAREACRBx:0x0
> [ 0.111485] NOTICE: Entry 2: DCMPAREACRAx:0x20000000 DCMPAREACRBx:0x0
> [ 0.118400] NOTICE: BL2: v1.5(release):556a11e
> [ 0.122890] NOTICE: BL2: Built : 18:03:48, Jan 11 2019
> [ 0.128077] NOTICE: BL2: Normal boot
> [ 0.131718] NOTICE: BL2: dst=0xe6321100 src="" len=512(0x200)
> [ 0.138106] NOTICE: BL2: dst=0x43f00000 src="" len=6144(0x1800)
> [ 0.144726] NOTICE: BL2: dst=0x44000000 src="" len=65536(0x10000)
> [ 0.151952] NOTICE: BL2: dst=0x44100000 src="" len=1048576(0x100000)
> [ 0.166777] NOTICE: BL2: dst=0x50000000 src="" len=1048576(0x100000)
> [ 0.180752] NOTICE: BL2: Booting BL31
>
>
> U-Boot 2018.09 (Jan 12 2019 - 03:03:43 +0900)
It is a u-boot from Renesas Yocto 3.13. I would not recommend you using it.
Seeing the problem below, it looks like u-boot messes with the device tree in a different way now.
>
> CPU: Renesas Electronics R8A7796 rev 1.0
> Model: Renesas M3ULCB board based on r8a7796
> DRAM: 1.9 GiB
> Bank #0: 0x048000000 - 0x07fffffff, 896 MiB
> Bank #1: 0x600000000 - 0x63fffffff, 1 GiB
>
> MMC: sd@ee100000: 0, sd@ee140000: 1
> Loading Environment from MMC... communication out of sync
> communication out of sync
> communication out of sync
> communication out of sync
> communication out of sync
> communication out of sync
> communication out of sync
> communication out of sync
> communication out of sync
> communication out of sync
> communication out of sync
> communication out of sync
> OK
> In: serial@e6e88000
> Out: serial@e6e88000
> Err: serial@e6e88000
> Net: eth0: ethernet@e6800000
> Hit any key to stop autoboot: 0
> ethernet@e6800000 Waiting for PHY auto negotiation to complete... done
> Using ethernet@e6800000 device
> TFTP from server 192.168.1.100; our IP address is 192.168.1.3
> Filename 'Image'.
> Load address: 0x48080000
> Loading: #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> ############################################
> 2.7 MiB/s
> done
> Bytes transferred = 15911424 (f2ca00 hex)
> Using ethernet@e6800000 device
> TFTP from server 192.168.1.100; our IP address is 192.168.1.3
> Filename 'Image-r8a7796-m3ulcb.dtb'.
> Load address: 0x48000000
> Loading: *
> TFTP error: 'File not found' (1)
> Not retrying...
> ERROR: Did not find a cmdline Flattened Device Tree
> Could not find a valid device tree
> => setenv bootargs
> => tftp 0x48080000 xen-m3ulcb.uImage
> Using ethernet@e6800000 device
> TFTP from server 192.168.1.100; our IP address is 192.168.1.3
> Filename 'xen-m3ulcb.uImage'.
> Load address: 0x48080000
> Loading: ###############################################################
> 28.3 MiB/s
> done
> Bytes transferred = 918928 (e0590 hex)
> => tftp 0x48000000 Image-r8a7796-m3ulcb-xen-local.dtb
> Using ethernet@e6800000 device
> TFTP from server 192.168.1.100; our IP address is 192.168.1.3
> Filename 'Image-r8a7796-m3ulcb-xen-local.dtb'.
> Load address: 0x48000000
> Loading: #####
> 21.8 MiB/s
> done
> Bytes transferred = 68545 (10bc1 hex)
> => tftp 0x7a000000 Image-m3ulcb.bin
> Using ethernet@e6800000 device
> TFTP from server 192.168.1.100; our IP address is 192.168.1.3
> Filename 'Image-m3ulcb.bin'.
> Load address: 0x7a000000
> Loading: #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> ################################################################
> 28.1 MiB/s
> done
> Bytes transferred = 19059200 (122d200 hex)
> => bootm 0x48080000 - 0x48000000
> ## Booting kernel from Legacy Image at 48080000 ...
> Image Name: XEN
> Image Type: AArch64 Linux Kernel Image (uncompressed)
> Data Size: 918864 Bytes = 897.3 KiB
> Load Address: 78080000
> Entry Point: 78080000
> Verifying Checksum ... OK
> ## Flattened Device Tree blob at 48000000
> Booting using the fdt blob at 0x48000000
> Loading Kernel Image ... OK
> Using Device Tree in place at 0000000048000000, end 0000000048013bc0
>
> Starting kernel ...
>
> Xen 4.12-unstable
> (XEN) Xen version 4.12-unstable (jelfn@xxxxxxxxx <mailto:jelfn@xxxxxxxxx>) (aarch64-poky-linux-gc9
> (XEN) Latest ChangeSet: Mon Dec 17 09:22:59 2018 +0000 git:a5b0eb3-dirty
> (XEN) Processor: 411fd073: "ARM Limited", variant: 0x1, part 0xd07, rev 0x3
> (XEN) 64-bit Execution:
> (XEN) Processor Features: 0000000000002222 0000000000000000
> (XEN) Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
> (XEN) Extensions: FloatingPoint AdvancedSIMD
> (XEN) Debug Features: 0000000010305106 0000000000000000
> (XEN) Auxiliary Features: 0000000000000000 0000000000000000
> (XEN) Memory Model Features: 0000000000001124 0000000000000000
> (XEN) ISA Features: 0000000000011120 0000000000000000
> (XEN) 32-bit Execution:
> (XEN) Processor Features: 00000131:00011011
> (XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
> (XEN) Extensions: GenericTimer Security
> (XEN) Debug Features: 03010066
> (XEN) Auxiliary Features: 00000000
> (XEN) Memory Model Features: 10201105 40000000 01260000 02102211
> (XEN) ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
> (XEN) Using SMC Calling Convention v1.1
> (XEN) Using PSCI v1.1
> (XEN) SMP: Allowing 6 CPUs
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Timer: Unable to retrieve IRQ 0 from the device tree
XEN failed to find timer node in the device tree. r8a7796.dtsi has timer node described, so it must be u-boot changed dtb.
We have scheduled switching to Renesas Yocto 3.13 soon, so will coupe with the issue.
But for now I would recommend you using 3.9 at most.
--
Sincerely,
Andrii Anisov.
