"Tiny4412 start"

1. Compile uboot

a) installed toolchain (arm-linux-gcc- 4.5.1-v6-vfp-20120301.tgz) and set

   The environment variable PATH, to ensure the normal use.

 sudo tar -xvf arm-linux-gcc-4.5.1-v6-vfp-20120301.tgz –C /

 sudo vim / etc / environment PATH modified as follows:

 PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/opt/FriendlyARM/toolschain/4.5.1/bin"

problem:

  Learn several ways to preserve the environment variables What is the difference?

b) extracting uboot_tiny4412-20130729.tgz and entering the appropriate directory

   tar xzf uboot_tiny4412-20130729.tgz

c) configuration uboot and compile

   cd uboot_tiny4412

   make tiny4412_config

   make

 

d) compiling for generating bl2 tool

   make -C sd_fuse

 

 

2. Make the SD card to start

  Sd is assumed that the card is identified as / dev / sdb in linux.

    cd sd_fuse/tiny4412

  ./sd_fusing.sh /dev/sdb

 

3. Start uboot

  Sd card into the development board, select the SD card to start, you can see the startup information uboot after opening. If the development board is 1506, and then only with a CD uboot printing ok, because the disc is in the uboot for 1306,1506 relative to 1306 less two ddr. To use the latest uboot, uboot can find the latest in a friendly forum.

 

4. Compile the kernel

  1.cp  tiny4412_linux_defconfig  .config

  2.make menuconfig

  Then CONFIG_ARM_TRUSTZONE option removed, can be directly removed in the .config. Original kernel configuration and superboot is supporting, but there uboot does not support changing the function, if not removed, the kernel boot time, you will be prompted Uncompressing linux ..... done, booting the kernel.

  3. Remove the SD card, power off, kernel zImage on a PC and copying the first fat32 partition on the SD card.

  Mmc 4.fatls 0: 1 /      // view the directory partition on the first partition of MMC devices 0

  5. The fatload MMC 0 : 0. 1 x40008000  zImage // the SD Card is loaded into memory address 0x40008000 zImage

  6.bootm 0x40008000

problem:

  Normal bootm is to guide uImage, where if a go 0x40008000 or not start. Learn the difference bootm and go at?

  7. If you can start the kernel normal, then re-enter the uboot:

     set bootcmd "fatload mmc 0:1 0x40008000  zImage ;bootm 0x40008000

          save

The virtual machine installed nfs

  sudo apt-get install portmap

  sudo apt-get install nfs-kernel-server

  sudo apt-get install nfs-common

 

Guess you like

Origin www.cnblogs.com/zhuangquan/p/11547062.html