Hi,
I am currently working on OMAPL137 EVM board.
I would like to use JFFS2 image file system for Linux kernel boot up. Can anyone provide me steps or procedure of how to use JFFS2 image as the root file system from the scratch.
Regards
Jitendra
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
I am currently working on OMAPL137 EVM board.
I would like to use JFFS2 image file system for Linux kernel boot up. Can anyone provide me steps or procedure of how to use JFFS2 image as the root file system from the scratch.
Regards
Jitendra
Hi,
Jitendra Jagasia said:
I am currently working on OMAPL137 EVM board.
I would like to use JFFS2 image file system for Linux kernel boot up. Can anyone provide me steps or procedure of how to use JFFS2 image as the root file system from the scratch.
Hope this helps
Regards
Gururaja
Hi Gururaja,
Thanks for you reply.
I had tried the above given procedure but it gives me the following errors
jffs2_scan_eraseblock () : Magic bitmask 0x1985 not found at 0x0037c024: 0x6373 instead
JFFS2 warning: (1) jffs2_do_read_inode_internal : Truncating ino #392 to 23300 bytes failed because it only had 20480 bytes to start with!
JFFS2 warning: (1) jffs2_do_read_inode_internal : Truncating ino #328 to 113552 bytes failed because it only had 110592 bytes to start with!
Kernel panic - not syncing: No init found. Try passing init= option to kernel .
I have copied the jffs2 filesystem image in the SPI0 flash of the EVM OMAPl137 board.
using flashcp <image dir>/rootfs.jffs2 /dev/mtd2 command in the mtdblock2.
Can you provide the solution on how to solve the above given issue.
Regards
Jitendra
Hi,
Jitendra Jagasia said:jffs2_scan_eraseblock () : Magic bitmask 0x1985 not found at 0x0037c024: 0x6373 instead
JFFS2 warning: (1) jffs2_do_read_inode_internal : Truncating ino #392 to 23300 bytes failed because it only had 20480 bytes to start with!
JFFS2 warning: (1) jffs2_do_read_inode_internal : Truncating ino #328 to 113552 bytes failed because it only had 110592 bytes to start with!
Kernel panic - not syncing: No init found. Try passing init= option to kernel .
"jffs2_scan_eraseblock () : Magic bitmask 0x1985 not found at ...."
this error (as per google) normally occurs because of incorrect erase_size settings for jffs2. Did you check that the flash geometry (page size / erase size) match the
flash device on your board?. Make sure the flash partition size match the actual image size (u-boot/kernel jfss2 image)
also, erase the SPI flash once before copying any data to spi flash. use erase option from u-boot or "flash_eraseall -j /dev/mtd3" from linux
Regards
Gururaja
Hi Gururaja,
The Flash have three partition as shown below
dev size erase size name
mtd0 00040000 00001000 U-Boot
mtd1 00004000 00001000 U-Boot Env
mtd2 003bc000 00001000 Linux
The JFFS2 root file system is of 0x380000 bytes.
The JFFS2 root file system image is put in the mtd2 partition which is of bigger size than the file system image.
Before copying the JFFS2 root file system image to the mtdblock2 I erased the mtd2 partition using flash_eraseall command.
I copied the JFFS2 root file system image into the SPI0 Flash of the EVM OMAPL137 board
I have followed all the steps given in the Link.
But even after that i was getting error like ' Kernel Panic - No init found'
But I modified my bootargs as follows ' setenv bootargs mem=32M console=/dev/ttyS2,115200n8 root=/dev/mtdblock2 rw rootfstype=jffs2 init=/linuxrc '
But after that I am getting following error
request_module: runaway loop modprobe binfmt-0000
request_module: runaway loop modprobe binfmt-0000
request_module: runaway loop modprobe binfmt-0000
request_module: runaway loop modprobe binfmt-0000
Can you guide me how to solve the issue.
Thanks & Regards
Jitendra
Hello, Gururaja.
I have attempted on OMAP-L138 with NAND,
but /dev/mtd# are not found.
and "cat /proc/mtd" also output empty items.
Could you show me the way?
my step ~~~~~~~~~~~~~~~~~~~~~~~~
1. kernel compile(NAND MTD)
2. boot(tftp:uImage, nfs:filesys)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/dev/mtd0 and /dev/mtdblock0 are made by mannally?
Hello, Gururaja
My boot log is as follows:
OMAP-L138 initialization passed!
I2C: ready Hit any key to stop autoboot: 0 Environment size: 420/131068 bytes Starting kernel ... Uncompressing Linux... done, booting the kernel. _____ _____ _ _ Arago Project http://arago-project.org arago ttyS2 Arago 2010.11 arago ttyS2 arago login: root |
Nand memory is OMAP-L138EVM "MT29F4G08AACWC".
I'm sure that I built the kernel base on the jffs2 ti-wiki.
best regards
Seyoung
Hi,
can you try configuring linux with below options and then show the kernel log
CONFIG_MTD_DEBUG=y
CONFIG_MTD_DEBUG_VERBOSE=3
CONFIG_MTD_CONCAT=y
regards
Gururaja
Thank you for your answer.
but, NAND partition is still not configured.
( compared previous, no more log about NAND)
When I tested released prebuilt-uImage(03.20.00.14), spi memory log was found on boot.
so I have thought this problem is on kernel.
Bytes transferred = 2113796 (204104 hex) Starting kernel ... Uncompressing Linux... done, booting the kernel. |
I attatch my uImage. 8407.uImage.gz
best regards
Seyoung
0702.JFFS2 Log file.docHi Gururaja,
I have attached my SPI 0 JFFS2 as root file system log file7080.JFFS2 Log file.doc.
Please just go through the Log file & provide us suggestion on how to solve the above problem that we are facing.
Thanks & Regards
Jitendra
Hi,
Can I use SPI0 Flash to store JFFS2 file system & Can I directly execute my root file system from SPI0 Flash.
Thanks & Regards
Jitendra
Hi,
I absolutly agree that using SPI0 Flash will be work.
However my customized OMAP-L138 board is only remained NAND boot side.
So I'm considering whether it changes to SPI or not?
SPI jffs2 boot-speed is not slow?
Thank you for your concern.
Best regards
Seyoung