From: Eric Nelson <eric@nelint.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx6ul_evk: Remove SPL support
Date: Tue, 19 Apr 2016 18:27:53 -0700 [thread overview]
Message-ID: <5716DB19.2080909@nelint.com> (raw)
In-Reply-To: <CAOMZO5CsJFi6Jh4kvrhKiO2i0MRNwUUb3h5e_7OQz-QFXc9JPw@mail.gmail.com>
Hi Fabio,
On 04/19/2016 05:45 PM, Fabio Estevam wrote:
> Hi Eric,
>
> On Tue, Apr 19, 2016 at 9:21 PM, Eric Nelson <eric@nelint.com> wrote:
>
>> Do you have details of which cards are failing and how?
>
> The brand that fails is SanDisk 8GB microSD HC I (4).
>
> If I change to a Kingston card, then it boots fine.
>
Interesting.
Does the SanDisk card load using the full U-Boot?
>> Do they also fail on other platforms?
>
> Yes, they also fail in the other SPL platforms I have access to like
> mx6q-sabresd, for example.
>
> They failure pattern is like this:
>
> U-Boot SPL 2016.05-rc1-00110-g0973972-dirty (Apr 19 2016 - 20:36:43)
> Trying to boot from MMC1
> hdr read sector 8a, count=0
> spl: mmc block read error from mmc_load_image_raw_sector
> SPL: failed to boot from all boot devices
>
> Inside mmc_load_image_raw_sector() we have:
>
> /* read image header to find the image size & load address */
> count = mmc->block_dev.block_read(&mmc->block_dev, sector, 1, header);
>
> and 'coun't always return 0 for these cards.
>
I'd suggest reviewing the pad settings and clock setup between
the SPL and full U-Boot, but I suspect you've already done that.
next prev parent reply other threads:[~2016-04-20 1:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 15:19 [U-Boot] [PATCH] mx6ul_evk: Remove SPL support Fabio Estevam
2016-04-19 19:22 ` Otavio Salvador
2016-04-19 20:13 ` Fabio Estevam
2016-04-19 20:19 ` Otavio Salvador
2016-04-20 14:17 ` Tom Rini
2016-04-21 0:34 ` Fabio Estevam
2016-04-21 1:56 ` Fabio Estevam
2016-04-20 0:21 ` Eric Nelson
2016-04-20 0:45 ` Fabio Estevam
2016-04-20 1:27 ` Eric Nelson [this message]
2016-04-20 13:22 ` Fabio Estevam
2016-04-19 20:11 ` Stefano Babic
2016-04-21 15:11 ` Dennis Gilmore
2016-04-21 18:32 ` Fabio Estevam
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=5716DB19.2080909@nelint.com \
--to=eric@nelint.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.