public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [PATCH 5/5] x86: edison: Add documentation for using am xFSTK image
Date: Fri, 4 Sep 2020 12:43:56 +0300	[thread overview]
Message-ID: <20200904094356.GK1891694@smile.fi.intel.com> (raw)
In-Reply-To: <20200904012856.1175506-6-sjg@chromium.org>

On Thu, Sep 03, 2020 at 07:28:56PM -0600, Simon Glass wrote:
> Add a description of how to flash Edison using the XFSTK tool.

Switch to OSIP and mentioned DnX may affect the wording here, though I didn't
see if it really the case. Also, please update with using clean U-Boot version
(no Git hash, no dirty suffix).

After addressing,
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
> 
>  doc/board/intel/edison.rst | 120 +++++++++++++++++++++++++++++++++++++
>  1 file changed, 120 insertions(+)
> 
> diff --git a/doc/board/intel/edison.rst b/doc/board/intel/edison.rst
> index 1aee2a1fc0d..40acd80a051 100644
> --- a/doc/board/intel/edison.rst
> +++ b/doc/board/intel/edison.rst
> @@ -39,3 +39,123 @@ use.
>     reset the board::
>  
>     => reset
> +
> +
> +Updating U-Boot using xFSTK
> +---------------------------
> +
> +You can also update U-Boot using the xfstk-dldr-solo tool if you can build it.
> +One way to do that is to follow the `xFSTK`_ instructions. You may need to use
> +a virtual machine running Ubuntu Trusty. Once you have built it and installed
> +libboost-all-dev, you can copy xfstk-dldr-solo to /usr/local/bin and
> +libboost_program_options.so.1.54.0 to /usr/lib/i386-linux-gnu/ and with luck
> +it will work. You might fine this `drive`_ helpful.
> +
> +If it does, then you can download and unpack the Edison reocovery image,
> +install dfu-util, reset your board and flash U-Boot like this::
> +
> +   $ xfstk-dldr-solo --gpflags 0x80000007 \
> +      --osimage u-boot-edison.img \
> +      --fwdnx recover/edison_dnx_fwr.bin \
> +      --fwimage recover/edison_ifwi-dbg-00.bin \
> +      --osdnx recover/edison_dnx_osr.bin
> +
> +This should show the following
> +
> +.. code-block:: none
> +
> +  XFSTK Downloader Solo 0.0.0
> +  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)......................
> +
> +
> +You have about 10 seconds after resetting the board to type the above command.
> +If you want to check if the board is ready, type:
> +
> +.. code-block:: none
> +
> +  lsusb |egrep "8087|8086"
> +  Bus 001 Device 004: ID 8086:e005 Intel Corp.
> +
> +If you see a device with the same ID as above, the board is waiting for your
> +command.
> +
> +After about 5 seconds you should see some console output from the board:
> +
> +.. 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:
> +
> +.. code-block:: none
> +
> +  U-Boot 2020.10-rc3-00032-gd9f6680e925-dirty (Sep 03 2020 - 18:44:28 -0600)
> +
> +  CPU:   Genuine Intel(R) CPU   4000  @  500MHz
> +  DRAM:  980.6 MiB
> +  WDT:   Started with servicing (60s timeout)
> +  MMC:   mmc at ff3fc000: 0, mmc at ff3fa000: 1
> +  Loading Environment from MMC... OK
> +  In:    serial
> +  Out:   serial
> +  Err:   serial
> +  Saving Environment to MMC... Writing to redundant MMC(0)... OK
> +  Saving Environment to MMC... Writing to MMC(0)... OK
> +  Net:   No ethernet found.
> +  Hit any key to stop autoboot:  0
> +  Target:blank
> +  Partitioning using GPT
> +  Writing GPT: success!
> +  Saving Environment to MMC... Writing to redundant MMC(0)... OK
> +  Flashing already done...
> +  5442816 bytes read in 238 ms (21.8 MiB/s)
> +  Valid Boot Flag
> +  Setup Size = 0x00003c00
> +  Magic signature found
> +  Using boot protocol version 2.0c
> +  Linux kernel version 3.10.17-poky-edison+ (ferry at kalamata) #1 SMP PREEMPT Mon Jan 11 14:54:18 CET 2016
> +  Building boot_params at 0x00090000
> +  Loading bzImage at address 100000 (5427456 bytes)
> +  Magic signature found
> +  Kernel command line: "rootwait root=PARTUUID=ada722ed-6410-764e-8619-abff6f66e10e rootfstype=ext4 console=ttyMFD2 earlyprintk=ttyMFD2,keep loglevel=4 g_multi.ethernet_config=cdc systemd.unit=multi-user.target hardware_id=00 g_multi.iSerialNumber=2249baf774c675598661a63098c0ad41 g_multi.dev_addr=02:00:86:c0:ad:41 platform_mrfld_audio.audio_codec=dummy"
> +  Magic signature found
> +
> +  Starting kernel ...
> +
> +  ...
> +
> +  Poky (Yocto Project Reference Distro) 1.7.2 edison ttyMFD2
> +
> +  edison login:
> +
> +.. _xFSTK: https://community.intel.com/t5/Intel-Makers/Building-xFSTK-on-Ubuntu-14-04-32-bit-for-flashing-Edison/td-p/538081
> +.. _drive: https://drive.google.com/drive/u/0/folders/1URPHrOk9-UBsh8hjv-7WwC0W6Fy61uAJ
> -- 
> 2.28.0.526.ge36021eeef-goog
> 

-- 
With Best Regards,
Andy Shevchenko

  reply	other threads:[~2020-09-04  9:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04  1:28 [PATCH 0/5] edison: Support for writing an xFSTK image Simon Glass
2020-09-04  1:28 ` [PATCH 1/5] x86: Use multiple images Simon Glass
2020-09-04  9:30   ` Andy Shevchenko
2020-09-04  1:28 ` [PATCH 2/5] binman: Show an error when a file is missing Simon Glass
2020-09-04  9:33   ` Andy Shevchenko
2020-09-07  1:43     ` Simon Glass
2020-09-07  9:05       ` Andy Shevchenko
2020-09-07 13:57         ` Simon Glass
2020-09-04  1:28 ` [PATCH 3/5] binman: Support adding a U-Boot environment Simon Glass
2020-09-04  9:37   ` Andy Shevchenko
2020-09-04  1:28 ` [PATCH 4/5] x86: edison: Generate an image suitable for xFSTK Simon Glass
2020-09-04  9:39   ` Andy Shevchenko
2020-09-04  1:28 ` [PATCH 5/5] x86: edison: Add documentation for using am xFSTK image Simon Glass
2020-09-04  9:43   ` Andy Shevchenko [this message]
2020-09-04  9:46 ` [PATCH 0/5] edison: Support for writing an " Andy Shevchenko
2020-09-05  3:23   ` Simon Glass
2020-09-07  8:04     ` Andy Shevchenko
2020-09-07 13:57       ` Simon Glass
2020-09-07 14:12         ` Tom Rini
2020-09-07 14:15           ` Simon Glass
2020-09-07 15:10             ` Andy Shevchenko
2020-09-22  7:11 ` Bin Meng
2020-09-22 22:03   ` Simon Glass
2020-09-24  3:22     ` Bin Meng
2020-09-24  3:27       ` Bin Meng
2020-09-25  1:00         ` Simon Glass

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=20200904094356.GK1891694@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.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