On Thu, 2019-01-24 at 15:52 +0800, Robert Yang wrote: > > On 1/24/19 3:31 PM, Robert Yang wrote: > > Hi Richard.L, > > > > On 1/24/19 3:09 PM, Richard Leitner wrote: > > > Hi, > > > I'm currently facing issues on how to include a fitImage with > > > devicetrees and > > > a INITRAMFS_IMAGE in my rootfs image. > > I think that set both INITRAMFS_IMAGE and INITRAMFS_IMAGE_BUNDLE should > work, > you have set INITRAMFS_IMAGE, so also set: > > INITRAMFS_IMAGE_BUNDLE = "1"
I'm n not sure bundling the initramfs with the kernel is the best approach when using a fitImage. After all, the purpose of the FIT is to describe to U-Boot the individual components and their location already. Cheers, Andre' > > // Robert > > > > > My config is something like: > > > > > > KERNEL_IMAGETYPE = "fitImage" > > > KERNEL_CLASSES = "kernel-fitimage" > > > KERNEL_DEVICETREE = "a.dtb b.dtb c.dtb" > > > INITRAMFS_IMAGE = "initramfs-mine" > > > > > > To include the "normal" fitImage without the initramfs in the rootfs > > > the > > > following works: > > > > > > IMAGE_INSTALL_append += " kernel-image" > > > > > > > > > When digging around a little bit I found that the fitImage-initramfs- > > > mine is > > > deployed to tmp/deploy/images but there's no package including that > > > file. > > > > fitImage-initramfs-mine is an image, so it is not in any package, it is > > handled by kernel.bbclass, you can check it for more info. > > > > // Robert > > > > > Therefore I'm unable to include it via IMAGE_INSTALL. > > > > > > Am I missing something? > > > Is anybody of you aware of a solution? > > > Does kernel-fitimage and kernel.bbclass offer this at all? > > > > > > Any help would be greatly appreciated! Thanks! > > > > > > regards;Richard.L -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
