u-boot analysis and transplantation - based on u-boot-2011.3 and FL2440

For the basic method of transplantation, you can first read the u-boot README document

If the system board that you have is not listed, then you will need

to port U-Boot to your hardware platform. To do this, follow these

steps:

1.  Add a new configuration option for your board to the toplevel

"Makefile" and to the "MAKEALL" script, using the existing

entries as examples. Note that here and at many other places

boards and other names are listed in alphabetical sort order. Please

keep this order.

Refer to the existing records and add new configuration items to the Makefile and MAKEALL scripts in the top-level directory. Note that here and in many other places,

The board and other names are in alphabetical order. Please keep this order. (Personal note: most of the configuration items have been moved to

A separate file - boards.cfg)

2.  Create a new directory to hold your board specific code. Add any

files you need. In your board directory, you will need at least

the "Makefile", a ".c", "flash.c" and "u-boot.lds".

Create a new directory to store the development board related code. Add the necessary files to the development board directory, including at least

"Makefile"、".c"、 "flash.c" 和"u-boot.lds"。

3. Create a new configuration file "include/configs/.h" for your board

Create a new configuration file "include/configs/.h" for the target board

3.  If you're porting U-Boot to a new CPU, then also create a new

directory to hold your CPU specific code. Add any files you need.

If you are porting to a new CPU, you need to create a new directory to store the CPU-related code and add the required files.

4.  Run "make _config" with your new name.

Execute "make _config".

5.  Type "make", and you should get a working "u-boot.srec" file

to be installed on your target system.

6.  Debug and solve any problems that might arise.

[Of course, this last step is much harder than it sounds.]

Debug and fix any problems that arise. [Of course, this last step is much harder than it sounds.]

The following paragraph is quite interesting:

U-Boot Porting Guide:

----------------------

[Based on messages by Jerry Van Baren in the U-Boot-Users mailing

list, October 2002]

int main(int argc, char *argv[])

{

sighandler_t no_more_time;

signal(SIGALRM, no_more_time);

alarm(PROJECT_DEADLINE - toSec (3 * WEEK));

if (available_money > available_manpower) {

Pay consultant to port U-Boot;

return 0;

}

Download latest U-Boot source;

Subscribe to u-boot mailing list;

if (clueless)

email("Hi, I am new to U-Boot, how do I get started?");

while (learning) {

Read the README file in the top level directory;

Read http://www.denx.de/twiki/bin/view/DULG/Manual;

Read applicable doc/*.README;

Read the source, Luke;

/* find . -name "*.[chS]" | xargs grep -i */

}

if (available_money > toLocalCurrency ($2500))

Buy a BDI3000;

else

Add a lot of aggravation and time;

if (a similar board exists) {    /* hopefully... */

cp -a board/ board/

cp include/configs/.h include/configs/.h

} else {

Create your own board support subdirectory;

Create your own board include/configs/.h file;

}

Edit new board/ files

Edit new include/configs/.h

while (!accepted) {

while (!running) {

do {

Add / modify source code;

} until (compiles);

Debug;

if (clueless)

email("Hi, I am having problems...");

}

Send patch file to the U-Boot email list;

if (reasonable critiques)

Incorporate improvements from email list code review;

else

Defend code as written;

}

return 0;

}

void no_more_time (int sig)

{

hire_a_guru();

}