[Yaffs-archive] Re: cannot see files in yaffs image

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Nick Bane
Date:  
To: Skumar, yaffs
Subject: [Yaffs-archive] Re: cannot see files in yaffs image
Sharath

If you are writing raw image data to the mtd device via the standard mtd
driver then it wont work for two reasons

1) The image data contains oob data as well as "normal" mtd data.
2) It is not clear if you are writing to block 0 on the device. If so, be
aware that yaffs skips this block.

There was a mooted a while back for a utility to write images to nand mtd
devices but I don't think anything has happened. I am too busy right now but
I may get round to it later.

To do this, I modifies the bootloader and wrote the data directly to the
nand chip.

Nick Bane

----- Original Message -----
From: "Skumar" <>
To: <>
Sent: Friday, January 03, 2003 9:37 AM
Subject: cannot see files in yaffs image


i have put the yaffs.image in the ramdisk, booted linux on board & run the
following

Mistral
Linux login: root
[root@Linux /root]$ls
dialogue.mp3   Hello_448.pcm  sound_arm      record         testioctl
yaffs.image
[root@Linux /root]$cp yaffs.image /dev/mtd7
MTD_open


MTD_write

MTD_write

MTD_write

MTD_write

MTD_write

MTD_write

MTD_close

[root@Linux /root]$cd ..
[root@Linux /]$mount -t yaffs /dev/mtdblock7 tmp
yaffs: dev is 7943 name is "1f:07"

yaffs_read_super: MTD block size 4096

yaffs: Attempting MTD mount on 31.7, "1f:07"

erase c00b2ac0

read c00b2748

write c00b2898

readoob c00b27f0

writeoob c00b2950

oobblock 200

oobsize 10

yaffs_read_super: guts initialised

yaffs_read_super: got root inode

yaffs_read_super: d_alloc_root done

yaffs_read_super: done

[root@Linux /]$cd tmp
[root@Linux /tmp]$ls
yaffs_readdir: starting at 0

yaffs_readdir: starting at 3

yaffs_readdir: starting at 0

yaffs_readdir: starting at 3

lost+found
[root@Linux /tmp]$
[root@Linux /tmp]$ls -la
yaffs_readdir: starting at 0

yaffs_readdir: starting at 3

yaffs_readdir: starting at 0

drw-rw-rw-    1 root     root         512 Jan  1 00:01 .
drwxr-yar-x   14      5f0      500    1f24 Aug  7  2002 ..
s_readdir: starting at 3


drw-rw-rw-    1 root     root         512 Jan  1 00:01 lost+found


as you can see when i do ls i cannot any of the files except lost+found
why is it like this?
Regards
sharath




---------------------------------------------------------------------------------------
This mailing list is hosted by Toby Churchill open software (www.toby-churchill.org).
If mailing list membership is no longer wanted you can remove yourself from the list by
sending an email to with the text "unsubscribe"
(without the quotes) as the subject.