From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <scottwood@freescale.com>
Date: Tue, 15 Jan 2013 11:33:20 -0600
Subject: [U-Boot] NAND flash - bad blocks
In-Reply-To: <008001cdf310$c2002c70$2901a8c0@dpn> (from dpn@switchfin.org on
	Tue Jan 15 05:09:16 2013)
References: <1357935693.5475.11@snotra> <008001cdf310$c2002c70$2901a8c0@dpn>
Message-ID: <1358271200.7463.0@snotra>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 01/15/2013 05:09:16 AM, Dimitar Penev wrote:
> Hi Scott,
> 
> I have tried to do some more tests on the board with the NAND chip I  
> have scrub-ed
> 
> -I have done 'nand erase.chip clean'

Don't specify "clean".  That will cause jffs2 cleanmarkers to be  
written.  Not all NAND chips can handle partial programming, and in any  
case it's an unnecessary variable for figuring out the bad block  
situation.

> and tried to probe different nand regions
> (I have 128MB RAM and 1GB NAND and I am not sure how I could dump the  
> whole NAND at once)
> It seems the whole NAND is 0xFF

Including OOB?

> So I tend to think that nand scrub did a good think for me.

No, it didn't.  You are ignoring the problem.

-Scott