Fw: rootfs as JFFS2 on AT91SAM9260

["Ulf Samuelsson" <ulf@xxxxxxxxx>]

I have never set those parameters, when I created the JFFS2 system.
Maybe you shouldn't do that either...    I.E set PHYSMAP to no.

Create a directory structure containing your root file systems
and then run mkfs.jffs2 on that according to Michels advice.

I automate this by using Buildroot...


Best Regards
Ulf Samuelsson                ulf@xxxxxxxxx
Atmel Nordic AB
Mail:  Box 2033, 174 02 Sundbyberg, Sweden
Visit:  Kavallerivägen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22     Fax +46 (8) 441 54 29
GSM    +46 (706) 22 44 57

Technical support when I am not available:
AT90 AVR Applications Group: mailto:avr@xxxxxxxxx
AT91 ARM Applications Group: mailto:at91support@xxxxxxxxx
AVR32 Applications Group        mailto:avr32@xxxxxxxxx
http://www.avrfreaks.net/;            http://avr32linux.org/
http://www.at91.com/ ;                ftp://at91dist:distrib@xxxxxxxxxxxxx/
----- Original Message ----- 
From: "Nicolas Brouard" <nicolas.brouard@xxxxxxxxxxx>
To: <linux-arm@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, April 05, 2007 9:43 PM
Subject: Re: rootfs as JFFS2 on AT91SAM9260


> Thank you Ulf and Michel. I tried to follow your advices but I think I need
> some help again. 
> 
> I use the "experimental linux project" patches and the following
> linux kernel configuration:
> CONFIG_MTD_PHYSMAP=y
> CONFIG_MTD_PHYSMAP_START=0xD0300000
> CONFIG_MTD_PHYSMAP_LEN=0x54000
> CONFIG_MTD_PHYSMAP_BANKWIDTH=1
> The entire configuration file is here: http://nbrouard.free.fr/.config2
> I didn't know how to map /dev/mtdx and /dev/mtdblockx to a physical 
> address. 
> 
> When I boot my kernel with rootfs in RAM (ext2) and try flash_info on 
> flash devices, only /dev/mtd0 and /dev/mtd1 works without error:
> 
>    / $ flash_info /dev/mtd0
>    MTD_open
>    MTD_ioctl
>    Device /dMTD_close
>    ev/mtd0 has 0 erase regions
>    / $ flash_info /dev/mtd1
>    MTD_open
>    MTD_ioctl
>    Device /dMTD_close
>    ev/mtd1 has 0 erase regions
>    / $ flash_info /dev/mtd2
>    MTD_open
>    File open error
>    / $ flash_info /dev/mtd3
>    MTD_open
>    File open error
>    / $ flash_info /dev/mtdblock0
>    mtdblock_open
>    ok
>    mtdblock_release
>    ok
>    / $ flash_info /dev/mtdblock1
>    mtdblock_open
>    ok
>    mtdblock_release
>    ok
>    / $ flash_info /dev/mtdblock2
>    File open error
>    / $ flash_info /dev/mtdblock3
>    File open error
> 
> Then, when I flash rootfs.arm.jffs2 at 0xD0300000 with SAM-BA.exe and boot 
> the linux kernel with the following arguments:
> mem=64M console=ttyS0,115200 root=/dev/mtdblock0 rw rootfstype=jffs2 debug
> I obtain the error:
> 
>  jffs2_get_sb(): dev_name "/dev/root"
>  jffs2_get_sb(): path_lookup() returned 0, inode c3c85070
>  jffs2_get_sb_mtd(): New superblock for device 0 ("physmap-flash.0")
>  jffs2: Too few erase blocks (1)
>  No filesystem could mount root, tried:  jffs2
>  Kernel panic - not syncing: VFS: Unable to mount root fs on
>  unknown-block(31,0)
> 
> The entire output is here: http://nbrouard.free.fr/output2
> 
> What is wrong in my configuration?
> If someone could give me some help...
> 
> Nicolas Brouard
> 
> 
> 
> -------------------------------------------------------------------
> List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
> FAQ:        http://www.arm.linux.org.uk/mailinglists/faq.php
> Etiquette:  http://www.arm.linux.org.uk/mailinglists/etiquette.php
>

-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
FAQ:        http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette:  http://www.arm.linux.org.uk/mailinglists/etiquette.php