[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [microblaze-uclinux] how to mount flash via jffs2 as dir /mnt ?



Hi Falk,

Brettschneider Falk wrote:

> After bootup I can read:
>   /> cat /proc/mtd
>   dev:    size   erasesize  name
>   mtd0: 01000000 00010000 "Physically mapped flash"
>   mtd1: 01000000 00010000 "Physically mapped flash"
>   mtd2: 00061000 00001000 "RAM"
> Here it looks like mtd0 and mtd1 is the flash, although the boot log looks
> like
> 
> -------------
> What mtd device is the flash now? I have /dev/mtd0 to /dev/mtd7
>   /> ls -l /dev/mtd*
>   crw-------    1 0        0         90,  15 /dev/mtdr7
>   crw-------    1 0        0         90,  13 /dev/mtdr6
>   crw-------    1 0        0         90,  11 /dev/mtdr5
>   crw-------    1 0        0         90,   9 /dev/mtdr4
>   crw-------    1 0        0         90,   7 /dev/mtdr3
>   crw-------    1 0        0         90,   5 /dev/mtdr2
>   crw-------    1 0        0         90,   3 /dev/mtdr1
>   crw-------    1 0        0         90,   1 /dev/mtdr0
>   brw-------    1 0        0         31,   7 /dev/mtdblock7
>   brw-------    1 0        0         31,   6 /dev/mtdblock6
>   brw-------    1 0        0         31,   5 /dev/mtdblock5
>   brw-------    1 0        0         31,   4 /dev/mtdblock4
>   brw-------    1 0        0         31,   3 /dev/mtdblock3
>   brw-------    1 0        0         31,   2 /dev/mtdblock2
>   brw-------    1 0        0         31,   1 /dev/mtdblock1
>   brw-------    1 0        0         31,   0 /dev/mtdblock0
>   crw-------    1 0        0         90,  14 /dev/mtd7
>   crw-------    1 0        0         90,  12 /dev/mtd6
>   crw-------    1 0        0         90,  10 /dev/mtd5
>   crw-------    1 0        0         90,   8 /dev/mtd4
>   crw-------    1 0        0         90,   6 /dev/mtd3
>   crw-------    1 0        0         90,   4 /dev/mtd2
>   crw-------    1 0        0         90,   2 /dev/mtd1
>   crw-------    1 0        0         90,   0 /dev/mtd0
>   />
> 

MTD provides block and character device interfaces to the partitions -
mtdblockN is the block interface, mtdN is the char interface
> ----------
> Huh? Block device?:
>   /> mount -t jffs2 /dev/mtd3 /mnt
>   mount: Mounting /dev/mtd3 on /mnt failed: Block device required
>   pid 18: failed 256
>   />

You can only mount on block devices, not char.  You probably want

mount -t jffs2 /dev/mtdblock0 /mnt

(mtd3 is your RAM based partition)


> Why does fdisk do such strange things for mtd0 and mtd1 (same output)?
   /> fdisk /dev/mtd0

Again, fdisk works on block devices, not char.

fdisk doesn't really make sense if you are using MTD partitions - just
put the jffs2 filesystem on an MTD partition directly, don't bother with
fdisk.

Cheers,

John

___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/