Analysis to Ethernet controller in u-boot

Analysis to Ethernet controller in u-boot

 

There are two methods to initialize Ethernet controller in u-boot. Firstly, the initialization to Ethernet controller is implemented by invoking “eth_initialize() “, which is called by “start_armboot()” and in which board specific initializations to Ethernet controllers are discriminated by corresponding macros, respectively . This is a normal way. The other method may be not fit for people’s thought, which is accomplished by means of parsing some u-boot commands refering to some network protocols, then intializing Ethernet controller as needed. Take “tftpboot” command for an example. The related functions are as follows:

do_tftpb()->netboot_common()->NetLoop()->eth_halt(),eth_init(),TftpStart()->TftpSend()……

 

As to our board, the later method is adopted. I found out that the control and status registers are based on the base address of Ethernet controller to some degree, which is defined as 0x12000000 in reading code. Unfortunately, it’s difficult for me to understand its origin. To be worst, there is no more information on our datasheet.

 

 

References:

[1] http://www.jollen.org/blog/2006/09/uboot_driver.html

[2] http://blog.chinaunix.net/u2/68846/showart_694712.html