Summary of NFS file system process under Davinci Mount VM-FC8

After a full day and one night, with the help of Liu Gong and Zeng Gong, the NFS file system was successfully mounted on the target board.

Some of them are summarized as follows:

 

About u-boot

After the cross-compilation environment is configured, make uImage does not have mkconfig and u-boot needs to be configured. Therefore, download the corresponding davinci evm version (make davinci evm) compiled by uboot) run the command export to PATH and then compile the kernel!

Some basic commands of u-boot can be abbreviated, saving a lot of trouble. For example, printenv is abbreviated to pr; saveenv is abbreviated to sa. After configuration, you must save it and write it to FLASH.

 

About Kernel

After each make clean operation, the rule clears the encrypted file, so you need to reconfigure the encrypted file. The version of the davinci kernel code differs greatly from the general kernel version on kernel.org, which is different from marvell. Therefore, it is not easy to overwrite the Kernel configuration (make def_config) before you are familiar with the configuration ). Otherwise, data abort will be suspended for many other reasons beyond this module ). Some external devices do not need to register with the platform or bus during initialization, such as some devices (cxd1391) that read and write through SPI ). Different external devices in the same read/write mode may also have different reading/writing time sequences. For example, when writing 16-bit data at a time on the 8-Bit Data Bus, some special protocols (mtd9x) need to be defined)

 

About Terminal

So far, we have used four types of terminals: putty, secuCRT, netterm, and xp. Not to mention the last one. Putty is commonly used in ssh mode, so it is used in a single way. SecuCRT and netterm are all terminals that support multiple communication protocols, including serial ports, SSH, and TELNET. The former is very nice, but has a fatal weakness. When copying long commands, it is easy to lose characters and is generally difficult to find. Netterm is generally not very stable, although it does not look very nice.

 

About nfs

I will not introduce nfs. I will directly start using the topic. First, check whether nfs (rpm-qa | grep nfs) is installed on your system, and then check whether there is a portmap. Portmap hurt me today. After half a day of FC5, portmap was not installed and some discrete versions were not installed, today I tried to dress a very frustrated portmap6.0 and its dependent package tcp_wrapper-7.6 is patch and change the source code tossing half a day installation successful discovery FC system does not regard it as a service. FC now uses rpcbind to replace portmap. After installation, restart all services (service nfs | network | rpcbind restart ). It is also important to disable all firewall-related services (iptables | iptablesv6 | isdn ...), try to use the same method to change the system settings either in the command line mode or in the graphic interface dialog box mode. In the end, remember to add rw, root_nospaush, and sync options under/etc/export to configure the file to be mounted. After the installation, try mounting the file on the PC (mount-t nfs ip:/direary ary/target_dir)

 

About davinci

Finally, the davinciDM644x arm + dsp is based on the arm system, and dsp is the core operation of image processing. At last, we changed the dsp part of the binary file. There are two methods for Kernel arm loading and file system loading: one is to directly load the file system in RAM, and the other is to load the img on the new memory address after tftp. After the development is complete, the kernel is written to flash and fixed after uboot, and then the file system in ram is loaded.

 

End.