From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] NAND: bad block in whole chip
Date: Wed, 13 Aug 2008 16:44:39 +0200 [thread overview]
Message-ID: <200808131644.39475.sr@denx.de> (raw)
In-Reply-To: <d970ff420808130710s67722e46j2d0461a86ef1e110@mail.gmail.com>
On Wednesday 13 August 2008, Alemao wrote:
> Now i got all NAND stuffs from u-boot-1.3.4, including common/cmd_nand.c
> and drivers/mtd/nand/*, but still the same problem.
>
> Other components of u-boot can influence NAND behavior?
>
> I saw some people with similar problem using "nand scrub", but im little
> bit afraid with this command...
Yes, you should be. Be careful with this command.
Note that in all cases where I read all NAND blocks as bad, either the NAND
driver had a problem or the hardware had a problem. Are you sure that the
hardware is ok?
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-08-13 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 17:28 [U-Boot-Users] NAND: bad block in whole chip Alemao
2008-08-12 17:30 ` [U-Boot] " Alemao
2008-08-12 17:57 ` Scott Wood
2008-08-13 14:10 ` Alemao
2008-08-13 14:44 ` Stefan Roese [this message]
2008-08-14 17:22 ` Alemao
2008-08-27 14:52 ` Alemao
-- strict thread matches above, loose matches on Subject: below --
2008-08-13 14:34 Darrik Spaude
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=200808131644.39475.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox