Re: dtb filename mismatch prevents booting

[Oliver Graute <oliver.graute@gmail.com>]

On 10/02/16, Maciej Borzecki wrote:
> 
> > Dnia 10 luty 2016 o 17:16 Oliver Graute <oliver.graute@gmail.com> napisał(a):
> >
> >
> > Hello list,
> >
> > if I try to boot from my yocto generated SD-card image my u-boot can't
> > start the kernel because the imx6ul-14x14-evk.dtb is missing.
> >
> >
> > reading boot.scr
> > ** Unable to read file boot.scr **
> > reading zImage
> > 5072288 bytes read in 328 ms (14.7 MiB/s)
> > Booting from mmc ...
> > reading imx6ul-14x14-evk.dtb
> > ** Unable to read file imx6ul-14x14-evk.dtb **
> > Kernel image @ 0x82000000 [ 0x000000 - 0x4d65a0 ]
> >
> > Starting kernel ...
> >
> >
> > In my /boot folder I saw a dtb file, but the filename is a bit different.
> >
> > zImage-imx6ul-14x14-evk.dtb instead of imx6ul-14x14-evk.dtb
> >
> > So I changed these filename manually and my Image is booting.
> >
> > mv zImage-imx6ul-14x14-evk.dtb imx6ul-14x14-evk.dtb
> > »zImage-imx6ul-14x14-evk.dtb“ -> »imx6ul-14x14-evk.dtb“
> >
> > What is the right way to define these dtb filename?
> >
> > some ideas whats going wrong here?
> >
> 
> IIRC the usual way was to add kernel-devicetree package and let u-boot
> pick the proper dtb during boot.
> 
> As for IMAGE_BOOT_FILES, you can tell wic to automatically rename files
> by passing the desired name after a semicolon like this:
> 
>   IMAGE_BOOT_FILES = "zImage zImage-imx6ul-14x14-evk.dtb;mx6ul-14x14-evk.dtb"

ok that worked for me, I changed it like this

-IMAGE_BOOT_FILES = "zImage zImage-imx6ul-14x14-evk.dtb"
+IMAGE_BOOT_FILES = "zImage zImage-imx6ul-14x14-evk.dtb;imx6ul-14x14-evk.dtb"

now the Image is directly booting without manually renaming.

thx for your help

Best Rgeards,

Oliver