[U-Boot] New to u-boot

[U-Boot] New to u-boot

[Rene Kolarik]

Hi, I am new to U-Boot, how do I get started?

I work at Freescale and in my free time I would like to port uboot to some
ARM and PPC board of the Freescale's Tower System.

Rene Kolarik

[U-Boot] New to u-boot

[Wolfgang Denk]

Dear Rene,

In message <CAB71J7aq1fnsPSUgDHO1DPoKYN6W1j6stkeipYfqRk1n9iT1gw@mail.gmail.com> you wrote:
> 
> Hi, I am new to U-Boot, how do I get started?

Welcome aboard.

> I work at Freescale and in my free time I would like to port uboot to some
> ARM and PPC board of the Freescale's Tower System.

If you want, you can just look around which boards / architectures are
already supported in mainline U-Boot (and/or read the mailing list
archives, or ask) which features are still missing); then check what
is available as out-of-tree code in Freescale's LTIB and other
distributions.  Then start to adapt this out-of-tree code to current
versions of U-Boot, and push the patches mainline.

This is a task where you don't have to start at the lowest levels, and
you can build up your experience gradually as you go.

Good luck!

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Dealing with failure is easy: work hard to improve. Success  is  also
easy  to  handle:  you've  solved  the  wrong  problem.  Work hard to
improve.

[U-Boot] New to u-boot

[Anton Staaf]

Rakesh, you probably want to take a look at the mkconfig script.  It is
responsible for doing much of the board configuration in preparation for
building, including the generation of the top level config.mk that specifies
things like ARCH, CPU and BOARD.

-Anton

On Mon, Jul 11, 2011 at 8:54 AM, Simon Schwarz <
simonschwarzcor@googlemail.com> wrote:

> Hi Rakesh,
>
> > I am new to u-boot. I want to understand the flow of u-boot.
> Here is a starting point for you:
> http://marc.info/?t=130381454100002&r=1&w=2
>
> > I did not understand that how board gets configured? in older version of
> > u-boot i can see <board name>_config option in makefile, but in newer
> > version it is not available in Makefile. So where it is?
> boards.cfg has name ARCH, CPU based on this the makefile uses the
> respective sources and config.
> I don't know the actual mechanism in make - but i'am sure someone can
> answer this ;)
>
> Regards
> Simon
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>

[U-Boot] New to u-boot

[Simon Schwarz]

Hi Rakesh,

> I am new to u-boot. I want to understand the flow of u-boot.
Here is a starting point for you:
http://marc.info/?t=130381454100002&r=1&w=2

> I did not understand that how board gets configured? in older version of
> u-boot i can see <board name>_config option in makefile, but in newer
> version it is not available in Makefile. So where it is?
boards.cfg has name ARCH, CPU based on this the makefile uses the
respective sources and config.
I don't know the actual mechanism in make - but i'am sure someone can
answer this ;)

Regards
Simon

[U-Boot] New to u-boot

[Rakesh Modi]

Hello Guys,
I am new to u-boot. I want to understand the flow of u-boot.

I have tried to go through start.s file, but I stop after arm_boot function
call.

I did not understand that how board gets configured? in older version of
u-boot i can see <board name>_config option in makefile, but in newer
version it is not available in Makefile. So where it is?

I also want to know that during compilation how specific board files links
with each other?

-- 
Thanks & Regards
Rock