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")
Acked-by: Francesco Dolcini <[email protected]>
Signed-off-by: Mehmet Fide <[email protected]>
---
configs/colibri_vf_defconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/configs/colibri_vf_defconfig b/configs/colibri_vf_defconfig
index 5145e947e88..beb64189d5c 100644
--- a/configs/colibri_vf_defconfig
+++ b/configs/colibri_vf_defconfig
@@ -2,7 +2,7 @@ CONFIG_ARM=y
CONFIG_SKIP_LOWLEVEL_INIT=y
CONFIG_SYS_THUMB_BUILD=y
CONFIG_ARCH_VF610=y
-CONFIG_TEXT_BASE=0x3f401000
+CONFIG_TEXT_BASE=0x3f408000
CONFIG_SYS_MALLOC_LEN=0x0220000
CONFIG_NR_DRAM_BANKS=1
CONFIG_ENV_SIZE=0x20000
@@ -16,7 +16,7 @@ CONFIG_SYS_MEMTEST_START=0x80010000
CONFIG_SYS_MEMTEST_END=0x87c00000
CONFIG_ENV_VARS_UBOOT_CONFIG=y
CONFIG_HAS_BOARD_SIZE_LIMIT=y
-CONFIG_BOARD_SIZE_LIMIT=520192
+CONFIG_BOARD_SIZE_LIMIT=491520
# CONFIG_EFI_LOADER is not set
CONFIG_BOOTDELAY=1
CONFIG_FDT_FIXUP_PARTITIONS=y
--
2.54.0
