[U-Boot-Users] Doubt regarding bootm in Uboot

Yasothabalan Ramaswamy-TLS,Chennai yasothabalanr at hcl.in
Mon Aug 6 08:39:28 CEST 2007


Thanks Grant.

After loading Uboot, we will get Uboot command. 

I will copy the kernel image to tftpboot directory.
And I will pass the command,

run tftp_nfs

to boot the kernel.


My question is after Uboot gets loaded, the control has to be
transferred directly to the kernel, without waiting in the UBOOT prompt.

So now after Uboot gets loaded, kernel should be loaded directly, where
I have to modify in the Uboot code for this could be done.

Note my question is how to transfer control directly to kernel from
Uboot. I should not get Uboot prompt, directly I should get the kernel
prompt.

Thanks,
Yaso.

-----Original Message-----
From: glikely at secretlab.ca [mailto:glikely at secretlab.ca] On Behalf Of
Grant Likely
Sent: Monday, August 06, 2007 11:03 AM
To: Yasothabalan Ramaswamy-TLS,Chennai
Cc: u-boot-users at lists.sourceforge.net
Subject: Re: [U-Boot-Users] Doubt regarding bootm in Uboot

On 8/5/07, Yasothabalan Ramaswamy-TLS,Chennai <yasothabalanr at hcl.in>
wrote:
> Hi all,
>
> I want to know how to transfer the control from Uboot to Linux Kernel.
I am using MPC5200B powerpc and ICECUBE board.
>
> Where exactly the Linux Kernel should be loaded?

Wherever you want to load it.  u-boot will relocate it to the correct
location after uncompressing the kernel uImage file.

>
>
>
> In cmd_bootm.c file,
<snip>
> What do these lines signify?

There are 2 different directories in the Linux kernel source tree
which can be used to build a powerpc kernel; arch/ppc and
arch/powerpc.  arch/ppc is obsolete and slowly all board support in
arch/ppc is moving over to arch/powerpc (support for mpc5200 is
currently in both trees).

BTW, for new designs, you should be using arch/powerpc (by setting
ARCH=powerpc in the environment when building the kernel)

One significant difference between arch/ppc and arch/powerpc is how
the bootloader communicates with the kernel for embedded platforms.
In arch/ppc, u-boot passes data via a static structure which has no
standard format as is prone to breakage.  In arch/powerpc, the
bootloader instead passes a device tree blob which does have a
standard format, and is much less prone to breakage.

So, when booting your Linux kernel that was built with ARCH=powerpc,
you should pass three parameters to the bootm command.
1. address of the kernel
2. address of the (or '-' if you don't have one)
3. address of the device tree

You can generate a device tree blob (.dtb file) by compiling the dts
file for your board with the device tree compiler (dtc).  The
Lite5200B device tree is in the kernel source tree in the directory
arch/powerpc/boot/dts.

Side note: you're email client is sending mail in HTML, not plain
ASCII text.  Etiquette on this list is for ASCII email only.

Cheers,
g.



-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely at secretlab.ca
(403) 399-0195

DISCLAIMER:
-----------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in 
this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of 
this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have
received this email in error please delete it and notify the sender immediately. Before opening any mail and 
attachments please check them for viruses and defect.

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




More information about the U-Boot mailing list