Hi Charles

Thanks for your quick response.

I enabled all the traces and here is what I get

when I mount the empty partition I get

................many prints............

nandmtd2_QueryNANDBlock 510

nandmtd2_ReadChunkWithTagsFromNAND chunk 32640 data 00000000 tags c0403c4c packetd tags obj -l chunk -1 byte -1 seq -1

ext.tags eccres 0 blkbad 0 chused 0 obj 0 chunk 0 byte 0 del 0 ser 0 seq 0

Block scanning block 510 state 3 seq 0

block empty

...................same for other blocks...................

Now I try to create a file and save it

I get error like "yaffs tragedy:attempt to put data chunk into a non-file"

Also it gets ecc in negative.

Is there a way to fix ecc and oob errors?

Any pointers would be highly appreciated.

regards,

shivas

Charles Manning <manningc2@actrix.gen.nz> wrote:

On Thursday 21 December 2006 11:43, Shiva Shankar wrote:
> Hi Charles,
> Thanks for your response.
>
> As per your suggestion I tried with empty partition.
>
> I mounted a partition as
>
> mount -t yaffs2 /dev/mtdblock1 /mnt1
>
> then created a file using "vi" and put some contents in it.
>
> After this I save the file and then umount /mnt1
>
> When I try to mount again I get messages as "Partially written block 1
> being set for retirement"
>
> When I looked in to the code I found that it is complaining because it
> thinks the block was retired in between. As I am new to yaffs2 I cannot
> understand what might be the issue.

As with almost all yaffs problems, it would appear that you're getting some
sort of oob corruption which makes it look like your writes are failing.

I suggest that you erase flash then rerun with all yaffs tracing turned on.

Somewhere in tracing you're likely to see some reports of tags/ecc errors.

>
> Any help/pointers in this regard would be highly appreciated.
>
> regards,
> shivas
>
> Charles Manning wrote:
>
> On Thursday 21 December 2006 09:38, Shiva Shankar wrote:
> > Hi All,
> >
> > I am working on kernel 2.6.14.3. I could successfully include the YAFFS
> > in to my kernel.
> >
> > I created a yaffs2.img file using the command
> >
> > "mkyaffs2image /my_dir yaffs2.img"
> >
> > after this I erased the flash using
> > "flash_eraseall /dev/mtd1"
> >
> > After this I used nand write to write the yaffs2.img to /dev/mtd1
> >
> > nandwrite -a -p /dev/mtd1 /yaffs2.img
> >
> > after this I mount the flash partition
> >
> > mount -t yaffs2 /dev/mtdblock1 /mnt1
> >
> > and do a 'ls'
> >
> > ls /mnt1
> > to see only lost+found
> >
> > I then create a file using vi and edit the file
> >
> > I do an "ls" i can see the file and its contents. I "umount" the
> > partition and mount again I again see only lost + found
> >
> > If I do a nanddump I can see the contents of all the files that I had
> > written!!!
> >
> > Can anyone give me some pointers I have reached a dead end.
>
> the mkyaffsimage process does not work correctly at presents for yaffs2.
> This is mainly due to the hassles trying to get the oob data to flow
> correctly through the process.
>
> I suggest you first try get going starting from an empty partition.
>
> -- Charles
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com