From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 2/3] mx25: Select the ESDHC_A001 erratum
Date: Fri, 3 Nov 2017 17:48:11 -0200 [thread overview]
Message-ID: <CAP9ODKoVhNprz1XnDKbYkj86gh4ApwCCsNoKyYQ_pqVWKpv_Rw@mail.gmail.com> (raw)
In-Reply-To: <1509723610-27434-2-git-send-email-festevam@gmail.com>
On Fri, Nov 3, 2017 at 1:40 PM, Fabio Estevam <festevam@gmail.com> wrote:
> From: Fabio Estevam <fabio.estevam@nxp.com>
>
> When a high speed card is connected to mx25 the following error is seen:
>
> U-Boot 2017.11-rc2-00104-gb79372a (Oct 31 2017 - 11:02:22 -0200)
>
> CPU: Freescale i.MX25 rev1.2 at 399 MHz
> Reset cause: POR
> Board: MX25PDK
> I2C: ready
> DRAM: 64 MiB
> No arch specific invalidate_icache_all available!
> MMC: FSL_SDHC: 0
> *** Warning - read failed, using default environment
> In: serial
> Out: serial
> Err: serial
> Net: FEC
> Hit any key to stop autoboot: 0
> => saveenv
> Saving Environment to MMC...
> Writing to MMC(0)... failed
>
> , which prevents any usage of the SD card.
>
> The root cause for the failure is the eSDHC-A001 erratum:
>
> "eSDHC-A001 : Data timeout counter (SYSCTL[DTOCV]) is not reliable for
> values of 0x4,0x8, and 0xC" that is listed
> on some PowerArchitecture chips:
> https://www.nxp.com/files-static/32bit/doc/errata/MPC8379ECE.pdf
>
> Even though eSDHC-A001 is not documented on the i.MX25 errata document,
> I have confirmed with the NXP design team that this erratum does affect
> i.MX25, so fix the problem by selecting SYS_FSL_ERRATUM_ESDHC_A001
> at SoC level.
>
> Successfully tested with a high speed SD card on a mx25pdk board.
>
> Suggested-by: Benoît Thébaudeau <benoit@wsystem.com>
> Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
> Acked-by: Sebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com>
Acked-by: Otavio Salvador <otavio@ossystems.com.br>
Tested-by: Otavio Salvador <otavio@ossystems.com.br> # mx25pdk
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
next prev parent reply other threads:[~2017-11-03 19:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 15:40 [U-Boot] [PATCH v3 1/3] mx25: Move MX25 selection to Kconfig Fabio Estevam
2017-11-03 15:40 ` [U-Boot] [PATCH v3 2/3] mx25: Select the ESDHC_A001 erratum Fabio Estevam
2017-11-03 19:48 ` Otavio Salvador [this message]
2017-11-03 15:40 ` [U-Boot] [PATCH v3 3/3] mx51: " Fabio Estevam
2017-11-03 21:21 ` [U-Boot] [PATCH v3 1/3] mx25: Move MX25 selection to Kconfig Benoît Thébaudeau
2017-11-06 23:44 ` Fabio Estevam
2017-11-07 1:22 ` Tom Rini
2017-11-07 9:10 ` Stefano Babic
2017-11-10 20:19 ` Benoît Thébaudeau
2017-11-10 20:47 ` 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=CAP9ODKoVhNprz1XnDKbYkj86gh4ApwCCsNoKyYQ_pqVWKpv_Rw@mail.gmail.com \
--to=otavio.salvador@ossystems.com.br \
--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.