public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] environment in NAND
Date: Tue, 6 Sep 2011 16:23:08 +0200	[thread overview]
Message-ID: <201109061623.08797.marek.vasut@gmail.com> (raw)
In-Reply-To: <CAACX+R38SwZeo199cugVRfMQn8VMNALaUN3hjSJPmDtWzAUzwQ@mail.gmail.com>

On Tuesday, September 06, 2011 04:16:59 PM Arno Steffen wrote:
> NAND is sufferered from Bad blocks and bit errors. Thats why usually
> exists a bad block handling and an ECC. Am I wrong, that I miss both
> on uboot  for it's environment?
> Or is my uboot just to old (2010.06) and newer versions handle this?
> Is there a special setting necessary to handle this?
> I see that environment is CRC protected but this make things even
> worse, if not an important bit is toogled.
> Best regards
> Arno

Hi,

the mtd subsystem in uboot is based on the one from linux. The ECC handling is 
there, no problem. The problem you might experience is in case you have a 
wrongly implemented NAND driver, which ignores ECC.

What board/cpu do you use? Also, why so old uboot, use mainline?

Cheers

> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot

  parent reply	other threads:[~2011-09-06 14:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-06 14:16 [U-Boot] environment in NAND Arno Steffen
2011-09-06 14:22 ` Wolfgang Wegner
2011-09-06 14:23 ` Marek Vasut [this message]
2011-09-07  6:20   ` Arno Steffen
2011-09-07  7:02     ` Wolfgang Wegner
2011-09-07  9:34       ` Arno Steffen
2011-09-07  9:35         ` Wolfgang Wegner
2011-09-07 10:20           ` Arno Steffen
2011-09-07 11:07             ` Wolfgang Wegner
2011-09-15 22:34         ` Scott Wood

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=201109061623.08797.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.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