[U-Boot] U-boot and JFFS2
Pillai, Manikandan
mani.pillai at ti.com
Mon Mar 16 12:41:38 CET 2009
Hi,
The cleanmarkers are being written in location 0x0 and 0x1 of the OOB space
And they are the problem since when u-boot comes up it does a scan and decided
That since these OOB locations do not contain 0xff, the blocks are bad.
Regards
Manikandan
> -----Original Message-----
> From: Nishanth Menon [mailto:menon.nishanth at gmail.com]
> Sent: Monday, March 16, 2009 5:09 PM
> To: Pillai, Manikandan
> Cc: u-boot at lists.denx.de
> Subject: Re: [U-Boot] U-boot and JFFS2
>
> Pillai, Manikandan said the following on 03/16/2009 01:35 PM:
> > Hi,
> >
> > On the OMAP3 EVM board, I have four partition on my Onenand flash of which
> /dev/mtd4 is a JFFS2 partition.
> >
> > After booting up linux, I use the following command to mount the jffs2 empty
> partition.
> >
> > Linux#> mount -t jffs2 /dev/mtdblock4 /mnt
> >
> > Then I do a reboot .
> >
> > When u-boot boots up it gives bad erase block for all the blocks used by
> /dev/mtd4.
> >
> > The reason is the JFFS2 filesystem is putting some signature at location 0x0
> and 0x1 of OOB locations
> > of every block.
> >
> > Is there a way this can be avoided ?
> >
> >
> A)
> mount -t jffs2 /dev/mtdblock4 /mnt
> umount /mnt
> sync
> reboot
>
> this gives the garbage collector time to put the cleanmarkers in place.
>
> B) is the kernel's oob layout and ECC strategy (h/w vs s/w ecc) same as
> that used for u-boot?
>
> Regards,
> Nishanth Menon
More information about the U-Boot
mailing list