summaryrefslogtreecommitdiff
path: root/common/env_nvram.c
diff options
context:
space:
mode:
authorRostislav Lisovy <lisovy@gmail.com>2014-09-02 17:00:30 +0200
committerTom Rini <trini@ti.com>2014-09-04 13:06:00 -0400
commitcc81a5291910d7a3016a65042bec7b4e54e81d03 (patch)
tree6cdf8400cd263a70202e3f4c95e914ee95e2f1bb /common/env_nvram.c
parent5c3f7e0ead6db15dc1888cd126b2420ae87980c4 (diff)
downloadu-boot-imx-cc81a5291910d7a3016a65042bec7b4e54e81d03.zip
u-boot-imx-cc81a5291910d7a3016a65042bec7b4e54e81d03.tar.gz
u-boot-imx-cc81a5291910d7a3016a65042bec7b4e54e81d03.tar.bz2
mtd: nand: omap_gpmc: Fix 'bit-flip' errors
OMAP GPMC driver used with some NAND Flash devices (e.g. Spansion S34ML08G1) causes that U-boot shows hundreds of 'nand: bit-flip corrected' error messages. Possible cause was discussed in the mailinglist thread: http://lists.denx.de/pipermail/u-boot/2014-April/177508.html Quote (Author: Pekon Gupta <pekon@ti.com>): "The issue is mainly due to a NAND protocol violation in the omap driver since the Random Data Output command (05h-E0h) expects to see only the column address that should be addressed within the already loaded read page into the read buffer. Only 2 address cycles with ALE active should be provided between the 05h and E0h commands. The Page read command expects the full address footprint (2bytes for column address + 3bytes for row address), but once the page is loaded into the read buffer, Random Data Output should be used with only 2bytes for column address." This patch combines the solution proposed in the mailinglist and the patch provided by the Spansion company (GPLv2 code, source: http://www.spansion.com/Support/Software/u-boot-psp-04.04.00.01-NAND.zip) Signed-off-by: Rostislav Lisovy <lisovy@merica.cz>
Diffstat (limited to 'common/env_nvram.c')
0 files changed, 0 insertions, 0 deletions