From: "Lothar Waßmann" <LW@KARO-electronics.de>
To: "Alice Guo (OSS)" <alice.guo@oss.nxp.com>
Cc: Tom Rini <trini@konsulko.com>, Lukasz Majewski <lukma@denx.de>,
Sean Anderson <seanga2@gmail.com>, Simon Glass <sjg@chromium.org>,
Stefano Babic <sbabic@denx.de>,
Fabio Estevam <festevam@gmail.com>,
"NXP i.MX U-Boot Team" <uboot-imx@nxp.com>,
Alper Nebi Yasak <alpernebiyasak@gmail.com>,
Alice Guo <alice.guo@nxp.com>,
marex@denx.de, u-boot@lists.denx.de
Subject: Re: [PATCH v7 15/19] tools: imx8image: add i.MX95 support
Date: Thu, 6 Mar 2025 06:51:02 +0100 [thread overview]
Message-ID: <20250306065102.4b76491e@karo-electronics.de> (raw)
In-Reply-To: <20250305-imx95-v1-15-286d15acbb8a@oss.nxp.com>
Hi,
On Wed, 05 Mar 2025 21:28:27 +0800 Alice Guo (OSS) wrote:
> From: Alice Guo <alice.guo@nxp.com>
>
> i.MX95 uses binman to invoke mkimage to create image container. 2 image
> containers are needed currently. The first one is composed of
> ahab-container.img, LPDDR firmware images, OEI images, System Manager
> image and u-boot-spl.bin. The second one is consisted of ARM Trusted
> firmware and u-boot.bin.
>
> Because DDR OEI image and LPDDR firmware images have to be packaged
> together and named as m33-oei-ddrfw.bin by binman, so imx9_image.sh does
> not check if m33-oei-ddrfw.bin exists.
>
> When using "make imx95_19x19_evk_defconfig; make", imx9_image.sh will
> delete the line for u-boot.bin in container.cfg. In fact, binman is
> always called after the u-boot.bin is built, so imx9_image.sh does not
> check if u-boot.bin exists.
>
> Signed-off-by: Alice Guo <alice.guo@nxp.com>
> ---
> include/imx8image.h | 19 +++++--
> tools/imx8image.c | 143 +++++++++++++++++++++++++++++++++++++++++++++++-----
> tools/imx9_image.sh | 8 +++
> 3 files changed, 153 insertions(+), 17 deletions(-)
>
> diff --git a/include/imx8image.h b/include/imx8image.h
> index 6b95e93fb5..b48e2b0396 100644
> --- a/include/imx8image.h
> +++ b/include/imx8image.h
> @@ -157,7 +157,9 @@ enum imx8image_cmd {
> CMD_SOC_TYPE,
> CMD_CONTAINER,
> CMD_IMAGE,
> - CMD_DATA
> + CMD_DATA,
> + CMD_DUMMY_V2X,
> + CMD_HOLD
add comma to facilitate extending the enum...
> enum imx8image_core_type {
> @@ -169,7 +171,9 @@ enum imx8image_core_type {
> CFG_A35,
> CFG_A55,
> CFG_A53,
> - CFG_A72
> + CFG_A72,
> + CFG_M33,
> + CFG_OEI
dto.
>
> enum imx8image_fld_types {
> @@ -208,7 +212,10 @@ typedef enum option_type {
> FILEOFF,
> MSG_BLOCK,
> SENTINEL,
> - UPOWER
> + UPOWER,
> + OEI,
> + DUMMY_V2X,
> + HOLD
dto.
[...]
> diff --git a/tools/imx8image.c b/tools/imx8image.c
> index 0135b19095..94b1efacd1 100644
> --- a/tools/imx8image.c
> +++ b/tools/imx8image.c
> @@ -7,6 +7,7 @@
>
> #include "imx8image.h"
> #include <image.h>
> +#include <linux/sizes.h>
>
> static int p_idx;
> static int sector_size;
> @@ -54,6 +55,8 @@ static table_entry_t imx8image_cmds[] = {
> {CMD_CONTAINER, "CONTAINER", "new container", },
> {CMD_IMAGE, "IMAGE", "new image", },
> {CMD_DATA, "DATA", "new data", },
> + {CMD_DUMMY_V2X, "DUMMY_V2X", "v2x", },
> + {CMD_HOLD, "HOLD", "hold", },
> {-1, "", "", },
> };
>
the list terminator entry should not have a comment at the end, since
it MUST ALWAYS be the last entry.
Without comma adding an entry after the terminator (e.g. when resolving
a merge conflict) will lead to a compile error.
Otherwise adding an entry after the terminator would go unnoticed.
> @@ -66,6 +69,8 @@ static table_entry_t imx8image_core_entries[] = {
> {CFG_A55, "A55", "A55 core", },
> {CFG_A53, "A53", "A53 core", },
> {CFG_A72, "A72", "A72 core", },
> + {CFG_OEI, "OEI", "OEI", },
> + {CFG_M33, "M33", "M33 core", },
> {-1, "", "", },
> };
>
dto.
Lothar Waßmann
next prev parent reply other threads:[~2025-03-06 5:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 13:28 [PATCH v7 00/19] imx: add i.MX95 support Alice Guo (OSS)
2025-03-05 13:28 ` [PATCH v7 01/19] firmware: scmi: smt: Interrupt communication enable Alice Guo (OSS)
2025-03-05 13:28 ` [PATCH v7 02/19] pinctrl: nxp: add a pin controller driver based on SCMI pin control protocol Alice Guo (OSS)
2025-03-05 13:28 ` [PATCH v7 03/19] firmware: scmi_agent: add SCMI pin control protocol support Alice Guo (OSS)
2025-03-05 13:28 ` [PATCH v7 04/19] scmi_protocols: add SCMI misc protocol protocol_id and message_id for getting the ROM passover data Alice Guo (OSS)
2025-03-05 13:28 ` [PATCH v7 05/19] scmi_protocols: add SCMI Performance domain management protocol message IDs Alice Guo (OSS)
2025-03-05 13:28 ` [PATCH v7 06/19] clk: scmi: add the command CLOCK_PARENT_SET Alice Guo (OSS)
2025-03-06 5:09 ` Lothar Waßmann
2025-03-05 13:28 ` [PATCH v7 07/19] clk: scmi: check the clock state/parent/rate control permissions Alice Guo (OSS)
2025-03-06 5:11 ` Lothar Waßmann
2025-03-05 13:28 ` [PATCH v7 08/19] sandbox: add SCMI clock control permissions to sandbox Alice Guo
2025-03-05 13:28 ` [PATCH v7 09/19] scmi_protocols: update struct scmi_base_discover_list_protocols_out Alice Guo (OSS)
2025-03-05 13:28 ` [PATCH v7 10/19] imx9: scmi: add i.MX95 SoC and clock related code Alice Guo (OSS)
2025-03-06 5:41 ` Lothar Waßmann
2025-03-21 7:17 ` 回复: " Alice Guo (OSS)
2025-03-22 0:34 ` Marek Vasut
2025-03-05 13:28 ` [PATCH v7 11/19] spl: imx: use trampoline buffer to load images to secure region Alice Guo (OSS)
2025-03-05 13:28 ` [PATCH v7 12/19] imx9: add i.MX95 Kconfig and Makefile Alice Guo (OSS)
2025-03-05 13:28 ` [PATCH v7 13/19] imx: Kconfig: IMX8_ROMAPI is not configured for i.MX95 Alice Guo (OSS)
2025-03-05 13:28 ` [PATCH v7 14/19] binman: add a new entry type for packing DDR PHY firmware images Alice Guo (OSS)
2025-03-05 13:28 ` [PATCH v7 15/19] tools: imx8image: add i.MX95 support Alice Guo (OSS)
2025-03-06 5:51 ` Lothar Waßmann [this message]
2025-03-05 13:28 ` [PATCH v7 16/19] imx: add V2X container support on i.MX95 Alice Guo (OSS)
2025-03-05 13:28 ` [PATCH v7 17/19] doc: imx: add document for i.MX95 Image Container Format Alice Guo (OSS)
2025-03-05 13:28 ` [PATCH v7 18/19] imx95_evk: add i.MX95 19x19 EVK board basic support Alice Guo (OSS)
2025-03-06 5:58 ` Lothar Waßmann
2025-03-05 13:28 ` [PATCH v7 19/19] Makefile: add some files to CLEAN_FILES Alice Guo
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=20250306065102.4b76491e@karo-electronics.de \
--to=lw@karo-electronics.de \
--cc=alice.guo@nxp.com \
--cc=alice.guo@oss.nxp.com \
--cc=alpernebiyasak@gmail.com \
--cc=festevam@gmail.com \
--cc=lukma@denx.de \
--cc=marex@denx.de \
--cc=sbabic@denx.de \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.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