From: Mehmet Fide <[email protected]>
Hello Francesco,
On Wed, Aug 12, 2026 at 10:47:53AM +0200, Francesco Dolcini wrote:
> what if you powercycle the board, instead of doing a reboot?
Measured today, and it turned out not to be an eBoot problem at all. I
wrote the current-defconfig image (CONFIG_TEXT_BASE=0x3f401000) into
NAND from a running U-Boot and power cycled: the BootROM does not start
it either. The module drops into the serial downloader, verified by the
0x23454523 UART association pattern echoing back on the console UART.
Writing back an image linked at 0x3f408000 through the same procedure,
the module cold boots normally.
So the eBoot observation from my report was just another face of the
same thing: nothing starts an image linked at the bottom of the gfxRAM
area, the low 28 KiB are not usable as a load address. It has been this
way since commit c0f432c37780 ("configs: vf610: increase maximum size
and enforce correct limit") in 2017; the vendor fork never took that
change, which is presumably why it went unnoticed.
> I would not focus on whatever you are getting pre-programmed on the
> board, apart maybe some note in the documentation.
Agreed on the standalone flashing. I have sent a two patch series: the
first restores 0x3f408000 in colibri_vf_defconfig with the measurements
above, the second adds the missing doc/board/toradex page for the
Colibri VF50/VF61 with the build, flashing and recovery mode steps.
Thanks,
Mehmet
