[PATCH 1/4] arm64: dts: imx8mn: Fix FSPI booting
Adam Ford
aford173 at gmail.com
Sun Nov 10 14:15:07 CET 2024
On Sat, Nov 9, 2024 at 7:34 PM Marek Vasut <marex at denx.de> wrote:
>
> On 11/9/24 9:06 PM, Adam Ford wrote:
> > When FSPI_CONF_HEADER is set, the binary needs to be built such
> > that there is a configuration file located at 0x400 and the start
> > of the file that would normally be flash.bin starts at 0x1000.
> > This used to be done properly until the device tree was converted to
> > nxp_imx8mimage.
> >
> > Building these with the offsets built into the binman device tree
> > changes impacts how the actual image is built and the locations
> > of the various blobs aren't fetched properly and booting fails.
> >
> > Fix this by building a standard image as if it were to boot from
> > eMMC or SD, then use that image as the input for a second image
>
> This seems like a workaround for some broken offset calculation in binman ?
This used to work until it was migrated to nxp_imx8mimage.
The blobs appear to be at the proper offsets, but the contents of
what's stored at those offsets are not the same.
If you're going to claim there is a bug somewhere, I would argue that
it's somewhere i nxp_imx8mimage. However, if you look at this series,
the added benefit is the ability for Nano to be able to build both a
SD/eMMC image and FSPI images with one config which allows for the
elimination of extra defconfig files. I am guessing Plus would have a
similar benefit since they have similar bootloaders.
adam
More information about the U-Boot
mailing list