MTD - NAND (Micron MT29F16G08)

[Ken Chan]

> Just a guess here, does it matter that the exact oob size is not
> supported? As long as there are enough bytes for what is needed (bad block
> indicator, ECC data, and jffs2 cleanmarkers if using jffs2 filesystem) it
> might not matter what the exact size is. Most flashes support reading and
> writing less than a full page or oob.
>

I tried to use "oob_64" and format the NAND Flash to use jffs2 filesystem.
The format part went well.  It detected a few bad sectors.....
After the format finished, I tried to do "mount -t jffs2
/dev/mtdblock8 /nand" but I got
the following exception error message:

sh-2.05b# mount -t jffs2 /dev/mtdblock8 /nand

[  617.996658] Oops: kernel access of bad area, sig: 11 [#1]
[  618.019446] NIP: FFFFFFFC LR: FFFFFFFF CTR: 00000000
[  618.049179] REGS: cb615b00 TRAP: 0400   Not tainted  (2.6.16.1)
[  618.084642] MSR: 00029200 <EE,ME>  CR: 28004482  XER: 20000000

ken



On Wed, Feb 20, 2008 at 11:25 AM, Ricard Wanderlof
<ricard.wanderlof at axis.com> wrote:
>
>
> On Wed, 20 Feb 2008, Ken Chan wrote:
>
> > Hi,
> > I am trying to get my NAND Flash (Micron MT29F16G08 -- 2 GBytes NAND) going.
> > Based on the data sheet, the page size is 4KB, the Spare area size (i.e.
> > OOB) is 218 Bytes, the Block size is 512KB.
> > I am using Linux Kernel 2.6.16 and it does not support this NAND Flash
> > because of the OOB is 218 Bytes.
> > I checked the Linux Kernel (2.6.24) and same thing applied.
> >
> > Here are my questions:
> > 1) How can I build a data structure "struct nand_oobinfo nand_oob_218"?
> > What shall I put for those eccpos[]?
> > 2) If I don't want to create that new data structure, what is the
> > alternative method to bring up that NAND Flash?
> > 3) Do anyone have similar problem using that kind of NAND Flash?
>