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.

DM814x Kit RFS missing nfs mount client

Hi,

I used to be developing on the AM3517EVK, but have migrated to the DM814x/AM387x EVK.  First thing I tried to do was mount my NFS server to the EVK and noticed that mount.nfs was not working (I also had to manually udhcpc -i eth3 first, too).

I noticed that many utils are now linked to util.linux.ng.  I also noticed that busybox is still there.  I directly used busybox's mount command and mounted the NFS share successfully.

What's the reason for switching over to util.linux.ng?  Any chance of either (A) including NFS support in the util.linux.ng binary or (B) reverting to busybox?

For now, I will us the busybox mount command instead to work around.

  • Hi,

    Both the EZSDK for DM81xx and the SDK for AM35xx are built using OpenEmbedded. Its possible that the version of the SDK that you had was an older version and the one in the EZSDK uses a newer OE recipe which uses util.linux.ng. Please continue to use busybox.

  • This one works for sharing folder within Ubuntu host to the evm

     

    On Ubuntu:

    mkdir /home/ti814x/nfs-share

     then add this line to /etc/exports as sudo

     /home/ti814x/nfs-share  *(rw,nohide,insecure,no_subtree_check,async,no_root_squash)

     

    On the evm:

     

    cd /home/root

    mkdir nfs-share

    mount -t nfs 192.168.3.116:/home/ti814x/nfs-share nfs-share -o rw,nolock,addr=192.168.3.116

     

     

    Without ipaddr passed in, it won’t mount in the evm. The ip address is of course ubuntu host, which in my case is 192.168.3.116

    RV