Question relates 2K page size flash chip

Question relates 2K page size flash chip

[peter meng]

Hi

I met a problem that use K9F1G08 flash with 2K page size on Linux .
I tried jffs2 and yaffs2 file system but occurs same error info as following 

----------------------------------------------------------
NAND device: Manufacturer ID: 0xec, Chip ID: 0xa1 (Samsung NAND 128MiB 1,8V 8-bit)
NAND_ECC_NONE selected by board driver. This is not recommended !!
Scanning device for bad blocks
nand_read_oob: from = 0x00000000, len = 64
Bad eraseblock 0 at 0x00000000
nand_read_oob: from = 0x00020000, len = 64
Bad eraseblock 0 at 0x00020000
........
........
nand_isbad_bbt(): bbt info for offs 0x007a0000: (block 61) 0x03
block 46 is bad
nand_isbad_bbt(): bbt info for offs 0x007c0000: (block 62) 0x03
block 47 is bad
nand_isbad_bbt(): bbt info for offs 0x007e0000: (block 63) 0x03
block 48 is bad
VFS: Mounted root (yaffs2 filesystem).
Freeing init memory: 88K
Warning: unable to open an initial console.
Failed to execute /linuxrc.  Attempting defaults...
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

------------------------------------------------------------

I checked the /dev/console and /linuxrc is exist on rootfs .

Seems this problem is caused since 2K page size with flash ,so how to resolve this problem ? Whether need do related work within u-boot because I suppose u-boot given wrong data format to flash that Linux mtd does not know it ?



Thanks Advanced .
Best Regards.
Peter Meng



      

Re: Question relates 2K page size flash chip

[Ricard Wanderlof]

On Sat, 3 Jan 2009, peter meng wrote:

> I met a problem that use K9F1G08 flash with 2K page size on Linux .
> I tried jffs2 and yaffs2 file system but occurs same error info as following
>
> NAND device: Manufacturer ID: 0xec, Chip ID: 0xa1 (Samsung NAND 128MiB 
> 1,8V 8-bit)
> ...
> Seems this problem is caused since 2K page size with flash ,so how to 
> resolve this problem ? Whether need do related work within u-boot 
> because I suppose u-boot given wrong data format to flash that Linux mtd 
> does not know it ?

Why do you think it is related to the 2k page size? This type of flash has 
been supported by mtd for a very long time now.

/Ricard
--
Ricard Wolf Wanderlöf                           ricardw(at)axis.com
Axis Communications AB, Lund, Sweden            www.axis.com
Phone +46 46 272 2016                           Fax +46 46 13 61 30

Re: Question relates 2K page size flash chip

[peter meng]

Hi,Ricard 

Thanks a lot.
Because linux deem all block is bad block  when scan flash .
I debug it that found need u-boot add OOB information into flash .


Best Regards.
Peter Meng




--- On Mon, 1/5/09, Ricard Wanderlof <ricard.wanderlof@axis.com> wrote:

> From: Ricard Wanderlof <ricard.wanderlof@axis.com>
> Subject: Re: Question relates 2K page size flash chip
> To: "peter meng" <mengsanshui@yahoo.com.cn>
> Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
> Date: Monday, January 5, 2009, 3:52 PM
> On Sat, 3 Jan 2009, peter meng wrote:
> 
> > I met a problem that use K9F1G08 flash with 2K page
> size on Linux .
> > I tried jffs2 and yaffs2 file system but occurs same
> error info as following
> > 
> > NAND device: Manufacturer ID: 0xec, Chip ID: 0xa1
> (Samsung NAND 128MiB 1,8V 8-bit)
> > ...
> > Seems this problem is caused since 2K page size with
> flash ,so how to resolve this problem ? Whether need do
> related work within u-boot because I suppose u-boot given
> wrong data format to flash that Linux mtd does not know it ?
> 
> Why do you think it is related to the 2k page size? This
> type of flash has been supported by mtd for a very long time
> now.
> 
> /Ricard
> --
> Ricard Wolf Wanderlöf                          
> ricardw(at)axis.com
> Axis Communications AB, Lund, Sweden           
> www.axis.com
> Phone +46 46 272 2016                           Fax +46 46
> 13 61 30