From: Zach Sadecki <zach.sadecki@ripcode.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] NAND driver question
Date: Tue, 29 Jan 2008 13:36:27 -0600 [thread overview]
Message-ID: <479F803B.60702@ripcode.com> (raw)
In-Reply-To: <67BFAF42E016FC40ADE4EE73E07B70600CA455@pks00005.kanatek.com>
"nand write.jffs2" skips bad blocks. I always thought that was a bad
name as it has nothing to do with jffs2 other than skipping is how jffs2
handles bad blocks...
Zach
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?
>
>
> 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?
>
>
> Thanks
> Craig
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
next prev parent reply other threads:[~2008-01-29 19:36 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 [this message]
2008-01-30 7:45 ` Stefan Roese
-- 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=479F803B.60702@ripcode.com \
--to=zach.sadecki@ripcode.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