From: "Jan Lübbe" <jlu@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>,
BAUER Bernd <bernd.bauer@ses-imagotag.com>,
"RAUC@pengutronix.de" <RAUC@pengutronix.de>
Subject: Re: [RAUC] Non reduntant bootloader update
Date: Tue, 03 Jan 2023 10:39:31 +0100 [thread overview]
Message-ID: <12e2013627f500131915d70d502dc9ea44bf31e7.camel@pengutronix.de> (raw)
In-Reply-To: <caa2c406-356a-372d-4f55-982652ddbb91@pengutronix.de>
Hi,
On Tue, 2023-01-03 at 09:31 +0100, Ahmad Fatoum wrote:
> Hello Bernd,
>
> On 03.01.23 09:17, BAUER Bernd wrote:
> > Hi!
> >
> > I have an IMX8MN system and want to use RAUC to update the bootloader.
> > The BL is on the EMMC (no partition) and is not redundant.
>
> Why would you not place it into the dedicated hardware boot partitions
> that your eMMC already has?
>
> > Does this work with Rauc at all?
>
> eMMC boot partition are better because they provide power-fail safe update,
> but you could use the eMMC user area with RAUC as well.
> Easiest way is to just place a MBR/GPT partition at the location where the
> bootrom expects the bootloader. There's no rule that the bootloader needs
> to be located in unpartitioned space.
Which SoC are you using?
Depending on what the ROM code expects, you could use the other types (boot-raw-
fallback or boot-mbr-switch).
If the ROM code only supports a single fixed bootloader offset, you cannot
update it atomically. Support for that is not implemented in RAUC yet.
> > I have unfortunately found nothing in the manual about it.
>
> There's: https://rauc.readthedocs.io/en/latest/examples.html#atomic-bootloader-updates-emmc
More details on the available methods are in:
https://rauc.readthedocs.io/en/latest/advanced.html#updating-the-bootloader
Regards,
Jan
--
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 |
next prev parent reply other threads:[~2023-01-03 9:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 8:17 BAUER Bernd
2023-01-03 8:31 ` Ahmad Fatoum
2023-01-03 9:39 ` Jan Lübbe [this message]
2023-01-03 10:22 ` Jan Lübbe
2023-01-03 14:22 ` BAUER Bernd
2023-01-04 10:14 ` BAUER Bernd
2023-01-04 10:18 ` Ahmad Fatoum
2023-01-04 10:23 ` BAUER Bernd
2023-01-04 10:36 ` Peter Korsgaard
2023-01-04 10:40 ` Ahmad Fatoum
2023-01-04 11:08 ` Peter Korsgaard
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=12e2013627f500131915d70d502dc9ea44bf31e7.camel@pengutronix.de \
--to=jlu@pengutronix.de \
--cc=RAUC@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=bernd.bauer@ses-imagotag.com \
/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