Setting up the test environment for S3C6410 Development Board

 

The Development Board of ARM architecture can be different in CPU instruction and binary format for PC based on X86 architecture. Linux drivers require access to hardware and these hardware are difficult to emulate on a PC, so they need to be debugged and tested on boards with these hardware.

S3C6410 is a low-power, cost-effective RISC processor from Samsung, based on the ARM11 core, which can be widely used in mobile phones and general processing applications. It provides optimized hardware performance for 2.5G and 3G communication services, built-in powerful hardware accelerators, integrates an MFC, supports MPEG4/H.263/H.264 codec and VC1 decoding, and provides real-time video conferencing and TV output for NRSC and PAL formats. The built-in 3D accelerator with state-of-the-art technology enables the OpenGL ES 1.1/2.0 and D3DM APIs to achieve 3D acceleration of 4M triangles/s. The s3c6410 includes an optimized external memory interface that can meet the data bandwidth requirements in high-end communication services.

Install serial debugging tool: Minicom

OK6410 Development Board with a serial port, can be connected to the PC through the serial line, Linux driver in the output of debugging information at the same time through the serial cable to send debugging information to the PC, This allows the Linux driver programmer to view debug information directly on the PC (serial communication: Displays debug information for the Linux driver output)

1. Check whether the current system supports USB to serial port: Lsmod | grep usbserial

2. Installing Minicom:apt-get Install Minicom

3. Configure minicom:

Minicom-s

Go to the "Serial Port Setup" menu item and configure it by content minicom

After Setup, select "Save setup as DFL" "Exit from Minicom"

4. Test minicom:minicom

Burn Write Android system

Erase Nandflash with Eboot

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

2. Enter Eboot Status: Open the power switch of the development Board, there is a prompt message waiting for 5 seconds (initiating image launch in 5 seconds), press the space bar of the PC keyboard is the development board stays in the Eboot state.

3. Erase Nandflash: Enter "A" to erase Nandflash.

Burn Write Android

1. Preparation: Prepare a 2GB or 4GB SD card, require FAT32 partition format, insert the card reader and connect the PC.

2. Write Mmc.bin and Zimage-sd.bin to the SD card: This step needs to be done in a Windows environment. Run Sd_writer,os type Select "Android" and select Mmc.bin and Zimage-sd.bin files in select root and select kernel, click the "Scan" button to automatically scan the drive letter to the SD card, click " Program to write the file to the SD card. When the write is successful, the "It's OK" dialog box is displayed.

3. Pre-Burn your Android: first copy the Android_fs.tar, Mmc.bin, and zimage files to the SD card, then set the startup switch on the board as shown in the table. (Nearest battery is Pin8 and descending, left is off, right is on)

4. Start burning Android from SD card: Insert SD card into slot of development Board and set SD card to boot, open Development Board, first write to board memory to start Android data, equivalent to brush boot.img to phone; # prompt, enter. yjsx command to copy the data from the SD card; "great!!! All jobs are over "information stating the successful installation of Android.

5. Calibrate screen: Close the board after installation and restore the switch to the Nandflash boot state. Restart the Development Board and calibrate the screen. (You can enter the command "Rm/data/pointercal" in minicom to delete the screen calibration file)

Configuring Wired Networks

You can set the IP and subnet masks using the Linux command ifconfig and set up the gateway with the route command. (ifconfig command defaults to set subnet mask to 255.255.255.0)

The "/system/busybox/sbin/ifconfig" "/system/busybox/sbin/route" command looks at the board's current IP configuration and routing table.

The Setup command can be written to the power-on auto-execute script file provided by the board so that the settings are retained after restarting the board.

Setting up the test environment for S3C6410 Development Board