Hi Adam, I tried with the device tree and indeed I can run the bootstrapper_hello sample!
Thanks a lot! Moshe ________________________________ From: Adam Lackorzynski <[email protected]> Sent: Sunday, April 6, 2025 12:08 PM To: [email protected] <[email protected]>; [email protected] <[email protected]> Subject: Re: Loading L4 after Uboot on ZynqMP Hi Moshe, Could you share some more info about the u-boot version that is being used on your ZynqMP device? Please also try to load a device-tree with bootm. The error message could just indicate a device tree is missing. Simply use the one you probably find on the flash (bootm 0x0ffffc0 - 0x....). Adam On Thu Apr 03, 2025 at 11:27:34 -0000, [email protected] wrote: > I'm trying to run L4 on a Xilinx ZyncMP board. The board runs Uboot from ROM > and then I tried to load L4 as described in https://l4re.org/bsp/zynqmp.html. > > > However, loading a uimage fails, I'm getting an error: > > ZynqMP> fatload usb 0:1 0x0ffffc0 bootstrap_hello.uimage > > ZynqMP> bootm 0x0ffffc0 > ## Booting kernel from Legacy Image at 00ffffc0 ... > Image Name: L4 Image #8 > Created: 2025-03-31 14:14:32 UTC > Image Type: AArch64 Linux Kernel Image (uncompressed) > Data Size: 1530680 Bytes = 1.5 MiB > Load Address: 01000000 > Entry Point: 01000000 > Verifying Checksum ... OK > XIP Kernel Image > FDT and ATAGS support not compiled in > > ### ERROR ### Please RESET the board ### > > > I tried to use rawimage, but there I get to the following problem: > ZynqMP> fatload usb 0:1 0x1000000 bootstrap_hello-cfg.rawimage > 2149176 bytes read in 151 ms (13.6 MiB/s) > ZynqMP> go 0x1000000 > ## S� > L4 Bootstrapper > Build: #15 Thu Apr 3 11:39:37 IDT 2025, 9.4.0 > Scanning up to 2048 MB RAM, starting at offset 32MB > Memory size is 2048MB (00000000 - 7fffffff) > RAM: 0000000000000000 - 000000007fffffff: 2097152kB > Total RAM: 2048MB > Scanning fiasco -serial_esc > Scanning sigma0 > Scanning moe rom/hello.cfg > Compressed modules: > cannot decompress at 0x10a8000, try 0x11bc000 > Uncompressing modules (modaddr = 0x11bc000 (backwards)): > mod06: 0x126c000-0x1296b38: hello > mod05: 0x126b000-0x126b080: hello.cfg > mod04: 0x11e1000-0x126a118: ned > mod03: 0x11bc000-0x11e0c40: l4re > Loading fiasco > found node 0 kernel info page (via ELF) at 0x3000 > L4Re is configured for EL2 mode (virtualization / hypervisor) but got started > in EL1 by the boot-loader. Please change your boot-loader to start L4Re in > EL2 mode. > > I'm not sure how to proceed from here. The Uboot is loaded from the board's > ROM and is running at EL2. > > Any help is appreciated, > Moshe
_______________________________________________ l4-hackers mailing list -- [email protected] To unsubscribe send an email to [email protected]
