From: "Jan Lübbe via RAUC" <rauc@pengutronix.de>
To: "大原 匠汰" <shota.ohara@nds-osk.co.jp>,
"rauc@pengutronix.de" <rauc@pengutronix.de>
Subject: Re: [RAUC] Inquiry About Initializing Both Slots with RAUC Without Reboot
Date: Mon, 17 Nov 2025 17:03:19 +0100 [thread overview]
Message-ID: <03a16f67487f0895a5e9a57d5786bf302fa5cfaa.camel@pengutronix.de> (raw)
In-Reply-To: <OS7PR01MB147471EF9E888386BBF570DD2F5C9A@OS7PR01MB14747.jpnprd01.prod.outlook.com>
Hi Ohara,
On Mon, 2025-11-17 at 02:52 +0000, 大原 匠汰 via RAUC wrote:
> Dear RAUC Development Team,
> I am currently working on a product that uses RAUC and involves a dual-slot
> (A/B) update setup.
> During factory initialization, we would like to write an image to both slots
> without rebooting between operations.
Please note that in general factory bring-up is considered out-of-scope for
RAUC:https://rauc.readthedocs.io/en/latest/index.html#and-what-not:~:text=And%20finally%2C%20factory%20bring%20up%20of%20your%20device
> The system uses an eMMC with two slots for RAUC as follows:
> * /dev/mmcblk0p1 → slot.A (on eMMC)
> * /dev/mmcblk0p2 → slot.B (on eMMC)
> During the factory process, we Boot from an SD card that contains a separate
> partition for initialization:
> * /dev/mmcblk1p1 → Factory initialization partition (on SD card)
> Currently, even when booting from the SD card, one of the eMMC slots (A or B)
> is still recognized as the active slot by RAUC.
That should not happen, but don't know enough details about your setup to
recommend anything specific. Please check:
https://rauc.readthedocs.io/en/latest/integration.html#booted-slot-detection
(specially the section on 'rauc.external')
> As a result, the factory image is only written to the inactive slot.
> Is there a way to configure RAUC to explicitly write to both slots (A and B)
> during the factory initialization process, without requiring a reboot between
> slot updates?
When you've told RAUC that none of your slots is active, you'll probably need
https://github.com/rauc/rauc/pull/1525 as well. This is part of the v1.15
release.
Regards,
Jan
> Thank you very much in advance for your support.
> Best regards,
> Ohara
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2025-11-17 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OS7PR01MB147471EF9E888386BBF570DD2F5C9A@OS7PR01MB14747.jpnprd01.prod.outlook.com>
2025-11-17 6:46 ` Robert Schwebel via RAUC
2025-11-17 16:03 ` Jan Lübbe via RAUC [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=03a16f67487f0895a5e9a57d5786bf302fa5cfaa.camel@pengutronix.de \
--to=rauc@pengutronix.de \
--cc=jlu@pengutronix.de \
--cc=shota.ohara@nds-osk.co.jp \
/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