[PATCH 3/5] x86: edison: Align U-Boot via binman to fix the boot
Andy Shevchenko
andriy.shevchenko at linux.intel.com
Mon Jun 8 10:29:15 CEST 2026
On Sun, Jun 07, 2026 at 05:47:26PM -0600, Tom Rini wrote:
> On Sun, Jun 07, 2026 at 05:05:12PM -0600, Simon Glass wrote:
>
> > The mask ROM loads the OS image to 0x01100000 but enters it at
> > 0x01101000, so U-Boot must sit 0x1000 (4KB) into the loaded image. This
> > was arranged by board/intel/edison/config.mk, which prepended 4096 zero
> > bytes to u-boot.bin through an 'INPUTS-y += u-boot-align.bin' rule whose
> > recipe moved its output back over u-boot.bin.
> >
> > Commit bd3f9ee679b4 ("kbuild: Bump the build system to 6.1") stopped
> > that rule from running, so u-boot.bin no longer gains the 4KB prefix.
> > The mask ROM then jumps 4KB into U-Boot's code and the board never
> > starts, sitting in BootROM download mode (DnX) and cycling.
> >
> > Since the Edison image is assembled by binman, provide the gap there
> > instead: pad with a 'fill' of 4096 zero bytes ahead of the u-boot entry.
> > Drop the now-redundant alignment hack from the board config.mk.
> >
> > Fixes: bd3f9ee679b4 ("kbuild: Bump the build system to 6.1")
> > Signed-off-by: Simon Glass <sjg at chromium.org>
>
> That's an unintentional behavior change we should understand why
> happened, and then do whatever needs to be done to fix it, so that other
> platforms that might have been in a similar spot can also be fixed.
While I agree on this, the Intel Edison case gets rectified by this series in
terms of getting rid of the known hack as Simon mentioned. Yes, it was me who
invented that hack long time ago for quicker ramping up the board.
--
With Best Regards,
Andy Shevchenko
More information about the U-Boot
mailing list