On Fri, Sep 8, 2017 at 1:17 PM, Andrea Galbusera <giz...@gmail.com> wrote: > On Fri, Sep 8, 2017 at 11:22 AM, Paul Barker <pbar...@toganlabs.com> wrote: >> >> On Fri, Sep 8, 2017 at 10:18 AM, Andrea Galbusera <giz...@gmail.com> >> wrote: >> > >> > The only particular configuration I have here (and probably did not have >> > when testing it a while ago) as you can guess by the missing target name >> > is >> > that i boot to U-Boot with KERNEL_IMAGETYPE = "uImage". Does this ring a >> > bell to anyone? >> >> Good timing, this is what I'm actually looking at today! The arm64 >> arch does not support the legacy "uImage" format. We need to use the >> "Image" format (or "Image.gz") and use "booti" in u-boot instead of >> "bootm". >> >> For now, you'll need to build without u-boot for raspberrypi3-64 by >> unsetting KERNEL_IMAGETYPE. > > > Understood, maybe we can test transitioning toward using "booti" and any of > the modern image formats for both raspberrypi3 and raspberrypi-64? This > should keep the platforms more aligned hence easing layer maintenance... >
Unfortunately "booti" is only supported on arm64 and "bootm" is only supported on 32-bit arm. I'm leaning towards having one variable, RPI_USE_U_BOOT, which when set to "1" will set KERNEL_IMAGETYPE correctly and enable u-boot. Thanks, -- Paul Barker Togán Labs Ltd -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto