From: Rasmus Villemoes <ravi@prevas.dk>
To: Heiko Schocher <hs@denx.de>
Cc: Peng Fan <peng.fan@nxp.com>,
U-Boot Mailing List <u-boot@lists.denx.de>,
Fabio Estevam <festevam@denx.de>,
Fabio Estevam <festevam@gmail.com>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Marek Vasut <marex@denx.de>, dl-uboot-imx <uboot-imx@nxp.com>,
Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
Stefano Babic <sbabic@denx.de>,
"tharvey@gateworks.com" <tharvey@gateworks.com>,
Tom Rini <trini@konsulko.com>
Subject: Re: [RFC PATCH v1] dts: imx8mp-u-boot.dtsi align flash.bin
Date: Mon, 14 Oct 2024 12:21:42 +0200 [thread overview]
Message-ID: <87a5f7assp.fsf@prevas.dk> (raw)
In-Reply-To: <aeec07bf-6a3d-08c5-2786-5a7c2bfe92b6@denx.de> (Heiko Schocher's message of "Mon, 14 Oct 2024 09:44:45 +0200")
On man, okt 14 2024, Heiko Schocher <hs@denx.de> wrote:
>
> Board boots fine from emmc, sd card. Booting blank board with
> uuu works with posted RFC patch, as it seems to me code in
>
> spl_romapi_load_image_stream()
>
> waits for more bytes than flash.bin currently has... appending some
> zero bytes at the end, and U_Boot begins to boot and works fine, uuu
> tool ends with errorcode 0.
Sounds like exactly the symptoms I fixed with commit 89f19f45d650.
So yes, you really do need to ensure that flash.bin (or rather the
embedded u-boot FIT image) has a large enough size for what the rom api
expects, and that number changes when HAB is enabled.
Rasmus
next prev parent reply other threads:[~2024-10-14 10:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 8:28 [RFC PATCH v1] dts: imx8mp-u-boot.dtsi align flash.bin Heiko Schocher
2024-10-12 21:24 ` Marek Vasut
2024-10-14 5:49 ` Heiko Schocher
2024-10-13 12:42 ` Francesco Dolcini
2024-10-14 6:09 ` Heiko Schocher
2024-10-14 6:29 ` Peng Fan
2024-10-14 6:45 ` Heiko Schocher
2024-10-14 7:29 ` Peng Fan
2024-10-14 7:44 ` Heiko Schocher
2024-10-14 10:21 ` Rasmus Villemoes [this message]
2024-10-14 10:31 ` Marek Vasut
2024-10-14 11:00 ` Heiko Schocher
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=87a5f7assp.fsf@prevas.dk \
--to=ravi@prevas.dk \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=hs@denx.de \
--cc=marcel.ziswiler@toradex.com \
--cc=marex@denx.de \
--cc=peng.fan@nxp.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=sbabic@denx.de \
--cc=tharvey@gateworks.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.