From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] NAND driver question
Date: Wed, 30 Jan 2008 08:45:05 +0100 [thread overview]
Message-ID: <200801300845.05577.sr@denx.de> (raw)
In-Reply-To: <67BFAF42E016FC40ADE4EE73E07B70600CA455@pks00005.kanatek.com>
On Tuesday 29 January 2008, Craig Millen wrote:
> I have been experiencing a few problems when using a NAND flash for
> storage in u-boot.
>
> When I'm reading large files (7MB) from the NAND, periodically there
> will be a NAND ECC read error when using the following command:
>
> => nand read 400000 0 154000
> NAND read: device 0 offset 0x0, size 0x154000 1392640 bytes read:
> ERROR.
>
> After turning on debug, the problem is occurring in the nand_read_ecc
> function whereby the ecc check fails. After running it numerous times,
> there seems to be no correlation between pages that fail and appears to
> be completely random.
> Has anyone else had these problems?
No. NAND blocks can fail and generate ECC errors. But your description doesn't
really sound like this is a NAND chips related problem. Does this happen on
multiple boards or just s single one? This looks more like a timing problem
or something like this to me.
IIRC, then you had to change the 4xx NDFC driver to access the NAND via 8bit
access, correct? I have used this driver on multiple 4xx boards and on all
boards this driver can be used as is, meaning with 32bit access enabled.
Perhaps you still have a problem with the interface to the NAND chips.
> Furthermore, the "nand write" command doesn't skip bad blocks. Are you
> supposed to use a different command to write files to the NAND that
> skips the bad blocks?
As already mentioned the .jffs2" extension is what you want. ".i" for "image"
should do too.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2008-01-30 7:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 16:44 [U-Boot-Users] NAND driver question Craig Millen
2008-01-29 19:36 ` Zach Sadecki
2008-01-30 7:45 ` Stefan Roese [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-01 19:55 Craig Millen
2008-02-02 7:49 ` Stefan Roese
2008-02-04 20:46 Craig Millen
2008-02-05 7:44 ` Stefan Roese
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=200801300845.05577.sr@denx.de \
--to=sr@denx.de \
--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.