After I got the OK2440 Development Board, I got the development board yesterday after connecting to the nfs server. After I clicked it, I found that the LCD was really bad. No money is required. Ke, I entered the topic. Today, I tried to connect to the company's computer with the Development Board to avoid "downloading again & again" and wanted to build an NFS environment. Www.2cto.com has not been completed for a long time. It takes some time today. The specific steps are as follows: 1. because the board has bootloader and the operating system, this step will be skipped. Later I will change the bootloader and I will explain it carefully. host installation (centOS6.2), if there are other versions of linux, but you must have nfs server, gcc, vim, gdb and other development tools, if you are a virtual machine, select a bridge to connect to the network (select a virtual network card), otherwise the Development Board will not be able to connect to the nfs www.2cto.com 3. share files. This step is necessary for VM users, so that they can access windows files (such as cross-compilation tools) on your linux host ). Here I want to talk about it. If vmware tools is not installed, sharing cannot be successful. You can find them online for sharing and installing vmware tools. use a serial port tool, such as a Super Terminal, to bring ok2440 to the linxu system, and use a network cable to connect the development board to the network hole of the host (of course, you can use a router, so that the host will not be affected) 5. run the nfs service on centos: service nfs restart or/etc/init. d/nfs start 6. modify the content to be shared. Run the command vim/etc/exports to add the directory to be shared, such as/home *, this will share everything in the home directory to the server, and the client can access it by connecting to nfs. Of course there are still many parameters, such as ro rw sync, I will not elaborate on it here. It was originally a work record and I don't want to write it like a tutorial... 7. restart nfs www.2cto.com 8 again after configuration. I Run the fconfig command to set the ip address of the host and the development board to the same CIDR block. Then input the "mount-o nolock 192.168.102.250: // mnt/kerwin" colon in the Super Terminal... I spent at least one hour looking for the reason... 9. after the connection, you can go to the/mnt/kerwin directory to view the files in the root directory of the host 10. install arm-linux-gcc 3.4.1 and write a hello world file to the root directory. In the super middle end, enter the root directory of the host ,. /hello, the following error occurs in the terminal: hello world! THE END