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.

How to boot the Kernel without NFS support?

I am trying to boot the DM365 EVM Linux Kernel (MontaVista) without requiring to have access to a NFS server.

To clarify, I have a working program that I already transfered to the board in the /home directory. I want to run in an environment w/o NFS support (DHCP OK). My problem is that the Linux kernel is only happy if I have a valid NFS server on the network. I assume that I have to change the root=/dev/nfs in the bootargs variable to something different... I would appreciate if someone can give me the full bootargs line that would allow me to do that. Hopefully this can be done w/o recompiling the kernel but I will do it if needed.

Thanks in advance,

Joe

 

  • you need to set up a root filesystem somewhere; be it on an SD card or in flash; then set the root in your kernel command line to wherever you put your root filesystem. make sure you also set your rootfstype to ext3 or whatever filesystem you choose to use. good luck!

     

    -Woody

  • I'm using dvsdk_4_00_00_22.  In the bin directory is a script for setting up the u-boot environment for booting up based on your preferences.  If you look at the script you can see the parameters that are generated for booting off the nand flash (as an example).  You can also just run the script, answer the questions, and it will generate the file to send to u-boot to setup the environment.  Of course you are going to need to put the RFS and kernal on the nand.  That's another subject.

    No need to recompile the kernel.

    John A

  • I hope any of you an help me with a problem I am having along the line of this thread: I have an application that runs as intended under the development NFS filesystem on the host.  Running like this I can SSH to my board successfully.  Now I need to flash this to NAND and am at the stage where I used the demo filesystem from PSP_02_10_00_14 ( I am using DVSDK_2_10_01_18 on evmdm365) and put it into a ramdisk of which I can boot and autorun now booting via tftp from the host still - flashing to NAND will be the last step in quest.  My problem with this filesystem is that I can not SSH to the target anymore.  How do I configure it to support SSH?  I have tried to copy from my development filesystem files I think/assume would be needed to enable SSH daemon like rc.d stuff, any ssh script or executable or text configuration file but still can't get to either telnet or ssh to my target.  Any help with this would be much appreciated.

    Thanks, Jinh T.

  • Jinh

    I just responded to the other thread where you have asked this question.

  • John Anderson said:

    I'm using dvsdk_4_00_00_22.  In the bin directory is a script for setting up the u-boot environment for booting up based on your preferences.  If you look at the script you can see the parameters that are generated for booting off the nand flash (as an example).  You can also just run the script, answer the questions, and it will generate the file to send to u-boot to setup the environment.  Of course you are going to need to put the RFS and kernal on the nand.  That's another subject.

    No need to recompile the kernel.

    John A

    John,

    Thanks that's a good start (except for the fact that  dvsdk_4 is huge!).

    Joe

  • Is your concern that the root file system is too large?  I can put it on a 512MB nand.  There are some large media files on it that can be deleted.  Also there is a really small RFS included that you can use.

    John A

  • Here's a file I send to u-boot to set up for nand boot... The green parts are boot kernel and mount RFS from nand.

    setenv bootcmd 'nboot 0x80700000 0 0x400000;bootm'
    setenv bootargs console=ttyS0,115200n8 rw mem=48M video=davincifb:vid0=OFF:vid1=OFF:osd0=720x576x16,4050K dm365_imp.oper_mode=0 davinci_capture.device_type=4 davinci_display.cont2_bufsize=6291456 vpfe_capture.cont_bufoffset=6291456 vpfe_capture.cont_bufsize=6291456 ip=192.168.1.5:::255.255.240.0:vcxnexus:eth0:off root=/dev/mtdblock3 rootfstype=jffs2 rw rootwait