回复: [PATCH v11 17/21] tools: imx8image: add i.MX95 support

[Alice Guo (OSS)]

> -----邮件原件-----
> 发件人: Enric Balletbo i Serra <eballetb at redhat.com>
> 发送时间: 2025年6月12日 22:18
> 收件人: Alice Guo (OSS) <alice.guo at oss.nxp.com>
> 抄送: Tom Rini <trini at konsulko.com>; Lukasz Majewski <lukma at denx.de>;
> Sean Anderson <seanga2 at gmail.com>; Jaehoon Chung
> <jh80.chung at samsung.com>; Simon Glass <sjg at chromium.org>; Stefano
> Babic <sbabic at denx.de>; Fabio Estevam <festevam at gmail.com>; Alper Nebi
> Yasak <alpernebiyasak at gmail.com>; Alice Guo <alice.guo at nxp.com>;
> u-boot at lists.denx.de; Lothar Waßmann <LW at karo-electronics.de>
> 主题: Re: [PATCH v11 17/21] tools: imx8image: add i.MX95 support
> 
> [You don't often get email from eballetb at redhat.com. Learn why this is
> important at https://aka.ms/LearnAboutSenderIdentification ]
> 
> Hi all,
> 
> On Mon, Apr 28, 2025 at 12:41 PM Alice Guo (OSS) <alice.guo at oss.nxp.com>
> wrote:
> >
> > From: Alice Guo <alice.guo at 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 at nxp.com>
> 
> I bisected a problem with the current mainline with the imx8qxp_mek board
> and seems to point to that patch. After this patch, I'm getting the following
> errors when u-boot creates the  flash.bin binary.
> 
>    error writing image hdr 400
>    MKIMAGE flash.bin
> 
> The resulting binary seems to not work. Reverting that patch helps to make
> bootable the board again.
> 
> The u-boot log is:
> ....
>   MKIMAGE u-boot.cnt
> 1+0 records in
> 1+0 records out
> 33792 bytes (34 kB, 33 KiB) copied, 6.5088e-05 s, 519 MB/s
> 64+1 records in
> 64+1 records out
> 32909 bytes (33 kB, 32 KiB) copied, 0.000142272 s, 231 MB/s
> 1+0 records in
> 1+0 records out
> 676864 bytes (677 kB, 661 KiB) copied, 0.000610144 s, 1.1 GB/s
> 1320+1 records in
> 1320+1 records out
> 676272 bytes (676 kB, 660 KiB) copied, 0.00326546 s, 207 MB/s
> build_container: 0 0
> error writing image hdr 400
>   MKIMAGE flash.bin
> 1+0 records in
> 1+0 records out
> 164864 bytes (165 kB, 161 KiB) copied, 0.00016016 s, 1.0 GB/s
> 321+1 records in
> 321+1 records out
> 164608 bytes (165 kB, 161 KiB) copied, 0.000612231 s, 269 MB/s
> 1+0 records in
> 1+0 records out
> 79872 bytes (80 kB, 78 KiB) copied, 7.304e-05 s, 1.1 GB/s
> 155+1 records in
> 155+1 records out
> 79799 bytes (80 kB, 78 KiB) copied, 0.000962302 s, 82.9 MB/s
> build_container: 400 0
> error writing image hdr 400
> append u-boot.cnt at 316 KB
> 702+0 records in
> 702+0 records out
> 718848 bytes (719 kB, 702 KiB) copied, 0.00186017 s, 386 MB/s
> 
> Best regards,
>   Enric

Hi Enric,

Thank you for pointing out this issue. This patch sets dcd_skip passed to build_container() to false. For i.MX8QXP, dcd_skip should be set to true. I will send a patch to fix this error later.

Best Regards,
Alice Guo