From: "Jeffrey Simons" <jeffrey.simons@boonedam.com>
To: Jeffrey Simons
<jeffrey.simons@boonedam.com>,yocto@lists.yoctoproject.org
Subject: Re: [yocto] fitImage generation issue #kirkstone #yocto
Date: Wed, 28 Feb 2024 22:56:19 -0800 [thread overview]
Message-ID: <23930.1709189779151110135@lists.yoctoproject.org> (raw)
In-Reply-To: <6qkK.1709043739115307641.VHLP@lists.yoctoproject.org>
On Tue, Feb 27, 2024 at 03:22 PM, Jeffrey Simons wrote:
>
> Hello Yocto friends,
>
> I have an issue with the generation of an fitImage with initramfs. The
> creation of an fitImage where a kernel and device tree are combined works,
> but when I add an initramfs then the kernel creation keeps adding the fitImage
> without the initramfs.
>
> What I see on the debug output is the following:
> --> FILES:kernel-image-fitimage="/boot/fitImage-5.4.129+g828ec42a6a32+p3
> /boot/fitImage"
>
> While I would expect something like:
> -->
> FILES:kernel-image-fitimage="/boot/fitImage-my-initramfs-name-5.4.129+g828ec42a6a32+p3
> /boot/fitImage"
I dove further down the rabbit hole and I think to know why this happens. the deb package creation happens
before the initramfs bundle/creation. Most likely this has its good reasons for that order (regarding dependencies)
but in our case this means that the deb file only contains a fitImage with a device tree. (Not good for us).
Perhaps this is a deb thingy and does this not happen with RPM or IPK, but I didn't dove into that due to the limited
time I had. So our solution for the time being will be to execute a rootfs post process command that copies the correct fitImage
into the boot folder which will end up in my ubi image.
Hopefully someone will find this information useful.
--
With kind regards,
Jeffrey Simons
Software Engineer
Royal Boon Edam International B.V.
prev parent reply other threads:[~2024-02-29 6:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 14:22 fitImage generation issue #kirkstone #yocto Jeffrey Simons
2024-02-29 6:56 ` Jeffrey Simons [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23930.1709189779151110135@lists.yoctoproject.org \
--to=jeffrey.simons@boonedam.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).