The fifth chapter of Android Deep Exploration

After reading the fifth chapter of this book, I Learned:

1. Reasons to use the Development Board:

is the main device to learn embedded technology.

ARM's Development board can be based on the X86 architecture of the PC in the CPU instruction and the binary instruction format is different, and if the Linux driver to access hardware (LCD, Wifi, Bluetooth, etc.), and these hardware on the PC is difficult to simulate, so you need to debug and test on the Development Board with these hardware.

Similar to mobile phones, it is easier to install embedded systems than phones, there are many extended ports, and it is easy to develop custom hardware.

1. s3c6410 Development Board: A low-power, cost-effective RISC compact instruction set processor from Samsung, based on the ARM11 core, Provides optimized hardware performance for 2.5G and 3G communication services, built-in powerful hardware accelerator, integrated with an MFC, built-in advanced 3D Accelerator, optimized external memory interface.
2. OK6410 Development Board: Based on Samsung's latest ARM11 processor s3c6410, with strong internal resources and video processing capabilities, using the "core board + backplane" structure, on which can be installed wince6.0/7.0, Linux2.6.28 and the above version, Android2.1 and above version, Uc/osⅱ and other operating systems.
3. Install the Serial debugging tool (Minicom):

① prepare a USB to RS232 serial line, the serial port is connected to the OKC6410 Development Board, the USB end is connected to the PC, and the driver of the cable is installed on the PC machine.

② detect if the current system supports USB to serial port: Enter #lsmod in the virtual machine | grep usbserial

③ if supported, install: #apt-get installed minicom

④ configuration: #minicom –s Enter the "Serial Port Srtup" menu item configuration minicom, and then save, exit.

⑤ Test: #minicom confirm the correct connection of USB to serial cable and open the Board power supply, if the installation is successful, Minicom will receive the information transmitted from the Development Board data.

1. Burn Write Android system:

①OKC6410 Development Board default system is WinCE6.0, to install Android system, first need to uninstall wince.

② start Eboot Erase Nandflash:

Connect the Development Board and PC, start the minicom, launch the Development Board, wait for 5 seconds to enter the Eboot state by pressing the SPACEBAR, then enter "A" erase

③ prepare a 2/4GB SD card, insert the card reader and connect the PC

④ write to sd card Mmc.bin, Zimage-sd.bin: (under Windows XP environment)

Run Sd_writer,os_type Select "Android", select "root" and "kernel" respectively select "Mmc.bin", "Zimage-sd.bin", then click "Scan", confirm that the SD card is connected to the PC, click "Program "Write the Mmc.bin, zimage-sd.bin to the SD card.

⑤ burning to write Android ready to work:

First copy the Android_fs.tar, Mmc.bin, zimage-sd.bin files to the SD card

Then set the Development Board startup switch as a table:

⑥ burning Android from SD card:

Insert the SD card into the card slot, set up the board for SD card boot, open the Development Board.

Input #./yjsx copy SD card data, installed Android system off the Development Board, the switch back to the Nandflash state.

⑦ Calibration Screen: Restart the Development Board and calibrate the five calibration points with the touch pen.

1. To configure a wired network:

(settings can only be saved in memory)

① set IP and subnet mask: #ifconfig eth0 192.168.17.150 netmask 255.255.255.0 up

② Setup Gateway: #route add default GW 192.168.17.254 dev eth0

③ querying the current IP configuration in the Development Board: #/system/busybox/sbin/ifconfig

Querying the current routing table in the Development Board: #/system/busybox/sbin/route

You can also write the LINUXRC script file, located at the root of the Android system, save the previous Settings command in, with VI into the modified IP, subnet mask, gateway, save and restart the Development Board, you can automatically connect the network.

The fifth chapter of Android Deep Exploration