Xen project Mailing List

Hi Julien, thanks for the suggestions.

I do have a dtb file that works with the (debian stretch) image that is on the boot partition.

Initially "fdt /" at the u-boot prompt yields "No FDT memory address configured."

However, if I execute "fdt addr 0x01f00000" and then "fdt header" I can see the expected magic = 0xd00dfeed.

Starting from reset, here's what I'm trying at the u-boot prompt:

=> fdt addr 0x01f00000

=> set devtype mmc

=> set devnum 1

=> set distro_bootpart 6

=> run boot_efi_binary

reading efi/boot/bootaa64.efi

885072 bytes read in 128 ms (6.6 MiB/s)

## Starting EFI application at 02000000 ...

Card did not respond to voltage select!

mmc_init: -95, time 9

Scanning disk rksdmmc@xxxxxxxxxxxx...

Found 2 disks

Xen 4.11-rc (c/s Tue May 1 09:03:13 2018 +0100 git:0306a1311d) EFI loader

Couldn't obtain the File System Protocol Interface: ErrCode: 0x8000000000000003

## Application terminated, r = 0

So the FDT_ERR_BADMAGIC is eliminated but the "ErrCode: 0x8000000000000003" remains.

I'm not clear what this error code means. Any help appreciated!

On Thu, May 24, 2018 at 7:34 AM, Julien Grall <julien.grall@xxxxxxx> wrote:

(+Andre)

On 24/05/18 14:35, Todd Stellanova wrote:

Hello,

Hi Todd,

I have CCed Andre who has some knowledge about UEFI in U-boot.

I'm trying to get Xen running on the Rock64 SBC (Rockchip RK3328).
The long details of my setup are here: https://forum.pine64.org/showthread.php?tid=6059

Basically I'm at a point where I am able to manually kick off efi boot from a uboot command line and getting a couple of errors (FDT_ERR_BADMAGIC and one that looks like it's coming from the EFI loader)-- see the output from uboot below.

Any suggestions on what to try next? Thanks for any ideas.

=> set devtype mmc

=> set devnum 1

=> set distro_bootpart 6

=> run boot_efi_binary

reading efi/boot/bootaa64.efi

885072 bytes read in 129 ms (6.5 MiB/s)

libfdt fdt_check_header(): FDT_ERR_BADMAGIC

## Starting EFI application at 02000000 ...

Card did not respond to voltage select!

mmc_init: -95, time 10

Scanning disk rksdmmc@xxxxxxxxxxxx <mailto:rksdmmc@xxxxxxxxxxxx>...

Scanning disk rksdmmc@xxxxxxxxxxxx <mailto:rksdmmc@xxxxxxxxxxxx>...

Found 2 disks

Xen 4.11-rc (c/s Tue May 1 09:03:13 2018 +0100 git:0306a1311d) EFI loader

Couldn't obtain the File System Protocol Interface: ErrCode: 0x8000000000000003

I suspect the File System Protocol Interface error is related to the "FDT_ERR_BADMAGIC" above. The latter usually indicates that U-boot was not able to find the FDT at the emplacement provided.

Do you know if the firmware provide a Device-Tree? You can check with from the U-boot prompt with "fdt /". You should get some output with it.
If not you will need to load a Device-Tree from a storage or network.

Cheers,

--
Julien Grall

Re: [Xen-users] Booting xen using uboot+efi on Rock64