3. Download the UBOOT,KERNEL,ROOTFS to the Development Board

Download Uboot,kernel,rootfs to the Development Board 1, why download

The so-called download, also known as burning, deployment.

1.1. What is U-boot

The Bootloader of the hi3518ev200 veneer adopts u-boot.
U-boot is a commonly used in embedded systems Bootloader,bootloader is a small program executed before the operating system, through which we can initialize the hardware device, establish the Memory space mapping table, thus establishing the appropriate hardware and software environment, Prepare for the final call to the operating system kernel. The main running task of boot loader is to read the kernel image from the hard disk into RAM and then jump to the kernel entry point to run, starting the operating system. The system usually executes from the address 0x00000000 at power-up or reset, and the system's boot loader program is usually arranged at this address.

1.2. What is kernel

After burning Uboot, began to burn kernel. Kerne refers to the core part of most operating systems. It consists of those parts of the operating system that are used to manage storage, files, peripherals, and system resources. The operating system kernel typically runs processes and provides inter-process communication. The operating system must be run on the kernel, the kernel provides the most basic computer operation, and makes the bottom of the computer as safe and easy to manage.

1.3. What is Rootfs

The root filesystem is the first file system on which the kernel is booted, the kernel code image file is stored in the root file system, and the system boot launcher loads some basic initialization scripts and services into memory after the root file system is mounted. Because of the INIT=/LINUXRC, after the file system is mounted, the first program to run is the root directory of the LINUXRC, and this is a link to/bin/busybox, that is, the system up and running after the first program is BusyBox. BusyBox will first attempt to parse/etc/inittab to obtain further initialization configuration information (refer to the Parse_inittab () function in BusyBox source code init/init.c). In fact, Root_qtopia does not/etc/inittab this configuration file, according to BusyBox's bare metal, it will generate a default configuration. One of the most important of these is new_init_action (Sysinit,init_script, ""), which determines the next initialization script is init_script defined value, the default value of this macro is "Etc/init.d/rcs".

2, through the Hitool tool burning Uboot

Note: Hitool is developed based on JAVEEE, so jre-6u45-windows-i586 must be installed before running. Note It must be this version, otherwise it cannot be run.

• [] (1), open Hitool, select the corresponding chip, click Hibure
  

• [] (2), the software as set
  
  Note: The \package\image_uclibc_hi3518ev200 inside the HI3518ESDK provides a u-boot image, or it can be compiled by itself.

• [] (3), select, Burn Write
  

• [] (4), close the Hitool, the Development Board to connect the serial port to SECURTCRT, restart the Development Board, interrupt 3s boot into uboot mode
  

• [] (5), print default environment variable
  

3. Burn via TFTP network

The board enters Uboot mode at this time

3.1 TFTP pre-burn conditions

• [] (1), the Development Board to use a serial cable, a network cable connected to the PC, and SECURTCRT connected to the serial port.
• [] (2), restart the Development Board under the command line to enter U-boot

• [] (3), between the Development Board and the Uboot can be the TFTP network can ping through

• [] (4), preparing the mirror
  • Step 1, Mirror in OSDRV/PUB/IMAGE_UCLIBC, enter this directory first
  • Step 2, copy the related image to the Tftpboot directory
  • CP U-boot-hi3518ev200.bin uimage_hi3518ev200 rootfs_hi3518ev200_64k.jffs2/tftpboot/-F
  • cd/tftpboot/
  • Ls
  • Ls-l
  • Cd..
  • sudo chmod-r 777 tftpboot/
  • cd/tftpboot/
  • Ls
  • Ls-l
• [] (5), Development Board and Ubuntu settings:
  • Ubutun: Setting up a bridge to a wired network card, statically assigning IP
  • hi3518e Enter HiSilicon mode [Uboot], execute the following command to set the environment variable
    • • Set Bootcmd ' Bootm 0x82000000 '
    • • Set Bootargs mem=96m console=ttyama0,115200
    • • Set Serveip 192.168.1.141
    • • Set IP 192.168.1.10
    • • Save
  • Ping 192.168.1.141

• [] (6), print
  

# # 2.2, download kernel

• MW.B 0x82000000 FF 0x300000
• TFTP 0x82000000 uimage_hi3518ev200
• SF probe 0
• SF Erase 0x100000 0x300000
• SF Write 0x82000000 0x100000 0x300000

# # 2.3, download Rootfs

• MW.B 0x82000000 FF 0xc00000
• TFTP 0x82000000 ROOTFS_HI3518EV200_64K.JFFS2
• SF probe 0
• SF Erase 0x400000 0xc00000
• SF Write 0x82000000 0x400000 0xc00000

# # 2.4, set Bootcmd and Bootargs to properly start "after each tftpboot directory image update, the Development Board will be synchronized with the new image"

• Set Bootcmd ' SF probe 0;SF read 0x82000000 0x100000 0x300000;bootm 0x82000000 '
• Set Bootargs mem=32m console=ttyama0,115200 root=/dev/mtdblock2 rootfstype=jffs2 mtdparts=hi_sfc:1024k (boot), 3072K ( Kernel), 12288K (ROOTFS)
• Save
• Reset "can reboot the system"
  

3. Download the UBOOT,KERNEL,ROOTFS to the Development Board