From mboxrd@z Thu Jan 1 00:00:00 1970 From: "LOPEZ, FUENTES NACARINO Jairo Eduardo" Subject: Re: RT Xen on ARM - R-Car series Date: Tue, 29 Jan 2019 02:20:32 +0900 Message-ID: References: <59df6425-f6de-fda1-a1a5-7d2774ff6796@gmail.com> <3aecad20-41f5-4249-46be-bfef80c88ea3@gmail.com> <623d0b16-8616-183c-d8d4-559ad81363ed@gmail.com> <7e217489-2c1a-c35f-d51f-0969654aa8cc@gmail.com> <4d078801-b804-06e7-ad5c-8032b1dbaa84@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2198472923921362570==" Return-path: In-Reply-To: <4d078801-b804-06e7-ad5c-8032b1dbaa84@gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" To: Andrii Anisov , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============2198472923921362570== Content-Type: multipart/alternative; boundary="0000000000006ff9960580802abf" --0000000000006ff9960580802abf Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Andrii, Thank you for your previous mail. I am sorry for taking so long to answer. The rest of the mail is inline 2019=E5=B9=B41=E6=9C=8822=E6=97=A5(=E7=81=AB) 18:00 Andrii Anisov : > > > On 22.01.19 12:45, LOPEZ, FUENTES NACARINO Jairo Eduardo wrote: > > Yes. Since you pointed out that the U-boot version was not what you > expected, I downgraded to Yocto 3.9. I am able to boot Linux 4.14 but Xen= , > of any version continues to give me absolutely no output. > Ok, let you try to start with earlyprintk. Follow next steps > - Go to /build/tmp/work/aarch64-poky-linux/xen/ version>/git/ > - Run `make distclean` > - Go to /build/tmp/work/aarch64-poky-linux/xen/ version>/temp/ > - Edit a file hidden behind a symbolic link `run.do_compile`: find > `oe_runmake_call()` function, to the line `make -j8 STDVGA....` add > `CONFIG_EARLY_PRINTK=3Drcar3`, correct `debug=3Dy`. > - Run `./run.do_configure` > - Run ./run.do_compile > - Go to /build/tmp/work/aarch64-poky-linux/xen/ version>/git/xen/ > - Run `mkimage -A arm64 -C none -T kernel -a 0x78080000 -e 0x78080000 -= n > "XEN" -d xen xen.uImage` > - Boot your board with just created xen.uImage. > > I was able to compile the Xen image with earlyprintk without issue. It is comforting to get some sort of feedback from the device, even if it is failing. > But I'm 99 percents sure you will see memory initialization error from > XEN, so you should merge your memory nodes. > > > Do not forget following: > > > > > > memory@48000000 { > > > > device_type =3D "memory"; > > > > /* first 128MB is reserved for secure > area. */ > > > > reg =3D <0x0 0x48000000 0x0 0x38000000>; > > > > }; > > > > > > > > memory@600000000 { > > > > device_type =3D "memory"; > > > > reg =3D <0x6 0x00000000 0x0 0x40000000>; > > > > }; > > > Merge memory nodes to be sure u-boot do not duplicate memory > ranges. > > > > > > Is this merge also required for Renesas' Yocto 3.9? > Yes, we escalated the problem and the solution to Renesas, but 3.9 still > needs memory nodes merging. > They should have unset `CONFIG_ARCH_FIXUP_FDT` in a u-boot config. But > Yocto 3.9 still have `CONFIG_ARCH_FIXUP_FDT=3Dy` configured for u-boot. > > I was also able to make a compilable DTB file by merging the memory ranges. I used the following configuration: memory@48000000 { device_type =3D "memory"; /* first 128MB is reserved for secure area. */ reg =3D <0x0 0x48000000 0x0 0x38000000>, <0x6 0x00000000 0x= 0 0x40000000>; } > > > That my M3 is old sounds unfortunate. > > > What limitation for Xen would I have to live with, with a lack o= f > a IPMMU? > > I'm not 100% sure, but as long as it works, there should not be > other issues. > > You just will not be able to passthrough peripherals to guest > domains (that is what IPMMU is needed for). > > > > > > Ah, it is a shame that I won't be able to passthrough peripherals to > guest domains. Fortunately at this point in time I only need to benchmark > the CPUs so this should not affect me. > It must be ok from the technical point of view. > > -- > Sincerely, > Andrii Anisov. > When attempting to boot the Xen image created I did get print messages but I get the following: [ 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=3D0x53 [ 0.030989] NOTICE: BL2: DDR3200(rev.0.33)NOTICE: [COLD_BOOT]NOTICE: ..0 [ 0.086118] NOTICE: BL2: DRAM Split is 2ch [ 0.090003] NOTICE: BL2: QoS is default setting(rev.0.19) [ 0.095507] NOTICE: BL2: Lossy Decomp areas [ 0.099680] NOTICE: Entry 0: DCMPAREACRAx:0x80000540 DCMPAREACRBx:0x570 [ 0.106765] NOTICE: Entry 1: DCMPAREACRAx:0x40000000 DCMPAREACRBx:0x0 [ 0.113677] NOTICE: Entry 2: DCMPAREACRAx:0x20000000 DCMPAREACRBx:0x0 [ 0.120591] NOTICE: BL2: v1.4(release):15dba6b [ 0.125081] NOTICE: BL2: Built : 11:34:26, Jan 21 2019 [ 0.130269] NOTICE: BL2: Normal boot [ 0.133914] NOTICE: BL2: dst=3D0xe6320d00 src=3D0x8180000 len=3D512(0x2= 00) [ 0.140297] NOTICE: BL2: dst=3D0x43f00000 src=3D0x8180400 len=3D6144(0x= 1800) [ 0.146918] NOTICE: BL2: dst=3D0x44000000 src=3D0x81c0000 len=3D65536(0= x10000) [ 0.154148] NOTICE: BL2: dst=3D0x44100000 src=3D0x8200000 len=3D1048576(0x100000) [ 0.168971] NOTICE: BL2: dst=3D0x50000000 src=3D0x8640000 len=3D1048576(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 Hit any key to stop autoboot: 0 =3D> bootm 0x48080000 - 0x48000000 ## Booting kernel from Legacy Image at 48080000 ... Image Name: XEN Image Type: AArch64 Linux Kernel Image (uncompressed) Data Size: 886096 Bytes =3D 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 ... - UART enabled - - CPU 00000000 booting - - Current EL 00000004 - - Xen must be entered in NS EL2 mode - - Please update the bootloader - - Boot failed - I thought that using the U-boot image from Yocto 3.9 would automatically let me avoid the issue with boot loader entering the wrong mode. As I mentioned before I am using the rocko branches from meta-virtualization and meta-selinux as shown below: Build Configuration: BB_VERSION =3D "1.36.0" BUILD_SYS =3D "x86_64-linux" NATIVELSBSTRING =3D "universal-4.9" TARGET_SYS =3D "aarch64-poky-linux" MACHINE =3D "m3ulcb" DISTRO =3D "poky" DISTRO_VERSION =3D "2.4.2" TUNE_FEATURES =3D "aarch64 cortexa57-cortexa53" TARGET_FPU =3D "" SOC_FAMILY =3D "rcar-gen3:r8a7796" meta meta-poky meta-yocto-bsp =3D "tmp:342fbd6a3e57021c8e28b124b3adb241936f3d9d" meta-rcar-gen3 =3D "tmp:fd078b6ece537d986852cb827bd21e022a797b2f" meta-optee =3D "tmp:75dfb67bbb14a70cd47afda9726e2e1c76731885" meta-oe meta-python meta-networking =3D "tmp:dacfa2b1920e285531bec55cd2f08743390aaf57" meta-selinux =3D "rocko:d855c624f32c5e599bf27e06cb8f5b25b3aae12d" meta-virtualization =3D "rocko:b704c689b67639214b9568a3d62e82df27e9434f" meta-rcar-gen3-xen =3D "lastest_xen:cc6e6e1c07197207769331b0532fc88a9165a855" I have no idea if that affects the u-boot creation, but I thought I might as well mention that. Once again thank you for all the help. If there is any other information I can give you, please let me know. Best regards, Jairo --0000000000006ff9960580802abf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Andrii,

Thank you for your previous mail.

I am sorr= y for taking so long to answer.

The rest of the ma= il is inline

2019=E5=B9=B41=E6=9C=8822=E6=97=A5(=E7=81=AB) 18:00 A= ndrii Anisov <andrii.anisov@g= mail.com>:
But I'm 99 percents sure you will see memory initialization error from = XEN, so you should merge your memory nodes.

>=C2=A0 =C2=A0 =C2=A0Do not forget following:
>
>=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 memory@48000000 {
>=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 device_type =3D "memory";
>=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 /* first 128MB is reserved for secure area. */
>=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 reg =3D <0x0 0x48000000 0x0 0x38000000>;
>=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 };
>=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 memory@600000000 {
>=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 device_type =3D "memory";
>=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 reg =3D <0x6 0x00000000 0x0 0x40000000>;
>=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 };
>=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A0 =C2=A0Merge memory nodes to be s= ure u-boot do not duplicate memory ranges.
>
>
> Is this merge also required for Renesas' Yocto 3.9?
Yes, we escalated the problem and the solution to Renesas, but 3.9 still ne= eds memory nodes merging.
They should have unset `CONFIG_ARCH_FIXUP_FDT` in a u-boot config. But Yoct= o 3.9 still have `CONFIG_ARCH_FIXUP_FDT=3Dy` configured for u-boot.


I was also able to make a compilable D= TB file by merging the memory ranges. I used the following configuration:

=C2=A0memory@48000000 {
=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 device_t= ype =3D "memory";
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 /* first 128MB is reserved= for secure area. */
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 reg =3D <0x0 0x48000000 0x0 0x38000000= >,=C2=A0 <0x6 0x00000000 0x0 0x40000000>;
}

=C2=A0
>=C2=A0 =C2=A0 =C2=A0 > That my M3 is old sounds unfortunate.
>=C2=A0 =C2=A0 =C2=A0 > What limitation for Xen would I have to live = with, with a lack of a IPMMU?
>=C2=A0 =C2=A0 =C2=A0I'm not 100% sure, but as long as it works, the= re should not be other issues.
>=C2=A0 =C2=A0 =C2=A0You just will not be able to passthrough peripheral= s to guest domains (that is what IPMMU is needed for).
>
>
> Ah, it is a shame that I won't be able to passthrough peripherals = to guest domains. Fortunately at this point in time I only need to benchmar= k the CPUs so this should not affect me.
It must be ok from the technical point of view.

--
Sincerely,
Andrii Anisov.


When atte= mpting to boot the Xen image created I did get print messages but I get the= following:

[=C2=A0=C2=A0=C2=A0 0.000191] NOTICE:= =C2=A0 BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.21
[=C2=A0= =C2=A0=C2=A0 0.005753] NOTICE:=C2=A0 BL2: PRR is R-Car M3 Ver.1.0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
[=C2=A0=C2= =A0=C2=A0 0.010422] NOTICE:=C2=A0 BL2: Board is Starter Kit Rev.1.0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
[=C2=A0=C2=A0=C2=A0 0.015534] NOTICE:= =C2=A0 BL2: Boot device is HyperFlash(80MHz)=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
[=C2=A0=C2= =A0=C2=A0 0.020960] NOTICE:=C2=A0 BL2: LCM state is CM=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0
[=C2=A0=C2=A0=C2=A0 0.025002] NOTICE:=C2=A0 BL2: = AVS setting succeeded. DVFS_SetVID=3D0x53
[=C2=A0=C2=A0=C2=A0 0.030989] = NOTICE:=C2=A0 BL2: DDR3200(rev.0.33)NOTICE:=C2=A0 [COLD_BOOT]NOTICE:=C2=A0 = ..0
[=C2=A0=C2=A0=C2=A0 0.086118] NOTICE:=C2=A0 BL2: DRAM Split is 2ch[=C2=A0=C2=A0=C2=A0 0.090003] NOTICE:=C2=A0 BL2: QoS is default setting(r= ev.0.19)
[=C2=A0=C2=A0=C2=A0 0.095507] NOTICE:=C2=A0 BL2: Lossy Decomp a= reas
[=C2=A0=C2=A0=C2=A0 0.099680] NOTICE:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 Entry 0: DCMPAREACRAx:0x80000540 DCMPAREACRBx:0x570
[=C2=A0=C2=A0= =C2=A0 0.106765] NOTICE:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Entry 1: DCMPA= REACRAx:0x40000000 DCMPAREACRBx:0x0
[=C2=A0=C2=A0=C2=A0 0.113677] NOTICE= :=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Entry 2: DCMPAREACRAx:0x20000000 DCMP= AREACRBx:0x0
[=C2=A0=C2=A0=C2=A0 0.120591] NOTICE:=C2=A0 BL2: v1.4(relea= se):15dba6b
[=C2=A0=C2=A0=C2=A0 0.125081] NOTICE:=C2=A0 BL2: Built : 11:= 34:26, Jan 21 2019
[=C2=A0=C2=A0=C2=A0 0.130269] NOTICE:=C2=A0 BL2: Norm= al boot
[=C2=A0=C2=A0=C2=A0 0.133914] NOTICE:=C2=A0 BL2: dst=3D0xe6320d0= 0 src=3D0x8180000 len=3D512(0x200)
[=C2=A0=C2=A0=C2=A0 0.140297] NOTICE:= =C2=A0 BL2: dst=3D0x43f00000 src=3D0x8180400 len=3D6144(0x1800)
[=C2=A0= =C2=A0=C2=A0 0.146918] NOTICE:=C2=A0 BL2: dst=3D0x44000000 src=3D0x81c0000 = len=3D65536(0x10000)
[=C2=A0=C2=A0=C2=A0 0.154148] NOTICE:=C2=A0 BL2: ds= t=3D0x44100000 src=3D0x8200000 len=3D1048576(0x100000)
[=C2=A0=C2=A0=C2= =A0 0.168971] NOTICE:=C2=A0 BL2: dst=3D0x50000000 src=3D0x8640000 len=3D104= 8576(0x100000)

</ redacted u-boot image loa= d information>

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

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

MMC:=C2= =A0=C2=A0 sh-sdhi: 0, sh-sdhi: 1
In:=C2=A0=C2=A0=C2=A0 serial
Out:=C2= =A0=C2=A0 serial
Err:=C2=A0=C2=A0 serial
Net:=C2=A0=C2=A0 ravb
Hit= any key to stop autoboot:=C2=A0 0

=3D> bootm 0x48080= 000 - 0x48000000
## Booting kernel from Legacy Image at 48080000 ...
= =C2=A0=C2=A0 Image Name:=C2=A0=C2=A0 XEN
=C2=A0=C2=A0 Image Type:=C2=A0= =C2=A0 AArch64 Linux Kernel Image (uncompressed)
=C2=A0=C2=A0 Data Size:= =C2=A0=C2=A0=C2=A0 886096 Bytes =3D 865.3 KiB
=C2=A0=C2=A0 Load Address:= 78080000
=C2=A0=C2=A0 Entry Point:=C2=A0 78080000
=C2=A0=C2=A0 Verif= ying Checksum ... OK
## Flattened Device Tree blob at 48000000
=C2=A0= =C2=A0 Booting using the fdt blob at 0x48000000
=C2=A0=C2=A0 Loading Ker= nel Image ... OK
=C2=A0=C2=A0 Using Device Tree in place at 000000004800= 0000, end 0000000048013bc0

Starting kernel ...

- UART enabled= -
- CPU 00000000 booting -
- Current EL 00000004 -
- Xen must be = entered in NS EL2 mode -
- Please update the bootloader -
- Boot fail= ed -

I thought that using the U-boot image fro= m Yocto 3.9 would automatically let me avoid the issue with boot loader ent= ering the wrong mode.

As I mentioned before I = am using the rocko branches from meta-virtualization and meta-selinux as sh= own below:

Build Configuration:
BB_VERSION=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D "1.36.0&= quot;
BUILD_SYS=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 =3D "x86_64-linux"
NATIVELSBSTRING=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 =3D "universal-4.9"
TARGET_SYS=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D "aarch64-poky-linux&quo= t;
MACHINE=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 =3D "m3ulcb"
DISTRO=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D "poky= "
DISTRO_VERSION=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D "2.4.= 2"
TUNE_FEATURES=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D &quo= t;aarch64 cortexa57-cortexa53"
TARGET_FPU=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D ""
SOC_FAMILY=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D "rcar-gen3:= r8a7796"
meta=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
meta-poky=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
meta-yocto-bsp=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D "tmp:342fbd6a3e57021c8e28b124b3adb2= 41936f3d9d"
meta-rcar-gen3=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D = "tmp:fd078b6ece537d986852cb827bd21e022a797b2f"
meta-optee=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D "tmp:75d= fb67bbb14a70cd47afda9726e2e1c76731885"
meta-oe=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
meta-python= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
meta-networking= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D "tmp:dacfa2b1920e285531bec55cd2f087= 43390aaf57"
meta-selinux=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 =3D "rocko:d855c624f32c5e599bf27e06cb8f5b25b3aae12d"
me= ta-virtualization=C2=A0 =3D "rocko:b704c689b67639214b9568a3d62e82df27e= 9434f"
meta-rcar-gen3-xen=C2=A0=C2=A0 =3D "lastest_xen:cc6e6e1= c07197207769331b0532fc88a9165a855"

I have= no idea if that affects the u-boot creation, but I thought I might as well= mention that.

Once again thank you for all the he= lp. If there is any other information I can give you, please let me know.

Best regards,

Jairo
--0000000000006ff9960580802abf-- --===============2198472923921362570== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cHM6Ly9saXN0 cy54ZW5wcm9qZWN0Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3hlbi1kZXZlbA== --===============2198472923921362570==--