Re: Loading L4 after Uboot on ZynqMP

2025-04-10 Thread Moshe Kravchik 
Hi,
I managed to get it working using the image I built myself:
module[arch=arm64,fname=linux,uncompress] Image.gz
Thanks a lot,
Moshe

From: Adam Lackorzynski 
Sent: Tuesday, April 8, 2025 7:36 AM
To: Moshe Kravchik ; [email protected] 

Subject: Re: Loading L4 after Uboot on ZynqMP

Hi Moshe,

interesting. The printf of the error is in
l4/pkg/uvmm/server/src/binary_loader_linux_compressed.cc, could you make
that:
Err().printf("zlib decompression error(%d): %s\n", err, strm.msg);
such that we also see the 'err' as well?


Thanks, Adam

On Mon Apr 07, 2025 at 12:41:30 +, Moshe Kravchik wrote:
> However, I still encounter and error when trying to run the VM-basic sample.
> It starts well, but fails while loading the kernel:
> VMM[main]: Loading kernel...
> VMM[loader]: Detected gzip compressed image: uncompressing (13618690 -> 
> 41658880)
> VMM: FATAL: zlib decompression error: (null)
>
> The size corresponds to the size of 
> https://l4re.org/download/Linux-kernel/arm64/Image-6.6.8 (while appears in 
> modules.list)
>
> Any advice?
> Best regards,
> Moshe
> 
> From: Moshe Kravchik 
> Sent: Monday, April 7, 2025 3:19 PM
> To: Adam Lackorzynski ; [email protected] 
> 
> Subject: Re: Loading L4 after Uboot on ZynqMP
>
> Hi Adam,
>
> I tried with the device tree and indeed I can run the bootstrapper_hello 
> sample!
>
> Thanks a lot!
> Moshe
> 
> From: Adam Lackorzynski 
> Sent: Sunday, April 6, 2025 12:08 PM
> To: [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 0x0c0 - 0x).
>
>
> Adam
>
> On Thu Apr 03, 2025 at 11:27:34 -, [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 0x0c0 bootstrap_hello.uimage
> >
> > ZynqMP> bootm 0x0c0
> > ## Booting kernel from Legacy Image at 00c0 ...
> >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: 0100
> >Entry Point:  0100
> >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 0x100 bootstrap_hello-cfg.rawimage
> > 2149176 bytes read in 151 ms (13.6 MiB/s)
> > ZynqMP> go 0x100
> > ## 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 ( - 7fff)
> >   RAM:  - 7fff: 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

Adam
--
Adam [email protected]
  Lackorzynski http://os.inf.tu-dresden.de/~adam/
___
l4-hackers mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Re: Loading L4 after Uboot on ZynqMP

2025-04-07 Thread Adam Lackorzynski 
Hi Moshe,

interesting. The printf of the error is in
l4/pkg/uvmm/server/src/binary_loader_linux_compressed.cc, could you make
that:
Err().printf("zlib decompression error(%d): %s\n", err, strm.msg);
such that we also see the 'err' as well?


Thanks, Adam

On Mon Apr 07, 2025 at 12:41:30 +, Moshe Kravchik wrote:
> However, I still encounter and error when trying to run the VM-basic sample.
> It starts well, but fails while loading the kernel:
> VMM[main]: Loading kernel...
> VMM[loader]: Detected gzip compressed image: uncompressing (13618690 -> 
> 41658880)
> VMM: FATAL: zlib decompression error: (null)
> 
> The size corresponds to the size of 
> https://l4re.org/download/Linux-kernel/arm64/Image-6.6.8 (while appears in 
> modules.list)
> 
> Any advice?
> Best regards,
> Moshe
> 
> From: Moshe Kravchik 
> Sent: Monday, April 7, 2025 3:19 PM
> To: Adam Lackorzynski ; [email protected] 
> 
> Subject: Re: Loading L4 after Uboot on ZynqMP
> 
> Hi Adam,
> 
> I tried with the device tree and indeed I can run the bootstrapper_hello 
> sample!
> 
> Thanks a lot!
> Moshe
> 
> From: Adam Lackorzynski 
> Sent: Sunday, April 6, 2025 12:08 PM
> To: [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 0x0c0 - 0x).
> 
> 
> Adam
> 
> On Thu Apr 03, 2025 at 11:27:34 -, [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 0x0c0 bootstrap_hello.uimage
> >
> > ZynqMP> bootm 0x0c0
> > ## Booting kernel from Legacy Image at 00c0 ...
> >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: 0100
> >Entry Point:  0100
> >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 0x100 bootstrap_hello-cfg.rawimage
> > 2149176 bytes read in 151 ms (13.6 MiB/s)
> > ZynqMP> go 0x100
> > ## 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 ( - 7fff)
> >   RAM:  - 7fff: 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

Adam
-- 
Adam [email protected]
  Lackorzynski http://os.inf.tu-dresden.de/~adam/
___
l4-hackers mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Re: Loading L4 after Uboot on ZynqMP

2025-04-07 Thread Moshe Kravchik 
However, I still encounter and error when trying to run the VM-basic sample.
It starts well, but fails while loading the kernel:
VMM[main]: Loading kernel...
VMM[loader]: Detected gzip compressed image: uncompressing (13618690 -> 
41658880)
VMM: FATAL: zlib decompression error: (null)

The size corresponds to the size of 
https://l4re.org/download/Linux-kernel/arm64/Image-6.6.8 (while appears in 
modules.list)

