From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 03 Jan 2023 11:23:02 +0100 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pCeRi-000JKT-Re for lore@lore.pengutronix.de; Tue, 03 Jan 2023 11:23:02 +0100 Received: from localhost ([127.0.0.1] helo=metis.ext.pengutronix.de) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1pCeRh-0004tn-AE; Tue, 03 Jan 2023 11:23:01 +0100 Received: from drehscheibe.grey.stw.pengutronix.de ([2a0a:edc0:0:c01:1d::a2]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pCeRY-0004tX-Bo; Tue, 03 Jan 2023 11:22:52 +0100 Received: from [2a0a:edc0:0:900:1d::77] (helo=ptz.office.stw.pengutronix.de) by drehscheibe.grey.stw.pengutronix.de with esmtp (Exim 4.94.2) (envelope-from ) id 1pCeRX-003Xbe-LI; Tue, 03 Jan 2023 11:22:51 +0100 Received: from localhost ([127.0.0.1]) by ptz.office.stw.pengutronix.de with esmtp (Exim 4.94.2) (envelope-from ) id 1pCeRW-009u5k-UR; Tue, 03 Jan 2023 11:22:50 +0100 Message-ID: <835cc6c5954c4a8b9fa3a700375c4eb93271dc15.camel@pengutronix.de> From: Jan =?ISO-8859-1?Q?L=FCbbe?= To: Ahmad Fatoum , BAUER Bernd , "RAUC@pengutronix.de" Date: Tue, 03 Jan 2023 11:22:50 +0100 In-Reply-To: <12e2013627f500131915d70d502dc9ea44bf31e7.camel@pengutronix.de> References: <12e2013627f500131915d70d502dc9ea44bf31e7.camel@pengutronix.de> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.2 (by Flathub.org) MIME-Version: 1.0 Subject: Re: [RAUC] Non reduntant bootloader update X-BeenThere: rauc@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: RAUC Project - Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "RAUC" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: rauc-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false Hi again, On Tue, 2023-01-03 at 10:39 +0100, Jan L=C3=BCbbe wrote: > Hi, >=20 > On Tue, 2023-01-03 at 09:31 +0100, Ahmad Fatoum wrote: > > Hello Bernd, > >=20 > > On 03.01.23 09:17, BAUER Bernd wrote: > > > Hi! > > >=20 > > > 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. > >=20 > > Why would you not place it into the dedicated hardware boot partitions > > that your eMMC already has? > >=20 > > > Does this work with Rauc at all? > >=20 > > eMMC boot partition are better because they provide power-fail safe upd= ate, > > 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 nee= ds > > to be located in unpartitioned space. >=20 > Which SoC are you using? Ah, I just noticed that you're using a i.MX8MN. That means you can use the = eMMC boot partitions and have atomic bootloader updates with the current implementation in RAUC: https://rauc.readthedocs.io/en/latest/advanced.html#update-bootloader-in-em= mc-boot-partitions Regards, Jan > Depending on what the ROM code expects, you could use the other types (bo= ot-raw- > fallback or boot-mbr-switch). >=20 > If the ROM code only supports a single fixed bootloader offset, you canno= t > update it atomically. Support for that is not implemented in RAUC yet. >=20 > > > I have unfortunately found nothing in the manual about it. > >=20 > > There's: https://rauc.readthedocs.io/en/latest/examples.html#atomic-boo= tloader-updates-emmc >=20 > More details on the available methods are in: > https://rauc.readthedocs.io/en/latest/advanced.html#updating-the-bootload= er --=20 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 |