Thanks again, Samual, for all your help.
Still not getting there:
=> booti ${kernel_addr_r} ${ramdisk_addr_r}:0 ${fdt_addr_r}
Moving Image from 0x40040000 to 0x40200000, end=415e10d8
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
I will read up on "device trees" but I am not sure if I am responsible for
setting that up before booting?
On Wed, May 25, 2022 at 4:42 PM Samuel Holland <[email protected]> wrote:
> Hi Bram,
>
> On 5/25/22 2:10 PM, Bram Stolk wrote:
> > I have been following these instructions:
> > https://linux-sunxi.org/Allwinner_Nezha#Mainline_kernel
> >
> > But u-boot does not accept my kernel image.
> > I tried both Image.gz and Image
> >
> > => ext4load mmc 0:1 ${kernel_addr_r} Image
> > 20515704 bytes read in 1906 ms (10.3 MiB/s)
> > => bootm ${kernel_addr_r}
> > Wrong Image Format for bootm command
> > ERROR: can't get kernel image!
> >
> > The load command works fine. But when trying to boot it from memory, the
> format
> > is not accepted?
>
> "bootm" expects the kernel to be wrapped in a U-Boot-specific header. To
> boot an
> unmodified Linux "Image" file, you need to use the booti command[1].
>
> There is a (rather non-obvious, I admit) note to this effect on the
> wiki[2],
> which I just edited to note that it also applies to RISC-V.
>
> Regards,
> Samuel
>
> [1]: https://u-boot.readthedocs.io/en/latest/usage/cmd/booti.html
> [2]: https://linux-sunxi.org/U-Boot#Booting_with_boot.cmd
>
--
Owner/Director of Game Studio Abraham Stolk Inc.
Vancouver BC, Canada
[email protected]
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web, visit
https://groups.google.com/d/msgid/linux-sunxi/CABYXEkvNdz6r4VEjXkKquRteBmvDY9UehK-3d5Bxuh37eLOvkQ%40mail.gmail.com.
