U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Simon Glass <sjg@chromium.org>
Cc: u-boot@lists.denx.de, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH v2 5/5] doc: edison: Rewrite the update instructions
Date: Wed, 17 Jun 2026 08:41:30 +0200	[thread overview]
Message-ID: <ajJBmmhl1Gk9n4GP@black.igk.intel.com> (raw)
In-Reply-To: <20260616142444.48193-6-sjg@chromium.org>

On Tue, Jun 16, 2026 at 08:24:20AM -0600, Simon Glass wrote:
> Split the two ways of getting U-Boot onto the board: a plain DFU
> transfer into u-boot0 when a working U-Boot is already present, and the
> xFSTK mask ROM recovery when it is not. Drop the steps that only applied
> to replacing the original 2014 U-Boot, document the 4KB alignment gap
> the mask ROM needs and which binman output to flash (rather than the
> bare u-boot.bin), note that a bricked board enters DnX without any
> straps, and add udev rules for running the tools without sudo.

...

> -1. Prepare u-boot.bin as described in chapter above. You still need one
> -   more step (if and only if you have original U-Boot), i.e. run the
> -   following command::
>  
> -     $ truncate -s %4096 u-boot.bin

Still missing this important detail. The DFU on v2014.04 is broken in a way
that it requires also the whole binary to be aligned by 4k. The above pads
the tail to full 4k (last block).

Btw, now I realised that I haven't checked if this is inherited in your binman
case. Note, I haven't put that into the Makefile hack as I expected users to
do this once, but perhaps if somebody wants to start over (by flashing the last
official image), the file size needs to be aligned.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-06-17  6:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16 14:24 [PATCH v2 0/5] edison: Convert the image build to binman Simon Glass
2026-06-16 14:24 ` [PATCH v2 1/5] binman: Add an entry type for the Intel OSIP header Simon Glass
2026-06-17  6:31   ` Andy Shevchenko
2026-06-17  6:42     ` Andy Shevchenko
2026-06-16 14:24 ` [PATCH v2 2/5] edison: Widen the DFU auto-probe window for flashing U-Boot Simon Glass
2026-06-16 14:24 ` [PATCH v2 3/5] x86: edison: Move U-Boot alignment into binman Simon Glass
2026-06-16 14:24 ` [PATCH v2 4/5] CI: Add an sjg-lab job for the Intel Edison Simon Glass
2026-06-17  6:34   ` Andy Shevchenko
2026-06-16 14:24 ` [PATCH v2 5/5] doc: edison: Rewrite the update instructions Simon Glass
2026-06-17  6:41   ` Andy Shevchenko [this message]
2026-06-17  6:44     ` Andy Shevchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ajJBmmhl1Gk9n4GP@black.igk.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox