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 0/5] allow boot firmware to go in user/boot0/boot1
Date: Tue, 2 May 2023 17:05:52 -0700 [thread overview]
Message-ID: <20230503000557.2275982-1-tharvey@gateworks.com> (raw)
The Gateworks Venice board family uses a combination of imx8mm, imx8mn,
and imx8mp SoC's. Because boot firmware for these are not binary
compatible and have different flash offsets it is highly desirable to
place boot firmware in an emmc boot partition instead of the current
user hardware partition to minimize unintended corruption of boot
firmware by flashing the wrong image or to the wrong location.
This series of patches allows the same boot firmware to be placed in
either boot0, boot1, or user hardware partition by detecting the boot
device and adjusting env device as well as u-boot sector.
Additionally the firmware script is updated to automate device, offset,
and soc.
Tim Harvey (5):
board: gateworks: venice: dynamically determine U-Boot raw sector
board: gateworks: venice: dynamically determine U-Boot env partition
board: gateworks: venice: dynamically update the update_firmware
script
board: gateworks: venice: move env location
board: gateworks: venice: update board doc to show other emmc parts
board/gateworks/venice/spl.c | 15 +++++
board/gateworks/venice/venice.c | 86 +++++++++++++++++++++++++++
board/gateworks/venice/venice.env | 6 +-
configs/imx8mm_venice_defconfig | 4 +-
configs/imx8mn_venice_defconfig | 4 +-
configs/imx8mp_venice_defconfig | 4 +-
doc/board/gateworks/imx8mm_venice.rst | 4 +-
doc/board/gateworks/imx8mn_venice.rst | 4 +-
doc/board/gateworks/imx8mp_venice.rst | 4 +-
include/configs/imx8mm_venice.h | 1 -
include/configs/imx8mn_venice.h | 1 -
include/configs/imx8mp_venice.h | 1 -
12 files changed, 119 insertions(+), 15 deletions(-)
--
2.25.1
next reply other threads:[~2023-05-03 0:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 0:05 Tim Harvey [this message]
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 ` [PATCH 5/5] board: gateworks: venice: update board doc to show other emmc parts Tim Harvey
2023-07-11 19:47 ` 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-1-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