• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 305 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.

OMAP3530 shared file system problem

Seydi Kacmaz
Prodigy 150 points

Hi everyone;

i am working on OMAP 35x Evaluation Board. ı couldn't connect host computer and evm using ethernet connection via router. Therefore, i couldn't access my programs in workdir/filesys directory. I assigned static ip on host computer. And I entered command setenv bootargs_nfs 'console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs
nfsroot=192.148.1.110:/home/dsplab1/workdir/filesys,nolock mem=99M mpurate=600 omapfb.rotate=1 omapfb.rotate_type=1
omap_vout.vid1_static_vrfb_alloc=y' and saveenv via Rs232 on evm. But when ı boot evm, ı get following. How should ı do?

Thanks for advance

<6>net eth0: SMSC911x/921x identified at 0xc685c000, IRQ: 336
net eth0: SMSC911x/921x identified at 0xc685c000, IRQ: 336
<5>Sending DHCP requests .Sending DHCP requests ...,, OK
 OK
IP-Config: Got DHCP answer from 192.168.2.1, IP-Config: Got DHCP answer from 192
.168.2.1, my address is 192.168.2.4
my address is 192.168.2.4
IP-Config: Complete:IP-Config: Complete:
     device=eth0
     device=eth0, addr=192.168.2.4, addr=192.168.2.4, mask=255.255.255.0, mask=2
55.255.255.0, gw=192.168.2.1, gw=192.168.2.1,
     host=192.168.2.4, domain=Belkin, nis-domain=(none),
     host=192.168.2.4, domain=Belkin, nis-domain=(none),
     bootserver=192.168.2.1,
     bootserver=192.168.2.1, rootserver=192.168.1.110, rootserver=192.168.1.110,
 rootpath=, rootpath=

<5>Looking up port of RPC 100003/2 on 192.168.1.110
Looking up port of RPC 100003/2 on 192.168.1.110
<5>rpcbind: server 192.168.1.110 not responding, timed out
rpcbind: server 192.168.1.110 not responding, timed out
<3>Root-NFS: Unable to get nfsd port number from server, using default
Root-NFS: Unable to get nfsd port number from server, using default
<5>Looking up port of RPC 100005/1 on 192.168.1.110
Looking up port of RPC 100005/1 on 192.168.1.110
<5>rpcbind: server 192.168.1.110 not responding, timed out
rpcbind: server 192.168.1.110 not responding, timed out
<3>Root-NFS: Unable to get mountd port number from server, using default
Root-NFS: Unable to get mountd port number from server, using default
<3>Root-NFS: Server returned error -5 while mounting /home/dsplab1/workdir/files
ys
Root-NFS: Server returned error -5 while mounting /home/dsplab1/workdir/filesys
<3>VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0)
VFS: Cannot open root device "nfs" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
Please append a correct "root=" boot option; here are the available partitions:
1f00             512 mtdblock01f00             512 mtdblock0 (driver?)
 (driver?)
1f01            1792 mtdblock11f01            1792 mtdblock1 (driver?)
 (driver?)
1f02             256 mtdblock21f02             256 mtdblock2 (driver?)
 (driver?)
1f03            5120 mtdblock31f03            5120 mtdblock3 (driver?)
 (driver?)
1f04          254464 mtdblock41f04          254464 mtdblock4 (driver?)
 (driver?)
<0>Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0
)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

 

  • 0
    Prodigy 150 points

    I found the problem on my own while searching, i share.

    I changed router configurations, for example ip of router(192.168.1.1) and dhcp range (192.168.1.2-192.168.1.254)

    and also used static ip for my host computer (ip: 192.168.1.110, mask: 255.255.255.0, default gateway:192.168.1.1)

    and again terminal in my host computer I made /etc/init.d/network restart and /sbin/service nfs restart.

    Finally after modifying bootargs on target environment according to 

    setenv bootargs_nfs 'console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=192.168.1.110:/home/seydi/workdir/filesys,nolock mem=99M mpurate=600 omapfb.rotate=1 omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y'

    saveenv

    The problem is solved...