A question on ECC

[Earl Manning]

Hi Tom and Edward,

I guess I misunderstood the question.  I didn't realize that the image was already up and running.  On my board I got that message because I had laid down the original image on the NAND flash without putting ECC into the OOB.

Althought, it does sound like new writes do use the SOFT ECC flag and that is why there are no complaints.  How did you get the ECC stuff into the OOB to start with?

Earl


On Tue, 15 Apr 2003 02:40:05 +0900
"Edward J. Lee" <noshel at idis.co.kr> wrote:

> Thomas Gleixner wrote:
> 
> >On Monday 14 April 2003 07:13, Edward Lee (???) wrote:
> >  
> >
> >>Hi Earl, thanks for the help.
> >>
> >>I didn't use nandwrite, I wrote on the chip using plain stuff like 'cp' or
> >>'tar', etc. (having a file system on my device, I couldn't find a reason
> >>to write files using other programs)
> >>    
> >>
> >nandwrite is just used to copy a filesystem image to a unformatted chip.
> >If you have mounted the fs already, then nandwrite would be the wrong tool.
> >
> >These messages have a different reason. I assume that you followed the advice 
> >on yaffs list and you have enabled YAFFS_USE_NANDECC and disabled 
> >YAFFS_USE_OLD_MTD.
> >
> >Then I can only guess, that you did not select a ecc mode in your board driver 
> >code. 
> >
> ><SNIP>
> >	/* 20 us command delay time */
> >	this->chip_delay = 20;		
> >	this->eccmode = NAND_ECC_SOFT;
> ><SNIP>
> >
> >NAND_ECC_SOFT is the right choice, if you don't have a hardware ecc generator.
> >If you have one, you must supply the neccecary functions to use it.
> >
> >  
> >
> this->eccmode is indeed set to NAND_ECC_SOFT.
> I guess my case is kind of 'extra-tricky'. I just found out another 
> weird thing,
> that the warning messages complaining '...without ECC...' do NOT appear when
> I'm 'writing' on the chip. Strange, eh. :'(
> 
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/