[U-Boot-Users] step to port u-boot on custom board

[U-Boot-Users] step to port u-boot on custom board

[nilgosavi]

I want to know the step to port u-boot on my custom board and required tools 
-- 
View this message in context: http://www.nabble.com/step-to-port-u-boot-on-custom-board-tf2120824.html#a5849289
Sent from the Uboot - Users forum at Nabble.com.

[U-Boot-Users] step to port u-boot on custom board

[Marc Leeman]

> I want to know the step to port u-boot on my custom board and required tools 

http://www.denx.de/en/Documents/WebHome

-- 
  greetz, marc
One thing, just to be absolutely certain, you are the female of your
species, right? I'll take that as a yes.
	Crichton - The Flax
scorpius.homelinux.org 2.6.17 #2 PREEMPT Thu Jun 22 07:18:33 CEST 2006 GNU/Linux
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.denx.de/pipermail/u-boot/attachments/20060817/c64cf79d/attachment.pgp 

[U-Boot-Users] step to port u-boot on custom board

[Ajay Jain]

Hi,

> I want to know the step to port u-boot on my custom board and required tools

Read the Readme of the project. It has a lot of information about the
options available in the uboot. If you have a board, that is not
already supported by uboot, then you need to do the following. These
steps are also listed in the Readme.

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.
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 "<board>.c", "flash.c" and "u-boot.lds".
3.  Create a new configuration file "include/configs/<board>.h" for your 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.
4.  Run "make <board>_config" with your new name.
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.]

--
Ajay