Mounting NAND flash as the root file system

[Jatin Sharma]

Actually, I was mounting the block device but wrote it wrong in the email.

WDS# mount -t jffs2 /dev/mtdblock0 /mnt
mount: mounting /dev/mtdblock0 on /mnt failed

Since the flash_eraseall and nandwrite tools are working on the NAND
device, NAND driver is working fine. Would you agree? I don't have the
nanddump tools on my file system but will include it to make sure NAND
is getting updating after being written by nandwrite.

I am planning to turn on JFFS2 debug in the kernel to see any related
errors. I have the following switches in my .config file:

CONFIG_MTD=y
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLOCK=y
CONFIG_MTD_NAND=y
CONFIG_MTD_NAND_ISPAN=y
CONFIG_JFFS2_FS=y
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_NAND=y

I would appreciate if you could give some direction on where to debug
for mount problems.

Thanks,
Jatin


2009/4/28 Ricard Wanderlof <ricard.wanderlof at axis.com>:
>
> On Mon, 27 Apr 2009, Jatin Sharma wrote:
>
>> When I boot the kernel using ramdisk (FS in RAM), I am able to run the
>> flash_eraseall utility successfully. But the mount command fails:
>>
>> WDS# mount -t jffs2 /dev/mtd0 /mnt
>> mount: mounting /dev/mtd0 on /mnt failed
>
> You should be using the block device - /dev/mtdblock0 - and not the
> character device when mounting.
>
> /Ricard
> --
> Ricard Wolf Wanderlöf                           ricardw(at)axis.com
> Axis Communications AB, Lund, Sweden            www.axis.com
> Phone +46 46 272 2016                           Fax +46 46 13 61 30
>