Hi Tom, On Mon, 8 Jun 2026 at 08:01, Tom Rini <[email protected]> wrote: > > On Mon, Jun 08, 2026 at 11:29:15AM +0300, Andy Shevchenko wrote: > > 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 <[email protected]> > > > > > > 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. > > That's good to know, thanks. As I agree that this is a better long-term > solution, but for the upcoming release the right answer is to fix the > direct regression (and so potentially other platforms, depending on root > cause).
It has been broken for a few releases, so I don't think we have to panic to get this into -master I believe this series cannot affect other boards, but we are very late for fixes. I spend some time looking around and found MXS has the same problem. So I'll send a new little series for both, then rebase this series on -next Regards, Simon > > -- > Tom
