Ti OMAP 3530 PSP compile note (4) --- run on the devkit8000 Board (1)

The first test showed that various dependent files were copied from the 2.6.28 kernel of devkit8000, such as the config configuration file, arch/ARM bottom-to-board support file (resource allocation, etc.), NIC driver, LCD driver, etc.; copy to the corresponding directory to the new kernel. These steps are mentioned by many people on the Internet during the transplantation process. For example:

 

Http://www.61ic.com/code/redirect.php? Tid = 26968 & goto = lastpost

 

In fact, it also solved some problems mentioned by others, for example, the compiler is too new to cause problems, and so on. After compilation, too many things were modified at the end, and many data structures were added to the kernel. The reference relationship is different from that of the 28 kernel, it turned out to have been compiled successfully (I remember there was no Nic or LCD Driver First). It was just a board-level support package modification and porting, but after the kernel was started to be decompressed, it will not go down.

 

I suspect that the Kernel configuration conflicts with the initialization, because I use TI to compile the EVM configuration by default and download it to the Board for running.

 

I started to try another method.

 

The idea is as follows: (1) devkit8000 imitates the clone version of beagleboard, and its kernel modification is also obtained from the Beagle configuration;

(2) the data structure of the kernel has changed greatly from 28 to the latest kernel version. Even with the old configuration to Beagle and the new configuration to Beagle, various drivers have become different.

(3) It can be seen from the above: from the old one to the Beagle (devkit8000) to the new one, but not to the devkit8000, there are two major things required: 1 is the kernel to adapt, 2. Adapt to the difference between beagle and devkit;

(4) kernel adaptation should be more complicated.

(5) Therefore, it is easier to modify the devkit8000 bit in the Beagle configuration from the new kernel.

 

Confirm your ideas and start construction.

 

 

For simplicity, I decided to directly modify the Beagle file to correspond to various files, instead of generating new devkit configurations, which saves a lot of configuration and changes makefile to work.
First configure the new kernel bit beagle to type, modify the Beagle corresponding to the Mach ID to 2001, in the file linux-03.00.01.06_baegle/ARCH/ARM/tools/Mach-types:

 

Omap3_beagle mach_omap3_beagle omap3_beagle 2001

 

Then make uimage. The command is successful. cp arch/ARM/boot/uimage/tftpboot. Then,

Download TFTP on the board and start bootm.

It can run but fails to load the network card.