LeopardBoard DM355 with RR SDK - NFS will not work

LeopardBoard DM355 with RR SDK - NFS will not work

  • I have problem to get NFS working on my Leopard 355 board with RR SDK version 840402. I have follow the instruction "TMS320DM355 DVEVM v2.0
      Getting Started Guide" (SPRUF73C).

    And I set my uboot as the following:

    setenv nfshost 192.168.1.72
    setenv rootpath /home/kqchen/workdir/filesys
    setenv bootargs console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/home/kqchen/workdir/filesys nfsroot=$(nfshost):$(rootpath),nolock mem=116M video=davincifb:vid0=0,2500K:vid1=0,2500K: osd0=720x576x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=$(videostd)

    Here is the error message when I try to get NFS:

    eth0: link down                                                                           
    [42949376.100000] Sending DHCP requests .<6>eth0: link up, 100Mbps, full-duplex, lpa 0x41E1                 
    [42949378.400000] ., OK                                                                                     
    [42949381.100000] IP-Config: Got DHCP answer from 192.168.1.254, my address is 192.168.1.103                
    [42949381.100000] IP-Config: Complete:                                                                      
    [42949381.110000]      device=eth0, addr=192.168.1.103, mask=255.255.255.0, gw=192.168.1.254,               
    [42949381.120000]      host=192.168.1.103, domain=gateway.2wire.net, nis-domain=(none),                     
    [42949381.120000]      bootserver=192.168.1.254, rootserver=192.168.1.254, rootpath=                        
    [42949381.130000] Looking up port of RPC 100003/2 on 192.168.1.254                                          
    [42949411.140000] rpcbind: server 192.168.1.254 not responding, timed out                                   
    [42949411.140000] Root-NFS: Unable to get nfsd port number from server, using default                       
    [42949411.150000] Looking up port of RPC 100005/1 on 192.168.1.254                                          
    [42949441.160000] rpcbind: server 192.168.1.254 not responding, timed out                                   
    [42949441.160000] Root-NFS: Unable to get mountd port number from server, using default                     
    [42949471.170000] Root-NFS: Server returned error -5 while mounting /tftpboot/$(nfshost):$(rootpath)        
    [42949471.170000] VFS: Unable to mount root fs via NFS, trying floppy.                                      
    [42949471.180000] VFS: Cannot open root device "/home/kqchen/workdir/filesys" or unknown-block(2,0)         
    [42949471.190000] Please append a correct "root=" boot option; here are the available partitions:           
    [42949471.200000] 1f00          524288 mtdblock0 (driver?)                                                  
    [42949471.210000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)         

    Kevin

  • As I recall, uboot likes to be completely different, so they use ${} instead of $()

  • Yes, looks like there is improvement, but still not through:

    eth0: link down                                                                            

    [42949376.100000] Sending DHCP requests .<6>eth0: link up, 100Mbps, full-duplex, lpa 0x41E1                  

    [42949378.400000] ., OK                                                                                      

    [42949381.730000] IP-Config: Got DHCP answer from 192.168.1.254, my address is 192.168.1.105                

    [42949381.730000] IP-Config: Complete:                                                                      

    [42949381.740000]      device=eth0, addr=192.168.1.105, mask=255.255.255.0, gw=192.168.1.254,                

    [42949381.750000]      host=192.168.1.105, domain=gateway.2wire.net, nis-domain=(none),                      

    [42949381.750000]      bootserver=192.168.1.254, rootserver=192.168.1.72, rootpath=                          

    [42949381.760000] Looking up port of RPC 100003/2 on 192.168.1.72                                            

    [42949381.780000] Looking up port of RPC 100005/1 on 192.168.1.72                                            

    [42949381.830000] VFS: Mounted root (nfs filesystem) on device 0:12.                                        

    [42949381.840000] Freeing init memory: 116K                                                                  

    [42949381.840000] Warning: unable to open an initial console.                                                

    [42949381.850000] Kernel panic - not syncing: No init found.  Try passing init= option to kernel.  

  • [42949381.750000]      bootserver=192.168.1.254, rootserver=192.168.1.72, rootpath=                          

    Notice your rootpath is blank - that is not what you want.

    When the kernel first starts booting, you can see the kernel command line being used.  Please verify it is correct or include it in your information you are providing when asking for help.

  • Hi,

    In my first e-mail, I have indicated that I did:

    setenv rootpath /home/kqchen/workdir/filesys.

    And I just did printenv and see (partial):

    ......

    nfshost=192.168.1.72                                                                                        

    rootpath=/home/kqchen/workdir/filesys                                                                        

    ......

    So I am not sure why it is missing during the boot  process...

  • Another way to ask question will be how do I know my "setenv bootargs" is syntax correct? Where is the place to find info?

  • Hi sjcoder,

    Have you seen this link?

    processors.wiki.ti.com/.../Installing_RR_free_SDK_for_Leopard_Board

    Also, if you do "make install" the SDK will automatically set the correct bootargs, search for it in that link.

    You will see that it set something similar to

    setenv bootargs console=ttyS0,115200n8 video=davincifb:osd1=0x0x8 mem=116M root=/dev/nfs nfsroot=192.168.0.100:/home/miguel/DM355SDK786811/fs/fs rw ip=192.168.0.101:::255.255.255.0::eth0 mtdparts=nand_davinci.0:4096k(UBOOT),128k(UBOOT_ENV),3200k(KERNEL),20480k(FS)

    Regards;

    Maria

  • hi all

    i am also getting similar error while booting my leo 365 board .here is the output

    Clocks: disable unused rto

    Clocks: disable unused mjcp

    davinci_emac_probe: using random MAC addr: 86:41:aa:88:be:af

    emac-mii: probed

    IP-Config: Complete:

        device=eth0, addr=192.168.1.101, mask=255.255.255.0, gw=255.255.255.255,

        host=192.168.1.101, domain=, nis-domain=(none),

        bootserver=255.255.255.255, rootserver=192.168.1.25, rootpath=

    Looking up port of RPC 100003/2 on 192.168.1.25

    rpcbind: server 192.168.1.25 not responding, timed out

    Root-NFS: Unable to get nfsd port number from server, using default

    Looking up port of RPC 100005/1 on 192.168.1.25

    rpcbind: server 192.168.1.25 not responding, timed out

    Root-NFS: Unable to get mountd port number from server, using default

    i have followed the boot args as explained above but still i cannot be able to boot the device.

    somebody please help

    its very urget , am stuck with hello world for past 3 weeks

    thanks in advance

    Arjun