Re: [Yaffs] How to partition a Nandsim?

Bounlith,

    From what I remember (this was several months ago) I believe the
options you've specified are correct. I don't know about the nonstandard
OOB size you're dealing with, as I had no such problem. I did need to
set up the mtd devices to match the partition sizes from the device I
dumped the filesystems from though. As you have to specify the total
size of the nandsim device in powers of 2, I just set up 7 partitions
rather than 6, and didn't worry about the size of the last one, as I
wasn't using it.
        John

-----Original Message-----
From: yaffs-bounces@lists.aleph1.co.uk
[mailto:yaffs-bounces@lists.aleph1.co.uk] On Behalf Of Bounlith Sirivong
Sent: Friday, October 08, 2010 3:55 AM
To: Charles Manning
Cc: yaffs@lists.aleph1.co.uk
Subject: Re: [Yaffs] How to partition a Nandsim?

On Fri, 8 Oct 2010 08:18:47 +1300
Charles Manning <manningc2@actrix.gen.nz> wrote:

> On Friday 08 October 2010 04:57:10 Bounlith Sirivong wrote:
> > On Thu, 7 Oct 2010 16:25:02 +0200
> >
>
> When you did the nandwrite did you include the argument to write spare
bytes?

I use these arguments:
nandwrite -a -o /dev/mtd0 dump.img

Is it right?

> Also, I wonder if perhaps there is a problem due to the checkpoint not

> matching the nandsim. Try mounting with the option to ignore
checkpoints.
>
> mount -t yaffs2 -o"no-checkpoint-read" /dev/mtdblock0 /mnt
>
> -- Charles
>

I just try this -o "no-checkpoint-read", but it changes nothing.

When dumping the original NAND with nanddump, the write size and oob
size were detected as 2048 and 56 respectively. The 56 OOB size is not
conventional. This is why I modify the source code of nanddump to
overwrite the OOB size to 64. Perhaps is it this point which is my
issue. What do you think about this?

Bounlith.

_______________________________________________
yaffs mailing list
yaffs@lists.aleph1.co.uk
http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs