Re: [PATCH 1/2] colibri_vf: restore the pre-2017 text base, the BootROM refuses the low one

Francesco Dolcini <[email protected]>
Newsgroups org.u-boot-project.lists.u-boot
Message-ID <20260814071920.GB5246@francesco-nb>
On Thu, Aug 13, 2026 at 05:07:25PM +0200, Mehmet Fide wrote:
> From: Mehmet Fide <[email protected]>
> 
> Since commit c0f432c37780 ("configs: vf610: increase maximum size and
> enforce correct limit") U-Boot for the Vybrid boards links at 0x3f401000, right
> at the start of the OCRAM gfxRAM area. On a Colibri VF50 the BootROM
> does not start such an image from NAND at all: the module drops into
> the serial downloader, verified by the 0x23454523 UART association
> pattern echoing back. The WinCE-era Toradex loader dies the same way
> when handed such an image with its flashloader command. Relinking the
> same tree at 0x3f408000, the value used before that commit and by the
> vendor fork since, boots through both paths.
> 
> The low 28 KiB of the gfxRAM area are evidently not usable as a load
> address for the ROM, so give them back and correct the size limit to
> match (0x3f480000 - 0x3f408000).
> 
> Tested on a Colibri VF50 128MB IT V1.2B on an Iris carrier: cold boot
> from NAND, both text bases, one build apart.
> 
> Fixes: c0f432c37780 ("configs: vf610: increase maximum size and enforce correct limit")
> Signed-off-by: Mehmet Fide <[email protected]>

Stefan: do you remember any of this? any comment?

Unless Stefan says anything against this change, I am ok with it. But I
really have no idea about it, I trust your analysis Mehmet.

Acked-by: Francesco Dolcini <[email protected]>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.