Hello Bertrand,
I succeeded in building the core minimal image with dunfell and its compatible
branches [except xen-troops (modified some files to complete the build)].
But I face the following error while booting.
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Timer: Unable to retrieve IRQ 0 from the device tree
(XEN) ****************************************
My Build Configuration:
BB_VERSION = "1.46.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "aarch64-poky-linux"
MACHINE = "salvator-x"
DISTRO = "poky"
DISTRO_VERSION = "3.1.1"
TUNE_FEATURES = "aarch64 cortexa57-cortexa53"
TARGET_FPU = ""
SOC_FAMILY = "rcar-gen3:r8a7795"
meta
meta-poky
meta-yocto-bsp = "tmp:39d7cf1abb2c88baaedb3a627eba8827747b2eb9"
meta-rcar-gen3 = "dunfell-dev:2b3b0447fbc6c360a43a13525ae63a253fe3e5b7"
meta-oe
meta-python
meta-filesystems
meta-networking = "tmp:cc6fc6b1641ab23089c1e3bba11e0c6394f0867c"
meta-selinux = "dunfell:7af62c91d7d00a260cf28e7908955539304d100d"
meta-virtualization = "dunfell:ffd787fb850e5a1657a01febc8402c74832147a1"
meta-rcar-gen3-xen = "master:60699c631d541aeeaebaeec9a087efed9385ee42"
May I know the reason for this error? Am I missing something here? Attaching
complete logs for reference.
Mit freundlichen Grüßen / Best regards
Chockalingam Manikandan
ES-CM Core fn,ADIT (RBEI/ECF3)
Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY |
www.bosch.com
Tel. +91 80 6136-4452 | Fax +91 80 6617-0711 |
manikandan.chockalin...@in.bosch.com
Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB
14000;
Chairman of the Supervisory Board: Franz Fehrenbach; Managing Directors: Dr.
Volkmar Denner,
Prof. Dr. Stefan Asenkerschbaumer, Dr. Michael Bolle, Dr. Christian Fischer,
Dr. Stefan Hartung,
Dr. Markus Heyn, Harald Kröger, Christoph Kübel, Rolf Najork, Uwe Raschke,
Peter Tyroller
-----Original Message-----
From: Manikandan Chockalingam (RBEI/ECF3)
Sent: Friday, July 10, 2020 9:56 AM
To: 'Bertrand Marquis' <bertrand.marq...@arm.com>
Cc: xen-de...@lists.xen.org; nd <n...@arm.com>
Subject: RE: [BUG] Xen build for RCAR failing
Hello Bertrand,
I couldn't find dunfell branch in the following repos 1. meta-selinux 2.
xen-troops 3. meta-renesas [I took dunfell-dev]
Mit freundlichen Grüßen / Best regards
Chockalingam Manikandan
ES-CM Core fn,ADIT (RBEI/ECF3)
Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY |
www.bosch.com Tel. +91 80 6136-4452 | Fax +91 80 6617-0711 |
manikandan.chockalin...@in.bosch.com
Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB
14000; Chairman of the Supervisory Board: Franz Fehrenbach; Managing Directors:
Dr. Volkmar Denner, Prof. Dr. Stefan Asenkerschbaumer, Dr. Michael Bolle, Dr.
Christian Fischer, Dr. Stefan Hartung, Dr. Markus Heyn, Harald Kröger,
Christoph Kübel, Rolf Najork, Uwe Raschke, Peter Tyroller
-----Original Message-----
From: Bertrand Marquis <bertrand.marq...@arm.com>
Sent: Tuesday, July 7, 2020 5:18 PM
To: Manikandan Chockalingam (RBEI/ECF3) <manikandan.chockalin...@in.bosch.com>
Cc: xen-de...@lists.xen.org; nd <n...@arm.com>
Subject: Re: [BUG] Xen build for RCAR failing
> On 7 Jul 2020, at 11:18, Manikandan Chockalingam (RBEI/ECF3)
> <manikandan.chockalin...@in.bosch.com> wrote:
>
> Hello Bertrand,
>
> Thank you. I will try a fresh build with dunfell branch. All layers in the
> sense [poky, meta-openembedded, meta-linaro, meta-rensas,
> meta-virtualisation, meta-selinux, xen-troops] right?
right
>
> Also, Can I use the same proprietary drivers which I used for
> yocto2.19[R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20170427.zip]
> for this branch?
I have no idea what is in that but i would guess it will probably not work that
easily.
You might need to get in contact with Renesas to get more up-to-date
instructions on how to build that.
Bertrand
[ 0.000149] NOTICE: BL2: R-Car H3 Initial Program Loader(CA57)
[ 0.004585] NOTICE: BL2: Initial Program Loader(Rev.2.0.6)
[ 0.010119] NOTICE: BL2: PRR is R-Car H3 Ver.2.0
[ 0.014787] NOTICE: BL2: Board is Salvator-X Rev.1.0
[ 0.019814] NOTICE: BL2: Boot device is HyperFlash(160MHz)
[ 0.025325] NOTICE: BL2: LCM state is CM
[ 0.029368] NOTICE: BL2: AVS setting succeeded. DVFS_SetVID=0x53
[ 0.035384] NOTICE: BL2: DDR3200(rev.0.40)
[ 0.050722] NOTICE: BL2: [COLD_BOOT]
[ 0.059497] NOTICE: BL2: DRAM Split is 4ch
[ 0.062192] NOTICE: BL2: QoS is default setting(rev.0.21)
[ 0.067635] NOTICE: BL2: DRAM refresh interval 1.95 usec
[ 0.072992] NOTICE: BL2: Periodic Write DQ Training
[ 0.078023] NOTICE: BL2: v1.5(release):af9f429
[ 0.082410] NOTICE: BL2: Built : 07:07:22, Jul 14 2020
[ 0.087597] NOTICE: BL2: Normal boot
[ 0.091238] NOTICE: BL2: dst=0xe6325100 src=0x8180000 len=512(0x200)
[ 0.097623] NOTICE: BL2: dst=0x43f00000 src=0x8180400 len=6144(0x1800)
[ 0.104233] NOTICE: BL2: dst=0x44000000 src=0x81c0000 len=65536(0x10000)
[ 0.111217] NOTICE: BL2: dst=0x44100000 src=0x8200000 len=1048576(0x100000)
[ 0.122179] NOTICE: BL2: dst=0x50000000 src=0x8640000 len=1048576(0x100000)
[ 0.132033] NOTICE: BL2: Booting BL31
U-Boot 2018.09 (Jul 12 2020 - 19:09:13 +0000)
CPU: Renesas Electronics R8A7795 rev 2.0
Model: Renesas Salvator-X board based on r8a7795 ES2.0+
DRAM: 3.9 GiB
Bank #0: 0x048000000 - 0x07fffffff, 896 MiB
Bank #1: 0x500000000 - 0x53fffffff, 1 GiB
Bank #2: 0x600000000 - 0x63fffffff, 1 GiB
Bank #3: 0x700000000 - 0x73fffffff, 1 GiB
MMC: sd@ee100000: 0, sd@ee140000: 1, sd@ee160000: 2
Loading Environment from MMC... OK
In: serial@e6e88000
Out: serial@e6e88000
Err: serial@e6e88000
Net:
Error: ethernet@e6800000 address not set.
eth-1: ethernet@e6800000
Hit any key to stop autoboot: 0
=> setenv ethaddr de:ad:be:ef:01:02
=> setenv ipaddr 192.168.2.51
=> setenv serverip 192.168.2.11
=> tftp 0x4A000000 r8a7795-salvator-x-xen.dtb
ethernet@e6800000 Waiting for PHY auto negotiation to complete..... done
Using ethernet@e6800000 device
TFTP from server 192.168.2.11; our IP address is 192.168.2.51
Filename 'r8a7795-salvator-x-xen.dtb'.
Load address: 0x4a000000
Loading: *
ARP Retry count exceeded; starting again
=> tftp 0x4A000000 r8a7795-salvator-x-xen.dtb
Using ethernet@e6800000 device
TFTP from server 192.168.2.11; our IP address is 192.168.2.51
Filename 'r8a7795-salvator-x-xen.dtb'.
Load address: 0x4a000000
Loading: ######
2.2 MiB/s
done
Bytes transferred = 80783 (13b8f hex)
=> tftp 0x48200000 Image
Using ethernet@e6800000 device
TFTP from server 192.168.2.11; our IP address is 192.168.2.51
Filename 'Image'.
Load address: 0x48200000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
############
2.3 MiB/s
done
Bytes transferred = 21156352 (142d200 hex)
=> tftp 0x48000000 xen
Using ethernet@e6800000 device
TFTP from server 192.168.2.11; our IP address is 192.168.2.51
Filename 'xen'.
Load address: 0x48000000
Loading: ###########################################################
2.1 MiB/s
done
Bytes transferred = 853328 (d0550 hex)
=> booti 0x48000000 - 0x4A000000
## Flattened Device Tree blob at 4a000000
Booting using the fdt blob at 0x4a000000
Using Device Tree in place at 000000004a000000, end 000000004a016b8e
Starting kernel ...
Xen 4.12.4-pre
(XEN) Xen version 4.12.4-pre (manikandan@) (aarch64-linux-gnu-gcc (Sourcery
CodeBench 2018.05-7) 7.3.1 20180612) d0
(XEN) Latest ChangeSet: Tue Jul 7 15:13:40 2020 +0200 git:19e0bbb
(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)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Timer: Unable to retrieve IRQ 0 from the device tree
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
