From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: u-boot@lists.denx.de
Subject: U-Boot fails dfu on edison
Date: Thu, 3 Sep 2020 16:40:36 +0300 [thread overview]
Message-ID: <20200903134036.GD1891694@smile.fi.intel.com> (raw)
In-Reply-To: <CAPnjgZ005JCr-YPQR7RDnbRc9zhjdYv0-oyFuhbya-g368Da9Q@mail.gmail.com>
On Thu, Sep 03, 2020 at 07:15:59AM -0600, Simon Glass wrote:
> Hi,
>
> I'd like to get edison running in my lab but it has resisted two
> attempts so far.
>
> My latest problem is that when I try the latest U-Boot, I get:
>
> U-Boot 2020.10-rc3-00012-g9f04a634ef3 (Sep 03 2020 - 07:06:30 -0600)
Do you have clean repo?
Can't reproduce neither with my personal branch nor with vanilla -rc3:
~~~~
U-Boot 2020.10-rc3 (Sep 03 2020 - 16:33:27 +0300)
CPU: Intel(R) Atom(TM) CPU U1000 @ 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
=>
=> run do_force_flash_os
Saving Environment to MMC... Writing to redundant MMC(0)... OK
~~~~
Maybe something wrong with the environment?
...
> Target:blank
> Partitioning already done...
> Flashing already done...
> Memory layout (mmc) not supported!
> DFU entities configuration failed!
> (partition table does not match dfu_alt_info?)
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.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-09-03 13:40 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 [this message]
2020-09-03 13:51 ` Andy Shevchenko
2020-09-03 14:21 ` Simon Glass
2020-09-03 15:05 ` Andy Shevchenko
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=20200903134036.GD1891694@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