Re: NAND write verify failed problem

[Pantelis Antoniou <panto@intracom.gr>]

Thomas Gleixner wrote:

>On Monday 02 June 2003 13:04, Pantelis Antoniou wrote:
>  
>
>> > root$ fcp -v /tmp/root.jffs2.image /dev/mtd0
>> > Erasing blocks: 33/33 (100%)
>> > Writing data: 528k/528k (100%)
>> > Verifying data: 20k/528k (3%)File does not seem to match flash data.
>>    
>>
>Are you writing with ECC ? If not use nandwrite from mtd/utils
>
>  
>
>>Mount takes 30 seconds to finish, and during that time the board does not
>>respond to any external stimulus. This is caused I believe from the scaning
>>of the NAND, which I take it is normal.
>>    
>>
>Should be much faster with current MTD CVS code
>
>
>  
>
>>nand_write_page: Failed write verify, page 0x0000040b <5>Write of 68
>>bytes at 0x00081774 failed. returned -5, retlen 0
>>Mar 10 21:44:22 netvia-ppc kernel: Not marking the space at 0x00081774
>>as dirty because the flash driver returned retlen zero
>>Any ideas how to proceed?
>>
>
>Yes, update nand driver from MTD-CVS. It's fixed.
>  
>

I ran into problems by trying to use a vanilla 2.4.21-rc7 with utils 
from the MTD latest snapshot.

Patching the kernel with the MTD-CVS fixed everything.

BTW, is there something anologous to CRAMFS for NAND flash?
I have a need for a compressed read-only filesystem on NAND
but CRAMFS has no concept of bad blocks.

Regards and thanks for the reply.

Pantelis