Interest in DOC and YAFFS? --> YAFFS bootloading
nick at cecomputing.co.uk
Tue Sep 24 14:23:24 EDT 2002
> On Tue, Sep 24, 2002 at 08:23:06AM +0100, Nick Bane wrote:
> > The modifications I made to bootldr (CRL bootloader as used in iPaq
> > handhelds) were trivial after mkysffsimage was fixed (ask for a copy as
> > CVS one is still badly broken).
> > Bootldr copies the data 512+16 bytes at a time into non-broken NAND. The
> > kernel is then booted with prior knowledge as to where to find the YAFFS
> > data and all is ok.
> What is non-broken NAND?
NAND is not guarranteed 100% working. Individual pages may break. This
renders the whole erase block (a collection of pages) unusable. The
tradition is to mark the block as broken by clearing more than one bit in
certain bytes of the oob (spare) data on each page. Non-broken NAND is where
this oob data is marked as valid - typically 0xff.
> > How this works with DOC I am unclear as I had noticed a while back that
> > there was hardware assisted ECC. This might get in the way of YAFFS ECC
> > maybe this can be circumvented.
> As far as I can tell, the hardware ECC just makes the DOC faster.
Umm. It may use some of the oob data area for its own ECC in a YAFFS
incompatible way. I am not sure of my ground here, only that you need to
check it out.
> Also, I think that Microsys has released information about how to use
> the hardware ECC.
More information about the linux-mtd