Android Deep Explore--hal and driver development----The fifth chapter reading notes

The fifth chapter mainly studies the test environment of building s3c6410 Development Board. The first thing to know is that s3c6410 is a low-power, cost-effective RISC processor that is based on the ARMI1 core and is widely used in mobile phones and general-purpose processing.

The Development Board is technically similar to the mobile phone we often use, and it also includes modules such as displays, keyboards, Wi-Fi, Bluetooth, and so on (possibly optional). But unlike phones, it is much easier to install embedded systems on board than phones. and the general development of the wrench has a lot of expansion of the port, it is easy to develop custom hardware and link with the Development Board. Therefore, the development Board is more suitable for testing the program than the Fu machine, especially for the underlying Linux programs such as Linux drivers.

There are many types of development boards on the market today, but the most popular is the Development board based on the Samsung s3c6410 ARM11 architecture. Many domestic manufacturers in the s3c6410 ARM11 Architecture Development Board based on the expansion, the development of the expansion board, this blog for the Ok6410-a Development Board. S3C6410 is a low power, cost-effective RISC processor from Samsung, which is based on the ARM11 core (arm1176jzf-s) and can be used in mobile phones and general processing applications.

Burn Write Android system

In order to install Android, you need to install the OK6410 Development Board by default is WinCE6.0, uninstall, and then install Android

To erase Nandflash using eboot:

1. Connect the Development Board and PC with the serial cable or USB to serial cable, and start the minicom

2. Open the OK6410 Development Board power switch, wait for 5 Seconds of information, press PC keyboard space bar is the development Board stay in the Eboot state

3. Enter "A" to erase Nandflash

1th Step: Prepare for a 2GB or 4GB SD card, require FAT32 partition format, insert card reader and connect pc

2nd step: Write Mmc.bin and zimage-sd.bin to SD card; This step needs to be done under Windows XP. Run Sd_writer,os type Select "Android" and select Mmc.bin and Zimage-sd.bin files to write to the SD card in select root and select Kernel respectively. The write is successful and the "It's OK" dialog box is displayed

3rd step: Burn and write the pre-work for Android. First copy the Android_fs.tar, Mmc.bin, and zimage files to the SD card, and then set the start switch on the Development Board

4th step: Start burning from SD card to write Android. Insert the SD card into the slot of the OK6410 Development Board, and set the SD card to boot, open the Development Board, first write to the board memory to start the Android data, the equivalent of Boot.bin to the phone, the # prompt appears, enter the. YJSX, the "great!!! All jobs are over "information indicating successful Android installation

5th step: Remember to close the Development Board after installation, restart the board will require calibration screen

Configuring Wired Networks

# ifconfig eth0 192.168.17.150 netmask 255.255.255.0 up

#route add default GW 192.168.17.254 dev eth0

#/system/busybox/sbin/ifconfig Querying the current IP configuration of the Development Board

#/system/busybox/sbin/route Query Routing table

Put all the setup commands into the script file Linuxre (depending on the situation), to ensure that each boot can automatically connect to the network

Development Board is the main hardware for the development and learning of embedded technology, in terms of technology, similar to our commonly used mobile phones, including monitors, keyboards, Wi-Fi, Bluetooth and other modules, the current market Development Board models and kinds of many, but the most popular is based on the Samsung S3C6410 ARM11 Architecture Development Board. s3c6410 ARM11 is a low-power, cost-effective RISC (reduced instruction SCT computer, streamlined instruction set computer) processor from Samsung, which is based on the ARM11 core and can be widely used in mobile phones and general processing applications.

First, build a compilation environment

Required cross-compilation toolchain: s3c6410x tool Chain 4.2.2-eabi V0.0-cross-4.2.2-eabi.tar

1. Unzip the tool chain above to get the folder: 4.2.2-eabi/

2. Create a directory below/usr/local/

arm/(Note that it is best to put it in this directory, or there may be some errors in the future compilation process)

3. Move the directory 4.2.2-eabi/below the/usr/local/arm/

4. Set Environment variables:

Edit the/etc/profile file, add: Path= "$PATH:/usr/local/arm/4.2.2-eabi/usr/bin" At the end of the file

Export PATH

To make an environment variable effective: In Terminal input command: source/etc/profile

Test environment variable is set successfully: in Terminal input: Echo $PATH

If the output path contains/usr/local/arm/4.2.2-eabi/usr/bin, the environment variable setting is successful

5. Test the cross-compilation tool chain

In Terminal input: arm-linux-gcc–v

Second, build the file system image production environment

1. Create a root file system directory

Rootfs and its subdirectories bin,sbin,boot,root,sys,srv,proc,usr, etc.

2. Compile busybox1.7.0: (Required source Bundle: BUSYBOX-1.7.0.TAR.BZ2)

2.1 Decompression Source Package, enter the source directory;

2.2 Configuration BusyBox: Do make menuconfig in the source directory, if you use the default configuration to exit, save, if you need to configure your own then change the appropriate options and then save exit.

2.3 Modifying the Makefile of the source directory

2.4 Formally compiled BusyBox: perform make compilation in source directory

2.5 Install BusyBox: Execute command make CONFIG_PREFIX=/***/ROOTFS (root file system directory) install

3. Copy glibc library-related files to the root file system

4. Create a configuration file

5. Create a Device file

6. Test the created root file system

http://www.cnblogs.com/caoyutao/

Android Deep Explore--hal and driver development----The fifth chapter reading notes

Android Deep Explore--hal and driver development----The fifth chapter reading notes