• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 378 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DM36X IPNC3.0 cannot support cramfs????

Minglei Li
Intellectual 365 points

Hello everyone, I use IPNC 3.0, I can run squashfs successfully, but the cramfs cannot run. I have support cramfs in the kernel by setting CONFIG_CRAMFS=y. The linux command is as follows:

setenv ipaddr 192.168.1.92;setenv serverip 192.168.1.93;setenv bootargs 'rootdelay=2 mem=48M console=ttyS0,115200n8 noinitrd ip=192.168.1.92:192.168.1.92:192.168.1.1:255.255.255.0:Camera:eth0:off ro root=/dev/mtdblock3 rootfstype=cramfs cmemk.phys_start=0x83000000 cmemk.phys_end=0x88000000 cmemk.phys_start_1=0x00001000 cmemk.phys_end_1=0x00008000 cmemk.pools_1=1x28672 cmemk.allowOverlap=1 cmemk.useHeapIfPoolUnavailable=1 lpj=1077248 nohz=off highres=off eth=EE:0C:0C:BE:19:02 loglevel';setenv verify no;saveenv;reset;

The error appearing is :

[ 5.570000] cramfs: empty filesystemVFS: Mounted root (cramfs filesystem) readonly.
[ 5.580000] Freeing init memory: 180K
[ 5.580000] Warning: unable to open an initial console.
[ 5.590000] Kernel panic - not syncing: No init found. Try passing init= option to kernel.

What is wrong? 

The same cramfs file can run successfully in another kernel.

Thank you !

  • 0
    Guru 31670 points

    If you have IPNC 2.6, please check and compare the bootargs parameters for cramfs there. Also see how the cramfs image is made there and follow the same steps here to create the image.

    What are the steps that are followed here for creating the cramfs image? 

  • 0 in reply to Renjith Thomas
    Intellectual 365 points

    Thank yyou for your response! I use the steps following:

    1.Support cramfs in the kernel by configure:CONFIG_CRAMFS=y

    2.make: to make the filesystem

    3.make cramfs to run the following command to make cramfs filesystem:

        ./mkcramfs $(TARGET_FS)/ cramfs_ipnc_$(HARDWARE)

    The bootargs is the same with IPNC2.6. 

    setenv bootargs 'mem=48M console=ttyS0,115200n8 ip=192.168.1.99:192.168.1.99:192.168.1.1:255.255.255.0:::off eth=EE:0C:0C:BE:19:02 root=/dev/mtdblock3 rootfstype=cramfs cmemk.phys_start="0x83000000" cmemk.phys_end="0x88000000" cmemk.phys_start_1="0x00001000" cmemk.phys_end_1="0x00008000" cmemk.pools_1="1x28672" cmemk.allowOverlap="1" quiet';saveenv;reset;

    Have you ever run cramfs successfully in IPNC3.0? Thank you very much!

  • 0 in reply to Minglei Li
    Guru 31670 points

    Li,

    What is the content of $(TARGET_FS)? Is it having one more directory inside? Have you followed the steps exactly same as 2.6? 

    Basically IPNC 3.0 is almost same as IPNC 2.6. So Cramfs should work directly. If this doesn't work, please share the complete boot logs, including the flashing procedure for cramfs image.

  • 0 in reply to Renjith Thomas
    Intellectual 365 points

    Hi Renjith Thomas, 

    I can run squashfs successfully with the same TARGET_FS by the following bootargs:

    setenv ipaddr 192.168.1.99;setenv serverip 192.168.1.93;setenv ethaddr EE:0C:0C:BE:19:02;setenv verify no;saveenv;setenv bootcmd 'nboot 0x80700000 0 0x500000;bootm 0x80700000';setenv bootargs 'mem=48M console=ttyS0,115200n8 ip=192.168.1.99:192.168.1.99:192.168.1.1:255.255.255.0:::off eth=EE:0C:0C:BE:19:02 root=/dev/mtdblock3 rootfstype=squashfs cmemk.phys_start="0x83000000" cmemk.phys_end="0x88000000" cmemk.phys_start_1="0x00001000" cmemk.phys_end_1="0x00008000" cmemk.pools_1="1x28672" cmemk.allowOverlap="1" quiet';saveenv;reset;

    The only difference between the command of cramfs and squashfs is the red contents. 


  • 0 in reply to Minglei Li
    Guru 31670 points

    Li,

    Have you followed the exact cramfs command from 2.6? This is just for re-confirming. Also please attach complete kernel logs as well.