[PATCH] doc: board: toradex: colibri_vf: flash u-boot-nand.imx, not the plain image

[PATCH] doc: board: toradex: colibri_vf: flash u-boot-nand.imx, not the plain image

[Mehmet Fide]

From: Mehmet Fide <mehmet.fide@screeningeagle.com>

The BootROM reads the IVT at offset 0x400 of the NAND boot device
(VFxxx Reference Manual rev. 8, table 7-51), but the page tells the
reader to write the plain u-boot.imx, which carries the IVT at offset
0. The BootROM refuses such an image and silently falls back to the
serial downloader, verified on a Colibri VF50 V1.2A. Point the NAND
flashing section and the eBoot flashloader section at the
u-boot-nand.imx make target, which prefixes the image with the 1 KiB
of padding the BootROM expects; that is the file the eBoot flow was
verified with on a Colibri VF61 V1.2B.

Fixes: 26e89c626827 ("doc: board: toradex: add the Colibri VF50/VF61 page")
Signed-off-by: Mehmet Fide <mehmet.fide@screeningeagle.com>
---
 doc/board/toradex/colibri_vf.rst | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/doc/board/toradex/colibri_vf.rst b/doc/board/toradex/colibri_vf.rst
index f9c81d70214..a010f9f5a2d 100644
--- a/doc/board/toradex/colibri_vf.rst
+++ b/doc/board/toradex/colibri_vf.rst
@@ -25,8 +25,18 @@ Build U-Boot
     $ make colibri_vf_defconfig
     $ make
 
-This produces ``u-boot.imx``, the image with the IVT for the Vybrid
-BootROM, ready to be written to the ``u-boot`` NAND partition.
+This produces ``u-boot.imx``, the plain image with the IVT for the
+Vybrid BootROM. The BootROM expects the IVT at offset 0x400 of a NAND
+boot device (VFxxx Reference Manual rev. 8, table 7-51), so the image
+written to the ``u-boot`` NAND partition needs 1 KiB of padding in
+front of it:
+
+.. code-block:: console
+
+    $ make u-boot-nand.imx
+
+The plain ``u-boot.imx`` written to NAND is refused by the BootROM,
+which then silently falls back to the serial downloader.
 
 Flash to NAND from a running U-Boot
 -----------------------------------
@@ -36,7 +46,7 @@ Load the image over TFTP or from a FAT formatted SD card and use the
 
 .. code-block:: none
 
-    Colibri VFxx # fatload mmc 0:1 ${loadaddr} u-boot.imx
+    Colibri VFxx # fatload mmc 0:1 ${loadaddr} u-boot-nand.imx
     Colibri VFxx # run update_uboot
     Colibri VFxx # reset
 
@@ -62,5 +72,5 @@ offer a ``flashloader`` command that writes a U-Boot image to NAND:
 
 .. code-block:: none
 
-    > flashloader u-boot.imx
+    > flashloader u-boot-nand.imx
     > reboot
-- 
2.54.0

Re: [PATCH] doc: board: toradex: colibri_vf: flash u-boot-nand.imx, not the plain image

[Francesco Dolcini]

On Fri, Aug 28, 2026 at 01:23:35PM +0200, Mehmet Fide wrote:
> From: Mehmet Fide <mehmet.fide@screeningeagle.com>
> 
> The BootROM reads the IVT at offset 0x400 of the NAND boot device
> (VFxxx Reference Manual rev. 8, table 7-51), but the page tells the
> reader to write the plain u-boot.imx, which carries the IVT at offset
> 0. The BootROM refuses such an image and silently falls back to the
> serial downloader, verified on a Colibri VF50 V1.2A. Point the NAND
> flashing section and the eBoot flashloader section at the
> u-boot-nand.imx make target, which prefixes the image with the 1 KiB
> of padding the BootROM expects; that is the file the eBoot flow was
> verified with on a Colibri VF61 V1.2B.
> 
> Fixes: 26e89c626827 ("doc: board: toradex: add the Colibri VF50/VF61 page")
> Signed-off-by: Mehmet Fide <mehmet.fide@screeningeagle.com>

Acked-by: Francesco Dolcini <francesco.dolcini@toradex.com>