Teach you to start from the beginning to build a friendly arm arm-tiny4412 development environment (most detailed!!) )

Source: Internet
Author: User
Tags bz2 chmod mkdir prepare

Create an ARM directory
Mkdir/disk/a9-p

Next you need to prepare the following things
1, arm-linux-gcc-4.5.1 Cross compiler
2. linux-3.5-tiny4412 kernel
3, rootfs_qtopia_qt4-20140124.tar.gz qt file System (DO)
4. busybox-1.22.1.tar.bz2 File System original code BusyBox
5, Uboot_tiny4412-20130729.tgz Uboot
6, arm-qte-4.8.5-20131207.tar.gz QT original code arm

7, uboot_tiny4412-20130729.tgz corresponding 4412uboot source code

8, Minicon serial port

9, install DNW, need to search the Internet dnw download and install to the system

10, an SD card, a serial line, a DNW line, a network cable



Well, we are ready to prepare, then see how to build the development environment.

1. Installing the Crossover Compiler
Cd/disk/a9

TAR-XVF arm-linux-gcc-4.5.1

LS opt
Friendlyarm

CP Opt/friendlyarm/opt-r

ls/opt/friendlyarm/toolschain/4.5.1/bin/

Copy/opt/friendlyarm/toolschain/4.5.1/bin/
Vim ~/.bash_profile

In path= $PATH: Add $HOME/bin below
Path= $PATH:/opt/friendlyarm/toolschain/4.5.1/bin/

Save Exit Ctrl +alt + BACKSPACE logoff

Test whether the installation is successful Arm-tab tab can list all the cross compilers to succeed

2. Compile Uboot
Cd/disk/a9

TAR-XVF uboot_tiny4412-20130729.tgz

CD uboot_tiny4412

Make Tiny4412_config

Make generates U-boot.bin u-boot files

3. Will be prepared U-boot.bin burned to the SD card

1> Insert SD Card

2>d Card
DD If=/dev/zero of=/dev/sdb bs=1024 count=102400

3> Burn Write
Cd/disk/a9/uboot_tiny4412/sd_fuse
Make
CD tiny4412
./sd_fusing.sh/dev/sdb

Burn, Finish.

Configure Minicom

On the command line, enter:
Minicom-s


┌─────[configuration]──────┐
│filenames and Paths
│file Transferprotocols
│serial Port Setup <== Select this item
│modem and dialing
│screen and keyboard
│save Setup as DFL
│save setup as..
│exit
│exit from Minicom
└──────────────────────────┘

Configure as shown in the figure
┌───────────────────────────────────────────────────────────────────────┐
│a-serial Device:/dev/ttyusb0
│b-lockfile Location:/var/lock
│c-callin Program:
│d-callout Program:
│e-bps/par/bits:115200 8N1
│f-hardware Flow Control:no
│g-software Flow Control:no

│change which setting?
└───────────────────────────────────────────────────────────────────────┘
Change it.
Enter

Save Setup as DFL as default
Exit exits

Exit minicom
CTRL + A + Q exit


The boot interface can then see the following print information:
U-boot 2010.12 (Oct 2015-11:03:50) for TINY4412
cpu:s5pc220 [Samsung SOC on Smpplatform Base on ARM CortexA9]
APLL = 1400MHz, MPLL = 800MHz

board:tiny4412
dram:1023 MiB
vdd_arm:1.2
vdd_int:1.0
vdd_mif:1.1
BL1 version:n/a (Trustzone enabledbsp)

Checking Boot Mode ... Sdmmc
revision:1.1
MMC Device 0:3724 MB
MMC Device 1:7456 MB
MMC Device 2:n/a
Warning-using Default Environment

Net:no Ethernet found.
Hit any key to stop autoboot:0
TINY4412 #


Kernel migration
Make up the kernel zimage give uboot guidance.

Cd/disk/a9

LS linux-3.5-tiny4412

TAR-XVF linux-3.5-tiny4412

CD linux-3.5

CP tiny4412_linux_defconfig. config

Make

Finally appear
Objcopy Arch/arm/boot/zimage
Kernel:arch/arm/boot/zimage is ready
Compilation successful
Arch/arm/boot/zimage



Install DNW
Cd/disk/a9/dnw-linux

Make
Make install


One. Download the kernel using the DNW method
1> minicom.
DNW 0x40008000

In 2> pc
cd/disk/a9/linux-3.5
DNW Arch/arm/boot/zimage

Download the kernel to the board successfully

3> boot kernel ==> boot kernel
Bootm 0x40008000

Two. SD Card Download kernel
1> off the SD card and zimage the kernel on the PC to the first partition on the SD card FAT32

2> the SD card into the development Board and turns the boot on

3> View the kernel on the SD card
FATLS MMC 0:1///view the partition directory for the first partition of the No. 0 MMC device

4> read the kernel on the SD card
Fatload MMC 0:1 0x40008000 zimage

5> Boot kernel
Bootm 0x40008000

