Re: RT Xen on ARM - R-Car series

["LOPEZ, FUENTES NACARINO Jairo Eduardo" <jairo@ruri.waseda.jp>]

[-- Attachment #1.1: Type: text/plain, Size: 9145 bytes --]

Andrii,

Thank you for your response.

I am sorry for not being able to make time to answer sooner.

Hello to everyone from the Xen Development mailing list.

As I told Andrii, I am interested in RT Xen, but before getting anywhere
near that, I need to actually get my board to use Xen.

As a total newcomer to these boards and knowing that Xen is a little
complex to get running, I am sure there are a lot of steps that I am either
doing wrong, or have made the wrong assumptions.

The SoC information of the R-Car H3 I have is below:

CPU: Renesas Electronics R8A7795 rev 2.0
Board: H3ULCB
I2C:   ready
DRAM:  3.9 GiB
MMC:   sh-sdhi: 0, sh-sdhi: 1
In:    serial
Out:   serial
Err:   serial
Net:   ravb
Hit any key to stop autoboot:  0
=> [    0.000158] NOTICE:  BL2: R-Car Gen3 Initial Program Loader(CA57)
Rev.1.0.16
[    0.005718] NOTICE:  BL2: PRR is R-Car H3 Ver2.0
[    0.010301] NOTICE:  BL2: Board is Starter Kit Rev1.0
[    0.015328] NOTICE:  BL2: Boot device is HyperFlash(80MHz)
[    0.020754] NOTICE:  BL2: LCM state is CM
[    0.024799] NOTICE:  BL2: AVS setting succeeded. DVFS_SetVID=0x53
[    0.030782] NOTICE:  BL2: DDR3200(rev.0.27)NOTICE:  [COLD_BOOT]NOTICE:
..0
[    0.057151] NOTICE:  BL2: DRAM Split is 4ch
[    0.061034] NOTICE:  BL2: QoS is default setting(rev.0.18)
[    0.066533] NOTICE:  BL2: Lossy Decomp areas
[    0.070711] NOTICE:       Entry 0: DCMPAREACRAx:0x80000540
DCMPAREACRBx:0x570
[    0.077796] NOTICE:       Entry 1: DCMPAREACRAx:0x40000000
DCMPAREACRBx:0x0
[    0.084708] NOTICE:       Entry 2: DCMPAREACRAx:0x20000000
DCMPAREACRBx:0x0
[    0.091623] NOTICE:  BL2: v1.3(release):0387358
[    0.096113] NOTICE:  BL2: Built : 04:35:44, Jun 22 2018
[    0.101300] NOTICE:  BL2: Normal boot
[    0.104941] NOTICE:  BL2: dst=0xe6320210 src=0x8180000 len=512(0x200)
[    0.111487] NOTICE:  BL2: dst=0x43f00000 src=0x8180400 len=6144(0x1800)
[    0.117949] NOTICE:  BL2: dst=0x44000000 src=0x81c0000 len=65536(0x10000)
[    0.125175] NOTICE:  BL2: dst=0x44100000 src=0x8200000
len=524288(0x80000)
[    0.135655] NOTICE:  BL2: dst=0x50000000 src=0x8640000
len=1048576(0x100000)
[    0.149770] NOTICE:  BL3-1 : Rev.1.0.16
[    0.154065] NOTICE:  BL31: v1.3(release):0387358
[    0.157189] NOTICE:  BL31: Built : 04:35:47, Jun 22 2018


U-Boot 2015.04 (Jun 22 2018 - 13:36:27)

CPU: Renesas Electronics R8A7795 rev 2.0
Board: H3ULCB
I2C:   ready
DRAM:  3.9 GiB
MMC:   sh-sdhi: 0, sh-sdhi: 1
In:    serial
Out:   serial
Err:   serial
Net:   ravb

I believe this is the SoC information. If there is any other method of
extracting the information, please let me know so I can transmit it.
I took a look at [1] and decided to start from scratch to attempt to get
the minimum workspace functioning.

As I mentioned before I attempted using the Salvator-X guideline for the
H3ULCB.

In previous attempts, I had to modify some recipes to get the compilation
working, but this time I would like to confirm with everyone the initial
steps before I take them.

I have not done anything other than what the Wiki (
https://www.renesas.com/us/en/solutions/automotive/adas/solution-kits/r-car-starter-kit.html)
says I should.
After adding all the layers, I start bitbake:

$ bitbake core-image-minimal

Build
Configuration:
BB_VERSION        =
"1.30.0"
BUILD_SYS         =
"x86_64-linux"
NATIVELSBSTRING   =
"universal"
TARGET_SYS        =
"aarch64-poky-linux"
MACHINE           =
"h3ulcb"
DISTRO            =
"poky"
DISTRO_VERSION    =
"2.1.2"
TUNE_FEATURES     = "aarch64
cortexa57-cortexa53"
TARGET_FPU        =
""
SOC_FAMILY        =
"rcar-gen3:r8a7796"
meta

meta-poky

meta-yocto-bsp    =
"tmp:cca8dd15c8096626052f6d8d25ff1e9a606104a3"
meta-rcar-gen3    =
"tmp:95cb48ba09bc7e55fd549817e3e26723409e68d5"
meta-linaro-toolchain

meta-optee        =
"tmp:2f51d38048599d9878f149d6d15539fb97603f8f"
meta-oe           =
"tmp:55c8a76da5dc099a7bc3838495c672140cedb78e"
meta-virtualization =
"morty:6249631f59ad6ee3dc93762de49fc4b443d99abc"
meta-selinux      =
"jethro:4c75d9cbcf1d75043c7c5ab315aa383d9b227510"
meta-networking

meta-python       =
"tmp:55c8a76da5dc099a7bc3838495c672140cedb78e"
meta-rcar-gen3-xen =
"master:60699c631d541aeeaebaeec9a087efed9385ee42"


NOTE: Preparing
RunQueue
NOTE: Executing SetScene
Tasks
NOTE: Executing RunQueue
Tasks
ERROR: xen-unstable+gitAUTOINC+9d357cbaf7-r0 do_package: QA Issue: xen:
Files/directories were installed but not shipped in any package:
  /usr/lib/libxenfsimage.so
  /usr/lib/libxenfsimage.so.4.12
  /usr/lib/libxenfsimage.so.4.12.0
  /usr/lib/xenfsimage/ext2fs-lib/fsimage.so
  /usr/lib/xenfsimage/ufs/fsimage.so
  /usr/lib/xenfsimage/fat/fsimage.so
  /usr/lib/xenfsimage/iso9660/fsimage.so
  /usr/lib/xenfsimage/reiserfs/fsimage.so
  /usr/lib/xenfsimage/zfs/fsimage.so
  /usr/lib/xen/bin/depriv-fd-checker
  /usr/sbin/xenmon
Please set FILES such that these items are packaged. Alternatively if they
are unneeded, avoid installing them or delete them within do_install.
xen: 11 installed and not shipped files. [installed-vs-shipped]
ERROR: xen-unstable+gitAUTOINC+9d357cbaf7-r0 do_package: Fatal QA errors
found, failing task.
ERROR: xen-unstable+gitAUTOINC+9d357cbaf7-r0 do_package: Function failed:
do_package
ERROR: Logfile of failure stored in:
/home/yocto/r-car/build/tmp/work/aarch64-poky-linux/xen/unstable+gitAUTOINC+9d357cbaf7-r0/temp/log.do_package.8954
ERROR: Task 329 (/home/yocto/r-car/meta-virtualization/recipes-extended/xen/
xen_git.bb, do_package) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3642 tasks of which 3641 didn't need to be
rerun and 1 failed.
No currently running tasks (2517 of 3653)

Summary: 1 task failed:
  /home/yocto/r-car/meta-virtualization/recipes-extended/xen/xen_git.bb,
do_package
Summary: There were 3 WARNING messages shown.
Summary: There were 3 ERROR messages shown, returning a non-zero exit code.

I am aware I am using a very old BSP. If there is a slightly better version
with which to start with, I would greatly like everyone's opinion.

>From the log it would seem that the xen_git.bb in the meta-virtualization
layer is being called and thus the recipe is attempting to compile the
newest version of Xen.

So my second question would be, what version of Xen should I point towards
for the board I am using?

I am sorry for the completely newcomer questions, but I hope to someday
soon be able to help with Xen ARM development.

Best regards,

2018年12月22日(土) 21:21 Andrii Anisov <Andrii_Anisov@epam.com>:

> Hello Jairo,
>
> From: LOPEZ, FUENTES NACARINO Jairo Eduardo <jairo@ruri.waseda.jp>
> Sent: Saturday, December 22, 2018 3:55 AM
> To: Andrii Anisov; Iurii Artemenko
> Subject: RT Xen on ARM - R-Car series
>
> > My name is Jairo Lopez.
>
> > I am currently working as a doctorate student at Waseda University in
> the area of distributed systems.
>
> > We have previously used the R-Car M3 Starter Kit Pro and R-Car H3
> Starter Kit Premier
> > (
> https://www.renesas.com/us/en/solutions/automotive/adas/solution-kits/r-car-starter-kit.html)
> for some
> > demos and were interested in using them to test Xen on these machines.
> Since we are looking at
> > real-time distributed systems, your work on real-time for Xen greatly
> interests me.
>
> Thank you for your interest in XEN and RT in XEN. I hope you'll have great
> progress in your work and enrich XEN hypervisor with your findings.
>
> > I have attempted to use the Salvator-X guidelines (
> https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/Salvator-X)
> on
> > the Xen Wiki to try to test Xen on the above mentioned machines
>
> What SoC revisions do you have on your boards? Keep in mind this [1],
> although it should not be a problem for you yet.
>
> > and although the build succeeds
>
> I hope you built x3ulcb targets instead of salvator-x. BTW, the BSP
> mentioned in the wiki is pretty old. Me currently using 3.9. But it should
> not be a big problem on this stage.
>
> > I am left with a wonderful empty screen.
> And what do you see in a console? Any logs?
>
> > It is currently possible to boot Xen on the R-Car M3 or R-Car H3?
> Yes, sure. Our team constantly work with R-Car Gen3 based boards.
> Unfortunately, Renesas BSP still needs some adjustments to get XEN built
> and run with it.
>
> > If my laboratory is keen on getting Xen working on these machines, how
> could we go on about doing this?
> Carefully follow instructions. Provide detailed descriptions of your steps
> and results (build/boot logs) in case something went wrong on your site.
>
> ps. You know, XEN is an open-source project, it's better to ask questions
> through the mailing list [2]. You might have more answers hints and
> opinions from the community. I've copied this email to the list for you.
>
> [1]
> https://elinux.org/R-Car/Boards/Yocto-Gen3#Known_issues_and_limitations
> [2] https://www.xenproject.org/help/mailing-list.html
>
> ANDRII ANISOV
>

[-- Attachment #1.2: Type: text/html, Size: 13646 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

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