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.

Problem when making copy to NFS shared directory

Hello

I have just started installing the software for the DM6446 but have run into a problem when I try to get the NFS up and running.  Everything worked perfectly up untill section 4.3.7 # 4 (using GSGv2 and all the latest software from the TI site, running in a SUSE 10.3 Virtual Machine).  When I execute the cp command, all seems to work well.  BUT, then when I run almost any command after that the system comes up with an error like:

-bash: /root/bin/grep: cannot execute binary file          ->  (when I switch users from andre to root using the "su -" command.  The system still seems to switch as the text becomes red)

-bash: /root/bin/ls: cannot execute binary file              -> (When I try to use the ls command)

-bash: /root/bin/chown: cannot execute binary file       -> (When I try the chown command following the cp command in 4.3.7 #4)

There are no files/directories in the /home/andre/workdir/filesys directory, despite the fact that I just copied it over.  This doesn't look right to me!  From what I understand from other threads on this forum, the fact that the copy didn't work well could result in the "cannot execute binary file" error, but I have no idea how fix the problem.

Does anybody have any ideas as to what (or what else) can be wrong?  I've tried installing everything from scratch, and I've tried also tried just restarting Linux, but it didn't help.

 

  • I have seen that message when the binary was built for x86 and one tries to run it on ARM or vice versa.  I assume you are typing 'grep' and 'ls' commands on the host correct?  Can you type 'which grep' or 'which ls" command to see which binary the system is trying to run? 

    Any binary under "/home/andre/workdir/filesys " per GSG should be an ARM binary and not able to run on host.

  • I was able to sort this one out, but why it went wrong is still a mystery.  I made a backup of the VM just before I started with the NFS section, so I could easily fall back and retry things without wasting too much time.  It turned out that the copy command didn't execute well, and the error message was because the files were present.  I tried this twice, without success, and then from the "My computer" GUI, also without success.  Then I tried it one last time from scratch as described in the GSG, and it worked.  I can't recall having changed anything in between, but I probably did something wrong that I don't know of.  In any case, its fixed now... and I'll probably be returning to this forum with another new question shortly...