From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <scottwood@freescale.com>
Date: Thu, 26 Apr 2012 14:26:22 -0500
Subject: [U-Boot] A problem about using the nand command
In-Reply-To: <BLU166-W11B6488BC1C152299941C8C6240@phx.gbl>
References: <BLU166-W11B6488BC1C152299941C8C6240@phx.gbl>
Message-ID: <4F99A15E.7010402@freescale.com>
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 04/25/2012 09:07 PM, li guohu wrote:
> 
> Hello, everyone!
> I find a strange problem when I use the u-boot command. I list the command I used in the u-boot command line as follows.
>  
> nand erase
> nand read 0x2000000 0x0 0x800
> md 0x2000000
>  
> I should see 2K bytes of "0xFF" because I have erase the whole nand flash device.

What version of U-Boot are you using?

With modern U-Boot you need "nand erase.chip".  Please try with current
U-Boot.

> Actually, I find a "0xFD" in one address. 
> Then I try display some other contend of the nand flash. I can also find one "0xFD" in every 2K address space. It is so strange.

What board/driver?

What do you see if you list the bad blocks?

-Scott