From: Rudolf J Streif <rudolf.streif@ibeeto.com>
To: yocto@lists.yoctoproject.org, lorenzo.arena@powersoft.com
Subject: Re: [yocto] Bundling an image artifacts into another image
Date: Mon, 4 Mar 2024 07:42:18 -0800 [thread overview]
Message-ID: <f71d1245-7db7-4e22-bd3a-d31006d7f054@ibeeto.com> (raw)
In-Reply-To: <sH98.1709546292003941347.n1Jf@lists.yoctoproject.org>
On 3/4/24 01:58, lorenzo.arena via lists.yoctoproject.org wrote:
> I'm currently trying to set up a production system for a board based
> on the Raspberry Pi CM4. I'd like to be able to build a kernel with
> bundled initramfs which allows me to flash the on-board eMMC; such
> "flasher" image however should include the artifacts of another image
> (which would be the "real" image, so the output wic and bmap files).
> Is there a way to do this? I can build this two things separately but
> I'd like a single build step which allows me to get the full "flasher"
> image
Yes, that is possible. I have done it many times. Create any scripts,
systemd service files etc. you need to automatically install the image
to the eMMC with recipe, create a recipe to install your previously
build system image, create a minimal root file system to contain the
necessary artifacts.
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#62660): https://lists.yoctoproject.org/g/yocto/message/62660
> Mute This Topic: https://lists.yoctoproject.org/mt/104719133/3617932
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [rudolf.streif@ibeeto.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
Rudolf J Streif
CEO/CTO
1.855.442.3386
prev parent reply other threads:[~2024-03-04 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 9:58 Bundling an image artifacts into another image lorenzo.arena
2024-03-04 15:42 ` Rudolf J Streif [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=f71d1245-7db7-4e22-bd3a-d31006d7f054@ibeeto.com \
--to=rudolf.streif@ibeeto.com \
--cc=lorenzo.arena@powersoft.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).