[yocto] Problem building kernel FIT image with initramfs

[Rick Altherr]

AFAIK, FIT w/ initramfs works with linux-yocto.  I suspect this is a bug in
the freescale kernel recipe.

On Tue, Jul 18, 2017 at 6:01 AM, Martin Townsend <mtownsend1973 at gmail.com>
wrote:

> Sorry hit send before finishing email.
>
> So it looks like do_install and do_deploy are expecting
> fitImage-${INITRAMFS_IMAGE} so is this renaming required anymore? and
> if so is this a problem with the freescale kernel?
>
> Many Thanks,
> Martin.
>
> On Tue, Jul 18, 2017 at 1:58 PM, Martin Townsend
> <mtownsend1973 at gmail.com> wrote:
> > Hi,
> >
> > Using Yocto 2.3 (pyro) I was trying to create a FIT image with the 4.9
> > linux-fslc kernel and an initramfs image.  following the instructions
> > it failed during do_bundle_initramfs.  After debugging I found that it
> > moves the fitImage file to fitImage.bak and then runs a second pass
> > and renames the new fitImage to fitImage.initramfs but fitImage is
> > never created on this second pass but  fitImage-${INITRAMFS_IMAGE} is
> > created.
> >
> > If I comment out the line that does this rename every builds fine
> >
> > echo "Resoring Kernel Image"
> > for tp in $tmp_path ; do
> >   type=`echo $tp|cut -d "#" -f 1`
> >   linkpath=`echo $tp|cut -d "#" -f 2`
> >   realpath=`echo $tp|cut -d "#" -f 3`
> >   if [ -n "$realpath" ]; then
> >     mv -f $realpath $realpath.initramfs
> >     mv -f $realpath.bak $realpath
> >     ln -sf $linkpath.initramfs ${B}/${KERNEL_OUTPUT_DIR}/$type.initramfs
> >   else
> >
> >     #mv -f ${KERNEL_OUTPUT_DIR}/$type ${KERNEL_OUTPUT_DIR}/$type.
> initramfs
> >     mv -f ${KERNEL_OUTPUT_DIR}/$type.bak ${KERNEL_OUTPUT_DIR}/$type
> >   fi
> > done
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170725/fe9b41b2/attachment.html>