Re: AARCH64 booting

[Jared McNeill <jmcneill%invisible.ca@localhost>]

Hi Robert --

For 64-bit images you need to use "booti" instead of "bootm". Typical 
sequence is:

  fatload mmc 0 ${kernel_addr_r} netbsd.img
  fatload mmc 0 ${fdt_addr_r} ${fdtfile}
  fdt addr ${fdt_addr_r}
  booti ${kernel_addr_r} - ${fdt_addr_r}

Mainline U-Boot supports ODROID-C2, I strongly suggest you use that 
instead of the vendor binaries.

Cheers,
Jared

On Thu, 17 May 2018, Robert Swindells wrote:

> What is the expected means of booting an aarch64 kernel with u-boot ?
>
> It looks to me as if the u-boot-mkimg.sh script doesn't know anything
> about aarch64 and the arguments supplied to it from mk.generic64 don't
> look complete.
>
> I'm trying to get something to boot on an ODROID-C2 and just wondering
> what route to go.
>
> I suspect that the u-boot binary supplied by Hardkernel on their disk
> images doesn't support legacy images.
>
> I have created a package to build u-boot for this board but not played
> with it yet.