Any advice?
Best regards,
Moshe

From: Moshe Kravchik 
Sent: Monday, April 7, 2025 3:19 PM
To: Adam Lackorzynski ; [email protected] 

Subject: Re: Loading L4 after Uboot on ZynqMP

Hi Adam,

I tried with the device tree and indeed I can run the bootstrapper_hello sample!

Thanks a lot!
Moshe

From: Adam Lackorzynski 
Sent: Sunday, April 6, 2025 12:08 PM
To: [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 0x0c0 - 0x).


Adam

On Thu Apr 03, 2025 at 11:27:34 -, [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 0x0c0 bootstrap_hello.uimage
>
> ZynqMP> bootm 0x0c0
> ## Booting kernel from Legacy Image at 00c0 ...
>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: 0100
>Entry Point:  0100
>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 0x100 bootstrap_hello-cfg.rawimage
> 2149176 bytes read in 151 ms (13.6 MiB/s)
> ZynqMP> go 0x100
> ## 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 ( - 7fff)
>   RAM:  - 7fff: 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]

Re: Loading L4 after Uboot on ZynqMP

2025-04-07 Thread Moshe Kravchik 
Hi Adam,

I tried with the device tree and indeed I can run the bootstrapper_hello sample!

Thanks a lot!
Moshe

From: Adam Lackorzynski 
Sent: Sunday, April 6, 2025 12:08 PM
To: [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 0x0c0 - 0x).


Adam

On Thu Apr 03, 2025 at 11:27:34 -, [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 0x0c0 bootstrap_hello.uimage
>
> ZynqMP> bootm 0x0c0
> ## Booting kernel from Legacy Image at 00c0 ...
>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: 0100
>Entry Point:  0100
>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 0x100 bootstrap_hello-cfg.rawimage
> 2149176 bytes read in 151 ms (13.6 MiB/s)
> ZynqMP> go 0x100
> ## 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 ( - 7fff)
>   RAM:  - 7fff: 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]

Re: Loading L4 after Uboot on ZynqMP

2025-04-06 Thread Adam Lackorzynski 
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 0x0c0 - 0x).


Adam

On Thu Apr 03, 2025 at 11:27:34 -, [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 0x0c0 bootstrap_hello.uimage
> 
> ZynqMP> bootm 0x0c0
> ## Booting kernel from Legacy Image at 00c0 ...
>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: 0100
>Entry Point:  0100
>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 0x100 bootstrap_hello-cfg.rawimage
> 2149176 bytes read in 151 ms (13.6 MiB/s)
> ZynqMP> go 0x100
> ## 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 ( - 7fff)
>   RAM:  - 7fff: 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]