From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 21 Feb 2023 11:34:15 +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 1pUPyR-00DnQp-M1 for lore@lore.pengutronix.de; Tue, 21 Feb 2023 11:34:15 +0100 Received: from bombadil.infradead.org ([2607:7c80:54:3::133]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pUPyQ-0002Xm-5O for lore@pengutronix.de; Tue, 21 Feb 2023 11:34:15 +0100 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:From:In-Reply-To: Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=kiOCO1fiIesvx4MR7OWkLAYzmjqR9/Tt5oLdIYXzPxY=; b=HjU7+IJYPnmkJAvTatxNzDzHrX XhtPYZspyAp0XEHKTMAcKTp2HCx43wUQi8yweNg4e3vNp6WBOmM418g3NpHBHfL8FGFPBdGJ3nGdo fPH6HYXXbT1ORSe6aQHtybZ3+yV+GoLyIGcwPIlGAF+tr1uuq1zxPl4n4stU8yfpPMJVlw2xtzwxV /VqB342RT3YwLxirYwoDd7ByvOSDWexAJM6bIo8IW6fl7oBmTXU3mGb3/ViPAV//iQPwBV8g3WFu4 pKKBXNYqqERNYcHWF7HkrbwIW33pxRSWG7M19Hrk1W3RuexUUcJu2uXoFPv8FTgFgUlPaLdcvc5AU b3/3dBRw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1pUPx7-007Ofn-2g; Tue, 21 Feb 2023 10:32:53 +0000 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1pUPx2-007Of0-3i for barebox@lists.infradead.org; Tue, 21 Feb 2023 10:32:49 +0000 Received: from ptx.hi.pengutronix.de ([2001:67c:670:100:1d::c0]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pUPx0-0002Lp-AR; Tue, 21 Feb 2023 11:32:46 +0100 Received: from sha by ptx.hi.pengutronix.de with local (Exim 4.92) (envelope-from ) id 1pUPx0-0005IF-2t; Tue, 21 Feb 2023 11:32:46 +0100 Date: Tue, 21 Feb 2023 11:32:46 +0100 To: Ahmad Fatoum Cc: barebox@lists.infradead.org Message-ID: <20230221103246.GI10447@pengutronix.de> References: <20230217132140.2240388-1-a.fatoum@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230217132140.2240388-1-a.fatoum@pengutronix.de> X-Sent-From: Pengutronix Hildesheim X-URL: http://www.pengutronix.de/ X-Accept-Language: de,en X-Accept-Content-Type: text/plain User-Agent: Mutt/1.10.1 (2018-07-13) From: Sascha Hauer X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230221_023248_174687_87C60BAD X-CRM114-Status: GOOD ( 29.52 ) X-BeenThere: barebox@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "barebox" X-SA-Exim-Connect-IP: 2607:7c80:54:3::133 X-SA-Exim-Mail-From: barebox-bounces+lore=pengutronix.de@lists.infradead.org X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on metis.ext.pengutronix.de X-Spam-Level: X-Spam-Status: No, score=-4.7 required=4.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_NONE, URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.2 Subject: Re: [PATCH v2] Documentation: i.MX8M: add EVK barebox installation documentation X-SA-Exim-Version: 4.2.1 (built Wed, 08 May 2019 21:11:16 +0000) X-SA-Exim-Scanned: Yes (on metis.ext.pengutronix.de) On Fri, Feb 17, 2023 at 02:21:40PM +0100, Ahmad Fatoum wrote: > The barebox i.MX images have a preamble that pads the i.MX header to > the offset expected by the BootROM. This allows writing barebox images > directly to offset 0 on SD-Cards and eMMC user area. For some i.MX8M, > these images can't be directly written to eMMC boot partitions and > instead require special handling. Add a note about this to the > documentation. > > Signed-off-by: Ahmad Fatoum > --- > v1 -> v2: > - Fix typo, s/as an/at an/ (Ulrich) > - Fix typo, s/Power-fail installation/Power-fail-safe installation/ (Sascha) > --- > Documentation/boards/imx/nxp-imx8mm-evk.rst | 18 ++++++++++++++++ > Documentation/boards/imx/nxp-imx8mn-evk.rst | 24 +++++++++++++++++++++ > Documentation/boards/imx/nxp-imx8mp-evk.rst | 24 +++++++++++++++++++++ > 3 files changed, 66 insertions(+) Applied, thanks Sascha > > diff --git a/Documentation/boards/imx/nxp-imx8mm-evk.rst b/Documentation/boards/imx/nxp-imx8mm-evk.rst > index c3cd35ae38a2..f0dfc53ed070 100644 > --- a/Documentation/boards/imx/nxp-imx8mm-evk.rst > +++ b/Documentation/boards/imx/nxp-imx8mm-evk.rst > @@ -69,3 +69,21 @@ board for serial download mode as printed on the PCB. You can start barebox with > the imx-usb-loader tool that comes with barebox like this: > > ./scripts/imx/imx-usb-loader images/barebox-nxp-imx8mm-evk.img > + > +Installing barebox > +================== > + > +When the EVK is strapped to boot from eMMC, the i.MX8M bootrom will > +consult the eMMC ext_csd register to determine whether to boot > +from the active eMMC boot partition or from the user area. > + > +The same barebox image written to the start of the SD-Card can > +be written to the start of the eMMC user area. Power-fail-safe > +installation to the eMMC boot partition requires special handling: > + > + - The barebox image must be written to the inactive boot partition, > + then afterwards, the newly written boot partition is activated > + (This is controlled by the barebox ``mmcX.boot`` variable). > + > +The ``barebox_update`` command takes care of this and need just be > +supplied a barebox image as argument. > diff --git a/Documentation/boards/imx/nxp-imx8mn-evk.rst b/Documentation/boards/imx/nxp-imx8mn-evk.rst > index b920e22d33e9..177fc59c1085 100644 > --- a/Documentation/boards/imx/nxp-imx8mn-evk.rst > +++ b/Documentation/boards/imx/nxp-imx8mn-evk.rst > @@ -58,3 +58,27 @@ Build barebox > > make imx_v8_defconfig > make > + > +Installing barebox > +================== > + > +When the EVK is strapped to boot from eMMC, the i.MX8M bootrom will > +consult the eMMC ext_csd register to determine whether to boot > +from the active eMMC boot partition or from the user area. > + > +The same barebox image written to the start of the SD-Card can > +be written to the start of the eMMC user area. Power-fail-safe > +installation to the eMMC boot partition requires special handling: > + > + - The barebox image must be written to the inactive boot partition, > + then afterwards, the newly written boot partition is activated > + (This is controlled by the barebox ``mmcX.boot`` variable). > + > + - The barebox image includes a 32KiB preamble that allows the image > + to be directly writable to the start of the SD-Card or eMMC user area. > + Unlike older i.MX8M, the i.MX8MN BootROM expects the bootloader to not > + start at an offset when booting from eMMC boot partitions, thus the first > + 32KiB must be stripped. > + > +The ``barebox_update`` command takes care of this and need just be > +supplied a barebox image as argument. > diff --git a/Documentation/boards/imx/nxp-imx8mp-evk.rst b/Documentation/boards/imx/nxp-imx8mp-evk.rst > index 1074992f2f88..53cdd904ab0e 100644 > --- a/Documentation/boards/imx/nxp-imx8mp-evk.rst > +++ b/Documentation/boards/imx/nxp-imx8mp-evk.rst > @@ -66,3 +66,27 @@ Boot Configuration > The NXP i.MX8MP-EVK board has four switches responsible for configuring > bootsource/boot mode. The settings for the different boot sources are > printed on the board. > + > +Installing barebox > +================== > + > +When the EVK is strapped to boot from eMMC, the i.MX8M bootrom will > +consult the eMMC ext_csd register to determine whether to boot > +from the active eMMC boot partition or from the user area. > + > +The same barebox image written to the start of the SD-Card can > +be written to the start of the eMMC user area. Power-fail-safe > +installation to the eMMC boot partition requires special handling: > + > + - The barebox image must be written to the inactive boot partition, > + then afterwards, the newly written boot partition is activated > + (This is controlled by the barebox ``mmcX.boot`` variable). > + > + - The barebox image includes a 32KiB preamble that allows the image > + to be directly writable to the start of the SD-Card or eMMC user area. > + Unlike older i.MX8M, the i.MX8MP BootROM expects the bootloader to not > + start at an offset when booting from eMMC boot partitions, thus the first > + 32KiB must be stripped. > + > +The ``barebox_update`` command takes care of this and need just be > +supplied a barebox image as argument. > -- > 2.30.2 > > > -- 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 |