From: Ye Li <ye.li@nxp.com>
To: "marex@denx.de" <marex@denx.de>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Cc: Peng Fan <peng.fan@nxp.com>,
"festevam@denx.de" <festevam@denx.de>,
"sbabic@denx.de" <sbabic@denx.de>
Subject: Re: [EXT] [PATCH] ARM: imx: romapi: Repair FlexSPI NOR boot offset
Date: Tue, 29 Mar 2022 02:49:28 +0000 [thread overview]
Message-ID: <1648521609.123397.54.camel@nxp.com> (raw)
In-Reply-To: <65ea21e4-fc25-e33b-6196-ed133ff3211c@denx.de>
On Mon, 2022-03-28 at 16:54 +0200, Marek Vasut wrote:
> Caution: EXT Email
>
> On 3/28/22 08:54, Ye Li wrote:
> >
> > Hi Marek,
> Hi,
>
> [...]
>
> >
> > >
> > > >
> > > > 2. Update the u-boot.itb offset in imx8mp-u-boot.dtsi, set the
> > > > offset
> > > > to 0x5f000. The previous offset 0x58000 is for SD, calculated
> > > > by
> > > > 0x60000 - 0x8000 (32KB image offset).
> > > >
> > > > uboot: blob-ext@2 {
> > > > filename = "u-boot.itb";
> > > > offset = <0x5f000>;
> > > > };
> > > But that breaks booting from SD card for me ?
> > Do you want to use one flash.bin for both SD and flexspi?
> Yes, the board I use can boot from SD/eMMC/FlexSPI. I don't want to
> build multiple confusing "flash.bin" files, one for each boot media.
>
> >
> > When first introduced 8m support by imx8mimage.c, we expected the
> > u-
> > boot.itb at same device offset (0x60000) on SD/emmc and flexspi.
> > The
> > imx8mimage will calculate the offset inside the flash.bin
> > automatically
> > according to different IVT offset. The ROMAPI driver also works
> > correspondingly.
> > After using binman, the u-boot.itb offset inside the flash.bin has
> > to
> > be manually set in this DTS node. To follow the original design,
> > this
> > offset should be different. That's why I asked to update this dts
> > node
> > for flexspi.
> This does imply that there are currently no users that boot from
> flexspi
> in upstream U-Boot, because such users would have to manually modify
> both arch/arm/dts/imx8m?-u-boot.dtsi and board/*/imximage.cfg to
> generate suitable flash.bin which can be started from FlexSPI.
>
> Also, git grep confirms that there are no users:
>
> u-boot$ git grep BOOT_FROM.*fspi
> doc/imx/mkimage/imx8image.txt:BOOT_FROM
> [sd|emmc_fastboot|fspi|nand_4k|nand_8k|nand_16k] [sector_size]
>
> >
> > If you change the ROM API driver, that will break our design. You
> > can
> > try to overwrite spl_romapi_get_uboot_base for your board only.
> Since there are no users which boot from flexspi upstream, this
> design
> can still be fixed such that it does not require different flash.bin
> for
> different boot media, but rather one flash.bin works on all boot
> media.
> I think that is much better.
Your flash.bin can work on flexspi because you manually program the
flexspi configurations header. But once you want to upgrade the
flash.bin, flexspi configurations will also be erased due to the block
size. Then you have to reprogram the configurations with flash.bin.
So most of our customers add the flexspi configurations to flash.bin
head. They don't use so called one image for both SD and flexspi.
As the spl_romapi_get_uboot_base is defined to weak. It is better to
overwrite this function for your particular usage.
Best regards,
Ye Li
>
> [...]
next prev parent reply other threads:[~2022-03-29 2:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 16:09 [PATCH] ARM: imx: romapi: Repair FlexSPI NOR boot offset Marek Vasut
2022-03-21 3:35 ` [EXT] " Ye Li
2022-03-21 14:59 ` Marek Vasut
2022-03-23 2:42 ` Ye Li
2022-03-23 21:16 ` Marek Vasut
2022-03-28 6:54 ` Ye Li
2022-03-28 14:54 ` Marek Vasut
2022-03-29 2:49 ` Ye Li [this message]
2022-03-29 9:01 ` Marek Vasut
2022-03-29 9:56 ` Ye Li
2022-03-30 22:27 ` Marek Vasut
2022-03-30 22:36 ` Fabio Estevam
2022-03-31 4:45 ` Ye Li
2022-03-31 15:09 ` Tim Harvey
2022-03-31 15:26 ` Marek Vasut
2022-03-31 16:03 ` Tim Harvey
2022-03-31 16:41 ` Marek Vasut
2022-03-31 18:02 ` Tim Harvey
2022-03-31 18:04 ` Marek Vasut
2022-04-12 21:40 ` 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=1648521609.123397.54.camel@nxp.com \
--to=ye.li@nxp.com \
--cc=festevam@denx.de \
--cc=marex@denx.de \
--cc=peng.fan@nxp.com \
--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