From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: u-boot@lists.denx.de
Subject: U-Boot fails dfu on edison
Date: Thu, 3 Sep 2020 18:05:44 +0300 [thread overview]
Message-ID: <20200903150544.GH1891694@smile.fi.intel.com> (raw)
In-Reply-To: <CAPnjgZ0kj5QJEp2Y=VM2WshDx96ykB7gvY+gPUCZrAqVQ9T+Dg@mail.gmail.com>
On Thu, Sep 03, 2020 at 08:21:23AM -0600, Simon Glass wrote:
> On Thu, 3 Sep 2020 at 07:51, Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> > On Thu, Sep 3, 2020 at 4:40 PM Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> wrote:
> > > On Thu, Sep 03, 2020 at 07:15:59AM -0600, Simon Glass wrote:
...
> > > Hmm... Have you read this [1]? It may give some hints I think.
> > >
> > > [1]: https://edison-fw.github.io/edison-wiki/u-boot-update (look into known-bugs section)
> > >
> > > > Any ideas please?
> > >
> > > See above.
> >
> > Just in case my script [2] to prepare a U-Boot image file suitable for xFSTK.
> >
> > [2]: https://gist.github.com/andy-shev/2c388310f2773ead647d9c1a3f1c813f
>
> Thanks, that gets me a bit closer. Here are my steps:
>
> 1. Start with the original 2014 U-Boot from 'flashall.sh --recovery'
> 2. Boot it and use dfu-util to flash the latest 2020 U-Boot as per edison.rst
> 3. Set env vars as guessed from the link you provided:
>
> setenv dfu_alt_info "ifwi${hardware_id} raw 0 8192 mmcpart
> 1;ifwib${hardware_id} raw 0 8192 mmcpart 2;u-boot0 part 0
> 1;u-boot-env0 part 0 2;u-boot1 part 0 3;u-boot-env1 part 0 4;boot part
> 0 7;rootfs part 0 8;update part 0 9;home part 0 10;vmlinuz fat 0
> 7;initrd fat 0 7"
> setenv do_dfu_alt_info_ifwi 'setenv dfu_alt_info "ifwi${hardware_id}
> raw 0 8192 mmcpart 1;ifwib${hardware_id} raw 0 8192 mmcpart 2"'
> setenv do_dfu_alt_info_mmc 'setenv dfu_alt_info "ifwi${hardware_id}
> raw 0 8192 mmcpart 1;ifwib${hardware_id} raw 0 8192 mmcpart 2;u-boot0
> part 0 1;u-boot-env0 part 0 2;u-boot1 part 0 3;u-boot-env1 part 0
> 4;boot part 0 7;rootfs part 0 8;update part 0 9;home part 0 10;vmlinuz
> fat 0 7;initrd fat 0 7"'
> setenv do_flash_ifwi 'run do_dfu_alt_info_ifwi ; dfu 0 raw 3'
> setenv do_force_flash_os 'run do_dfu_alt_info_mmc ; sleep 1 ; setenv
> do_flash_os_done 1 ; saveenv ; dfu 0 raw 3'
^^^
> 4. Reboot and see:
>
> U-Boot 2020.10-rc3-00012-g9f04a634ef3 (Sep 03 2020 - 07:06:30 -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
> Net: No ethernet found.
> Hit any key to stop autoboot: 0
> Target:ifwi
> Partitioning already done...
> Partitioning already done...
> Saving Environment to MMC... Writing to redundant MMC(0)... OK
> dfu_fill_entity: Device raw not (yet) supported!
> So I am still missing something?
Yes. You haven't read the Issue #3 [3] mentioned in the known-bug section in [1].
[3]: https://github.com/intel/edison-u-boot/issues/3
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-09-03 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 13:15 U-Boot fails dfu on edison Simon Glass
2020-09-03 13:40 ` Andy Shevchenko
2020-09-03 13:51 ` Andy Shevchenko
2020-09-03 14:21 ` Simon Glass
2020-09-03 15:05 ` Andy Shevchenko [this message]
2020-09-03 15:49 ` Andy Shevchenko
2020-09-14 22:03 ` Ferry Toth
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=20200903150544.GH1891694@smile.fi.intel.com \
--to=andy.shevchenko@gmail.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