[Buildroot] [Fwd: Re: Problem with jffs2 image creation.]
I use the default configuration : make at91sam9260dfc_defconfig
By default buildroot build 2 images, ext2 and jffs2, I have not changed any option in menuconfig :
[nlc at nlcLaptop buildroot]$ ls -l binaries/at91sam9260dfc/ total 15444
-rwxr-xr-x 1 nlc nlc 3708 2008-12-02 14:49
at91sam9260dfc-dataflashcardboot-2.3.4.bin*
-rw-r--r-- 1 nlc nlc 1622380 2008-12-02 14:49 at91sam9260dfc-linux-2.6.24.4-20081202.gz
-rwxr-xr-x 1 nlc nlc 167300 2008-12-02 14:49 at91sam9260dfc-u-boot-1.2.0-atmel-20081202.bin*
-rw-r--r-- 1 nlc nlc 483 2008-12-02 14:49 autoscript
-rw-r--r-- 1 nlc nlc 555 2008-12-02 14:49 autoscript.at91sam9260dfc
-rw-r--r-- 1 nlc nlc 9576448 2008-12-02 14:49 rootfs.arm-20081202.ext2 -rw-r--r-- 1 nlc nlc 4392688 2008-12-02 14:50 rootfs.arm-20081202.jffs2
If I mount the ext2 image on my laptop everything is OK (devices are presents in /dev), and the image works fine when I put it in the board. But when I mount the jffs2 image on my laptop, /dev, and even /etc are empty ! And of course the image doesn't work on the board. ext2 and jffs2 images seems to not be generated with the same tool. I think there is a problem with the mkfs.jffs2 tool ?
Quoted 13 lines
I am new to the list. I built a custom electronic board based on an
atmel AT91SAM9260 processor.
I successfully finished a complete buildroot build, but I have a problem.
The generated jffs2 image of the root filesystem is incorrect, in fact
the dev directory is not populated, thus I have this message after the
linux kernel has mounted the filesystem : "Unable to open an initial
console"
Quoted 4 lines
I tried the ext2 image in my board, it works correctly. But I absolutely
need to use jffs2 because my filesystem is in a Nand flash.
You mean when you use an ext2 image (just changing from buildroot config) they create necessary files on /dev?
Send your config file.
--
Tiago Maluta.
I found something !
I looked in detail the build procedure, and I see that before mkdev.jffs2 is called with the -D device_table.txt option, makedevs is called !
Thus /dev/ directory is already populated, and mkdev.jffs2 doesn't work correctly !
I edited the script target/jffs2/jffs2root.mk and commented this line :
#JFFS2_OPTS += -D $(TARGET_DEVICE_TABLE)
Thus now mkfs.jffs2 is called without the device_table.txt, and the image is built correctly because /dev is already populated by makedevs.
Cyril HAENEL a ?crit :
Quoted 27 lines
I use the default configuration : make
at91sam9260dfc_defconfigBy default buildroot build 2 images, ext2 and jffs2, I have not changed any option in menuconfig :
[nlc at nlcLaptop buildroot]$ ls -l binaries/at91sam9260dfc/ total 15444
-rwxr-xr-x 1 nlc nlc 3708 2008-12-02 14:49
at91sam9260dfc-dataflashcardboot-2.3.4.bin* -rw-r--r-- 1 nlc nlc 1622380 2008-12-02 14:49 at91sam9260dfc-linux-2.6.24.4-20081202.gz -rwxr-xr-x 1 nlc nlc 167300 2008-12-02 14:49 at91sam9260dfc-u-boot-1.2.0-atmel-20081202.bin*(quoted diff) +0
-4-rw-r--r-- 1 nlc nlc 483 2008-12-02 14:49 autoscript -rw-r--r-- 1 nlc nlc 555 2008-12-02 14:49 autoscript.at91sam9260dfc -rw-r--r-- 1 nlc nlc 9576448 2008-12-02 14:49 rootfs.arm-20081202.ext2 -rw-r--r-- 1 nlc nlc 4392688 2008-12-02 14:50 rootfs.arm-20081202.jffs2If I mount the ext2 image on my laptop everything is OK (devices are presents in /dev), and the image works fine when I put it in the board. But when I mount the jffs2 image on my laptop, /dev, and even /etc are empty ! And of course the image doesn't work on the board. ext2 and jffs2 images seems to not be generated with the same tool. I think there is a problem with the mkfs.jffs2 tool ?
Signature · 2 lines
Cyril Haenel Registered Linux User #332632