Linux 2.6.30.4 system porting to TQ2440

Finally, the compilation was successful, and many times it was caused by your own carelessness and negligence. If you can do it carefully, it should be able to solve it quickly. However, this will make you more familiar with the porting system. (This is done based on the manual. This is for TQ2440, kernel 2.6.30.4, and cross compiler 4.3.3) Step 1: Create your own cross compiler. I used the Fedora10 System in the Virtual Machine and installed the 4.3.3 cross compiler. After the establishment, I needed to use the arm-linux-gcc-

Finally, the compilation was successful, and many times it was caused by your own carelessness and negligence. If you can do it carefully, it should be able to solve it quickly.

However, this will make you more familiar with the porting system.

(This is mainly done according to the manual. This is for TQ2440, kernel 2.6.30.4, and cross compiler 4.3.3)

Step 1: Create your own cross compiler. I used the Fedora10 System in the Virtual Machine and installed the 4.3.3 cross compiler. After the establishment, I used arm-linux-gcc-v to check whether the installation was successful. If not, it is very likely that it is a problem with environment variables. In Fedora, the path is the absolute path to add pathmunge compiler to/etc/profile. In Ubuntu, the path is added to/etc/environment, and then source/etc /.... You also need to use mkyaffs + Tab (twice) to check whether the file system compiler is installed.

Step 2: Compile U-boot. Enter the command: make EmbedSky_config in the directory, and then make it again.

Step 3: Compile the kernel. After decompression, the kernel will have its own configuration. you can load this configuration by using make menuconfig. You can also make another one by yourself, but remember it, you must select the correct one. Otherwise, there will be many problems in the subsequent writing, and the configuration will be saved in. config. To modify the file information, run the command "make zImage" in the kernel directory to automatically generate the zImage. binfile in the directory. (Read the manual for details)

Step 4: Compile the file system: this step is also the most troublesome. First, extract the busybox and save the configuration file in busybox, which is the same as configuring the kernel. in config, remember to select the file format that supports ELF, and ARCH = arm, CROSS_COMPILE = arm-linux in Makefile. Remember this. Then enter the command: make; make install to install the file system, generate the directory _ install, and then create a new directory for the file system. Here, the directory is root_2.6.30, and copy the files in _ install, create the required files and directories according to the manual in root_2.6.30. Finally, because it is a MB Nandflash, we need to use mkyaffs2image for compilation to generate the file root_2.6.30.

After the compilation phase is completed, the system copies the generated three image files to the windows operating system and completes the writing through the terminal. It took almost a week to call! But ...... After checking, another problem occurs. When a command is successfully entered, the system will shut down the time and restart it? Is it a question about the dog? Let's take a look at it. Well, it's really a question about the dog. You have to go back to the kernel to set it or simply cancel it. It may be a problem, but now it's now. Most of the time, I still don't know what the configurations will do, but as the experiment below is more and more, I think there will be a time to hide, I believe I can do it, as long as I stick to it.

This article from the CSDN blog, reproduced please indicate the source: http://blog.csdn.net/williamlinchen/archive/2011/03/07/6228185.aspx