Three. Automatically reads the kernel on the SD card and starts

In the Minicom
Set Bootcmd "fatload mmc 0:10x40008000 zimage;bootm 0x40008000"
Save

Reset to see if the kernel will start automatically



Four. Movi Kernel boot
1> DNW Download Kernel to board Uboot address 0x40008000

2> Write kernel

Movi Write kernel 0 0x40008000

3> set to start automatically
Set Bootcmd "movi read kernel 0 0x40008000;bootm 0x40008000"

4> Reset automatically start the kernel


Burn the file system
1> Network File System

Cd/disk/a9

TAR-XVF busybox-1.22.1.tar.bz2

CD busybox-1.22.1

Make Defconfig//default configuration

Make Menuconfig

Busybox Settings--->

[*] Build BusyBox as a static binary (no shared libs) │
[*] Build BusyBox as a positionindependent executable (NEW) │
[] Force Nommu build│
[] Build Shared Libbusybox (NEW) │
[*] Build with Large File Support (for accessing files > 2 GB) │
(arm-linux-) Cross Compiler Prefix

Save exit

Make-j4

Make install generates a directory _install


Make a file system

Cd/disk/a9
mkdir filesystem

Cd/disk/a9/filesystem

cp/disk/a9/busybox-1.22.1/_install/*.-R

mkdir etc Dev opt sys tmp mnt LIB proc

mkdir ETC/INIT.D

Vim Etc/init.d/rcs
Add to
Mount-t Ramfs None/dev
Mount-t Sysfs None/sys
MOUNT-T proc None/proc
Mount-t Tmpfs none/tmp
/sbin/mdev-s
Save exit

Vim Etc/inittab
Add to
:: Sysinit:/etc/init.d/rcs
Ttysac0::askfirst:-/bin/sh
Save exit

Vim Etc/profile
Add to
Export ps1= "[root @ cjy \w] #"
Save exit

Mknod dev/console C 5 1

cp/opt/friendlyarm/toolschain/4.5.1/arm-none-linux-gnueabi/lib/*./lib-r

Cd..
To Permissions
chmod 777 Filesystem-r

Publish File System
Vim/etc/exports
Add to
/disk/a9/filesystem * (Rw,sync,no_root_squash)
Save exit

Check whether the file system has been published
SHOWMOUNT-E 192.168.88.xxx

The board is configured with IP and Bootargs.

Set Gatewayip 192.168.88.1
Set IPADDR 192.168.88.x//Board IP
Set ServerIP 192.168.88.xxx//pc machine IP

Save

Set Bootargs "Root=/dev/nfsnfsroot=192.168.88.xxx:/disk/a9/filesystem
ip=192.168.88.x console=ttysac0,115200 LCD=S70 ctp=2 "

Save

Reset to see if the file system is entered

//************************************************************
SD Card File System

A >
Copy the/disk/a9/filesystem to the fourth partition on the SD card

Board
1> Save Nfsbootargs
Set Nfsbootargs $bootargs
Save

2>
Set Bootargs "root=/dev/mmcblk0p4console=ttysac0,115200 lcd=s70 ctp=2"
Save

3>
Reset to see if access to SD card file system

Two >
Enter the network file system first
Mount the fourth partition of the SD card
Mount/dev/mmcblk0p4/mnt
To package an existing file system
Cd/disk/a9/filesystem
TAR-CF Nfs.tar *
TAR-XVF nfs.tar-c/mnt
Umount/mnt

Board
2>
Set Bootargs "root=/dev/mmcblk0p4console=ttysac0,115200 lcd=s70 ctp=2"
Save

3>
Reset to see if access to SD card file system



Last one
Burning the file system directly to the MMC on the board
1.
Write the uboot into the fire.
DNW E4412_N.bl1.bin

First into the SD card Uboot
2.
eMMC Open 1
1 MMC on the board 0x40008000 from where to read 0 start block address 0x10 size
3.
MMC write 1 0x40008000 0 0x10

DNW Bl2.bin
4.
MMC write 1 0x40008000 0x10 0x1c

DNW U-boot.bin

5.
MMC write 1 0x40008000 0x300x1f6

6.
eMMC Close 1

7.
Segment power, pull SD card, choose NAND Start, on the power to see whether to enter the board Mmcuboot


Burning the MMC kernel
DNW Arch/arm/boot/zimage

Movi Write kernel 0 0x40008000
Set Bootcmd "movi read kernel 00x40008000;bootm 0x40008000"
Save

MMC on the partition board
Fdisk-p 0 View zoning Information
Creating partitions
FDISK-C 1000 500 500

Go directly to the network file system
Set Bootargs "Root=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
Save

After entering the system
Mount/dev/mmcblk0p2/mnt
TAR-XVF nfs.tar-c/mnt
chmod 777/mnt/-R
Umount/mnt


In U-boot
Set Bootargs "Root=/dev/mmcblk0p2 console=ttysac0,115200 lcd=s70 ctp=2"
Save

Reset start the file system in MMC




Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.