Build a hi3520 Development Environment

The hi3520 development board just arrived. The first thing to do was to build the environment. It was originally called so many boards. It was not just a piece of cake, but it was a waste of an hour to mount NFS, depressed, this is good. Following the hi3520 context, we will record the construction process of this environment, so that we can take notes...
I bought the hi3520 Development Board of Yayi technology. The board is still pretty good, 6800 oceans. A maximum of eight SATA hard drives are required, so the Board uses the ATX power of the computer. Immediately connect to the serial port, power it on, wipe it, and there is no response. This is the case of the magic horse. When you call a question, you will know that the serial port received by the Board itself is not the debug serial port, uart0 needs to be connected by myself as the root line, so let's go...
Then I started to mount nfs. It was a very simple task, but I had to wait for a while because of the company's network. I used to use Ubuntu, but ubuntu was heavily dependent on the network, the company's network is limited. I can't install sudo apt-getinstall nfs-kernel-server by executing sudo apt-getinstall. Is there a way to save the country? Instead, I can change it to fedora.
Here, we will describe the basic steps for NFS mounting under Ubuntu and fedora, and then describe the issues to be aware:
Let's talk about Ubuntu below:
1. Install the NFS service
Run the following command: sudo apt-Get install nfs-kernel-server.
Nfs-common and Portmap are automatically installed when nfs-kernel-server is installed.
2. Modify the/etc/exports file
Run the command Vim/etc/exports.
Generally, the file content of the newly installed nfs-kernel-Server service should be blank. Add a line above and below in the file
/Root/hi3520194251.244 (RW, sync, no_root_squash)
Here/root/hi3520 indicates the shared directory on your Linux host. You can change the IP address to the IP address of your development board. The following parameters are already described on the Internet. Do not describe them too much.
3. Set the IP address of the Linux host.
4. Restart the NFS service.
Run the following command:
Sudo/etc/init. d/Portmap restart
Sudo/etc/init. d/nfs-kernel-server restart
 
Let's talk about the following in fedora:
The following is a little complex under fedora, but the NFS service of Fedora already exists when installing the system. We only need to configure and enable it.
1. Enable the NFS service
Enter setup in the terminal, select "System Service" in the pop-up menu, and select the netconsole, netplugd, and NFS services (press the Space key to select or cancel ). Press the tab key to exit.
Enter service NFS restart in the terminal to restart the NFS service
2. Modify the/etc/exports file
This is the same as the operation in Ubuntu.
3. Set the network on the Linux host
Here, we will not only set the IP address, but also set the network
Choose Edit> virtual networksetting> host virtual network mapping from the VM menu (VMware is used here ", select an existing network card from the first drop-down menu, that is, the real network card on your PC, and press "application", "OK"
Shut down the VM and confirm that the network connection is in bridged mode.
 
The above are some settings on the Linux host. The following points should be noted, because many of us are directly connected to the Development Board using a network cable when mounting NFS, you can set the IP address at will at this time, but in this case, you will not be able to access the Internet during development, so many people use a small humble to connect the PC and the development board to the LAN at the same time, when setting an IP address at this time, you must first confirm that the IP address is usable, and that the network connection of the virtual machine needs to be bridging.
 
Let's talk about setting up the hi3520 development board. I think many development boards use bootargs in uboot to mount nfs directly when Linux is started, however, haisi mounts NFS after it enters Linux. I personally think the latter is more flexible. If I want to mount it, it will be a little troublesome.
In the haisi document, I swear to write the script well.
Modprobe mmzmmz = DDR, 0, 0xc2000000, 16 m/* is inserted into the mmz module. This module is used by the network port driver */
Modprobe hiether/* Insert the network port driver module */
Ifconfig eth0 HW ether00: 10: 85: 18: 01: 84/* configure the MAC address */
Ifconfig eth010.85.180.184 netmask 255.255.254.0/* configure the IP address and subnet mask */
Route add default gw10.85.180.1/* configure the default gateway */
Modprobe nfs/* Insert NFS module */
Mount-T nfs-O nolock10.85.180.133:/home/c00002/glibc-nfs/mnt
It is exactly the same as the 3515 documentation, but your NIC Driver has changed. It's not responsible. I didn't even update the documentation, and I used a gigabit Nic on this board, you have to set the mode. I will wipe and paste my script content, and change the IP address and NFS Directory of the host based on the actual situation.
Modprobemmz mmz = DDR, 0, 0xc2000000, 16 m
Modprobeh2gether port_mode = 1
Ifconfigeth0 HW ether DC: 07: C1: Fe: 26: D3
Ifconfigeth0 192.168.1.244 netmask 255.255.255.0
Routeadd default GW 192.168.1.1
Modprobenfs
Mount-T nfs-O nolock 192.168.1.233:/root/hi3520/mnt
Execute this script, NFS will be mounted, and then you can develop it.
 
Note: When installing the 3520 SDK in Ubuntu, many people may report an error. It is ubuntu that changed the default shell to dash, run sudo dpkg-reconfigure Dash and select "no". Over!