[yocto] fitImage and initramfs

[Rick Altherr]

Have you tried manually extracting the .xz it is having trouble with?  The
bundling process for zImage and fitImage are different but both involve
extracting the initramfs image first and they use the same copy_initramfs
method in kernel.bbclass to do it.  Setting INITRAMFS_IMAGE to
"core-image-minimal" is a bit odd though as that is typically the fully
built rootfs, not just the initramfs.  That might also introduce a
dependency problem as core-image-minimal depends on the kernel.  Did you
mean to use "core-image-minimal-initramfs" instead?

On Wed, Dec 21, 2016 at 8:50 AM, Hamish Guthrie <Hamish.Guthrie at kistler.com>
wrote:

> Hi List,
>
> I am trying to create a fitImage including an initramfs. I am able to
> create a fitImage without an initramfs, and I am able to create a zImage
> with an initramfs. If I try to create a fitImage with an initramfs, I
> receive the following error:
>
> | Creating a kernel image with a bundled initramfs...
> | Copying initramfs into ./usr ...
> | xz decompressing image
> | xz: /home/hamish/build/tmp/work/beaglebone-poky-linux-gnueabi/
> linux-yocto/4.8.12+gitAUTOINC+926c93ae07_85dc85153c-r0/
> linux-beaglebone-standard-build/usr/core-image-minimal-beaglebone.cpio.xz:
> Unexpected end of input
>
> I have added the following to my machine .conf file:
>
> KERNEL_IMAGETYPES = "zImage fitImage"
> KERNEL_CLASSES += "kernel-fitimage"
>
> INITRAMFS_IMAGE = "core-image-minimal"
> INITRAMFS_IMAGE_BUNDLE = "1"
>
> Any ideas would be most welcome.
>
> Hamish
> -
> --
> _______________________________________________
> 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/20161221/42eee73d/attachment.html>