> >>I did a "eraseall" of the device, but the moment I try to write, it's
> >>all marked bad...
> >>Any new hints?
> > Make sure that bad block checking in the MTD layer is commented
> out (it does wipe all the factory marked bad blocks but in my
> experience this is not a crisis for development work) or the
> blocks are not erased at all and remain "bad".
>
> Well, the device does report 99% free according to "df" after eraseall.
> Further, a "mkyaffs" on the device does not state that there is
> thousands of bad blocks - just the factory ones, so I think eraseall
> does it correct?
> Moreover, I tried it on a new NAND device never before being used for
> YAFFS, and the same occured (with my new kernel without YAFFS_ECC)...
>
> You still think I should try without bad block checking?
No. It sounds like the mtd layer is content.
I am surprised that you are having this grief. You will probably need to add a liberal smattering of printks to tease ot the issue. Is it the mtd layer reporting write errors? Is it read/write oob reporting rubbish?
>
> // Martin
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.9.2/53 - Release Date: 20/07/2005
(text/plain)