[PATCH 5/5] doc: edison: Rewrite the update instructions

[Andy Shevchenko]

On Sun, Jun 07, 2026 at 05:05:14PM -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 that the bare u-boot.bin lacks), note that a
> bricked board enters DnX without any straps, and add udev rules for
> running the tools without sudo.

...

> -By default Intel Edison boards are shipped with preinstalled heavily
> -patched U-Boot v2014.04. Though it supports DFU which we may be able to
> -use.

I think we need to have a reference to this aspect somewhere.

...

> +Updating U-Boot over DFU
> +------------------------
>  
> +Once a working U-Boot is present, updating it is just a DFU transfer into the
> +``u-boot0`` eMMC partition; the board boots the new U-Boot on the next reset.
>  
> +1. Prepend the 4KB alignment gap to ``u-boot.bin``::
>  
> +     $ { head -c 4096 /dev/zero; cat u-boot.bin; } > u-boot-edison-dfu.bin

But this step is not needed if we build upstream U-Boot, otherwise the whole
point of having out-of-the-box working binary is ruined. That's why we should
really distinguish the U-Boot from stock image and from upstream.

...

> +Copy ``xfstk-dldr-solo`` to ``/usr/local/bin`` and
> +``libboost_program_options.so.1.54.0`` to ``/usr/lib/i386-linux-gnu/``. You
> +might find this `drive`_ helpful for the recovery image and the libraries.
>  
> +Download and unpack the Edison recovery image, then, with the board powered

Intel Edison.

> +off, run:

...

>  .. code-block:: none
>  
> -  XFSTK Downloader Solo 1.8.5
> -  Copyright (c) 2015 Intel Corporation
> -  Build date and time: Aug 15 2020 15:07:13
> -
> -  .Intel SoC Device Detection Found
> -  Parsing Commandline....
> -  Registering Status Callback....
> -  .Initiating Download Process....
> -  .......(lots of dots)........XFSTK-STATUS--Reconnecting to device - Attempt #1
> -  .......(even more dots)......................

I believe it's still useful for users to understand that reconnection is not an
issue.

...

> -.. code-block:: none
> -
> -  ******************************
> -  PSH KERNEL VERSION: b0182b2b
> -  		WR: 20104000
> -  ******************************
> -
> -  SCU IPC: 0x800000d0  0xfffce92c
> -
> -  PSH miaHOB version: TNG.B0.VVBD.0000000c
> -
> -  microkernel built 11:24:08 Feb  5 2015
> -
> -  ******* PSH loader *******
> -  PCM page cache size = 192 KB
> -  Cache Constraint = 0 Pages
> -  Arming IPC driver ..
> -  Adding page store pool ..
> -  PagestoreAddr(IMR Start Address) = 0x04899000
> -  pageStoreSize(IMR Size)          = 0x00080000
> -
> -  *** Ready to receive application ***
> -
> -After another 10 seconds the xFSTK tool completes and the board resets. About
> -10 seconds after that should see the above message again and then within a few
> -seconds U-Boot should start on your board:

The above example seems also useful to me for the unprepared users.

-- 
With Best Regards,
Andy Shevchenko