From: Tim Harvey <tharvey@gateworks.com>
To: sbabic@denx.de, Fabio Estevam <festevam@denx.de>
Cc: u-boot@lists.denx.de, Tim Harvey <tharvey@gateworks.com>
Subject: [PATCH 5/5] board: gateworks: venice: update board doc to show other emmc parts
Date: Tue, 2 May 2023 17:05:57 -0700 [thread overview]
Message-ID: <20230503000557.2275982-6-tharvey@gateworks.com> (raw)
In-Reply-To: <20230503000557.2275982-1-tharvey@gateworks.com>
Update the venice board documentation to show how to install to the
various eMMC hardware partitions available as the same binary firmware
can be placed in either user/boot0/boot1 without build-time config
changes. Note that the boot offsets differ depending on the SoC and the
eMMC hardware partition.
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
---
doc/board/gateworks/imx8mm_venice.rst | 4 +++-
doc/board/gateworks/imx8mn_venice.rst | 4 +++-
doc/board/gateworks/imx8mp_venice.rst | 4 +++-
3 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/doc/board/gateworks/imx8mm_venice.rst b/doc/board/gateworks/imx8mm_venice.rst
index f1e7e4994458..ea78dfd7ae6b 100644
--- a/doc/board/gateworks/imx8mm_venice.rst
+++ b/doc/board/gateworks/imx8mm_venice.rst
@@ -47,4 +47,6 @@ Update eMMC
=> tftpboot $loadaddr flash.bin
=> setexpr blkcnt $filesize + 0x1ff && setexpr blkcnt $blkcnt / 0x200
- => mmc dev 2 && mmc write $loadaddr 0x42 $blkcnt
+ => mmc dev 2 0 && mmc write $loadaddr 0x42 $blkcnt # emmc user hw part
+ => mmc dev 2 1 && mmc write $loadaddr 0x42 $blkcnt # or emmc boot0 hw part
+ => mmc dev 2 2 && mmc write $loadaddr 0x42 $blkcnt # or emmc boot1 hw part
diff --git a/doc/board/gateworks/imx8mn_venice.rst b/doc/board/gateworks/imx8mn_venice.rst
index 7ba953a4a85c..7015f4ef31c7 100644
--- a/doc/board/gateworks/imx8mn_venice.rst
+++ b/doc/board/gateworks/imx8mn_venice.rst
@@ -47,4 +47,6 @@ Update eMMC
=> tftpboot $loadaddr flash.bin
=> setexpr blkcnt $filesize + 0x1ff && setexpr blkcnt $blkcnt / 0x200
- => mmc dev 2 && mmc write $loadaddr 0x40 $blkcnt
+ => mmc dev 2 0 && mmc write $loadaddr 0x40 $blkcnt # emmc user hw part
+ => mmc dev 2 1 && mmc write $loadaddr 0 $blkcnt # or emmc boot0 hw part
+ => mmc dev 2 2 && mmc write $loadaddr 0 $blkcnt # or emmc boot1 hw part
diff --git a/doc/board/gateworks/imx8mp_venice.rst b/doc/board/gateworks/imx8mp_venice.rst
index 632cd742d1f8..a219caadff26 100644
--- a/doc/board/gateworks/imx8mp_venice.rst
+++ b/doc/board/gateworks/imx8mp_venice.rst
@@ -47,4 +47,6 @@ Update eMMC
=> tftpboot $loadaddr flash.bin
=> setexpr blkcnt $filesize + 0x1ff && setexpr blkcnt $blkcnt / 0x200
- => mmc dev 2 && mmc write $loadaddr 0x40 $blkcnt
+ => mmc dev 2 0 && mmc write $loadaddr 0x40 $blkcnt # emmc user hw part
+ => mmc dev 2 1 && mmc write $loadaddr 0 $blkcnt # or emmc boot0 hw part
+ => mmc dev 2 2 && mmc write $loadaddr 0 $blkcnt # or emmc boot1 hw part
--
2.25.1
next prev parent reply other threads:[~2023-05-03 0:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 0:05 [PATCH 0/5] allow boot firmware to go in user/boot0/boot1 Tim Harvey
2023-05-03 0:05 ` [PATCH 1/5] board: gateworks: venice: dynamically determine U-Boot raw sector Tim Harvey
2023-07-11 19:42 ` sbabic
2023-05-03 0:05 ` [PATCH 2/5] board: gateworks: venice: dynamically determine U-Boot env partition Tim Harvey
2023-07-11 19:43 ` sbabic
2023-05-03 0:05 ` [PATCH 3/5] board: gateworks: venice: dynamically update the update_firmware script Tim Harvey
2023-07-11 19:46 ` sbabic
2023-05-03 0:05 ` [PATCH 4/5] board: gateworks: venice: move env location Tim Harvey
2023-07-11 19:46 ` sbabic
2023-05-03 0:05 ` Tim Harvey [this message]
2023-07-11 19:47 ` [PATCH 5/5] board: gateworks: venice: update board doc to show other emmc parts sbabic
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=20230503000557.2275982-6-tharvey@gateworks.com \
--to=tharvey@gateworks.com \
--cc=festevam@denx.de \
--cc=sbabic@denx.de \
--cc=u-boot@lists.denx.de \
/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