PPCboot and latest kernel

PPCboot and latest kernel

[vijay sharma]

[-- Attachment #1: Type: text/plain, Size: 1946 bytes --]

Hi ALL,
I have been woking on upgrading an embedded system based on MPC8241 from
2.4.17 linux to 2.6.30 kernel.
I am currently struck one point.

Here is the console output where I am struck:
=================================
cpboot> bootm
## Booting image at 08000000 ...
   Image Name:   Linux-2.6.30
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    21729342 Bytes = 21220 kB = 20 MB
   Load Address: 01900000
   Entry Point:  01900570
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
Memory <- <0x0 0x10000000> (256MB)
CPU clock-frequency <- 0xbebc1fe (200MHz)
CPU timebase-frequency <- 0x17d783f (25MHz)
CPU bus-frequency <- 0x5f5e0ff (100MHz)

zImage starting: loaded at 0x01900000 (sp: 0x0fdc3a08)
Allocating 0x165ca04 bytes for kernel ...
gunzipping (0x00000000 <- 0x0190c000:0x02f58efc)...done 0x1637b54 bytes

Linux/PowerPC load:
Finalizing device tree... flat tree at 0x2f65300 <== Beyond this point no
output is available.
(The size of image is 20MB because ramfs embedded inside the image)

==================================

Here are the steps I have taken till now.
1) Defined platform.dts file for my platform. Since I am using MPC8241, I
have taken cuboot-824x.c. Is this file correct.
Do I need to define my own cuboot-*.c file ?

2)Built cuImage and loaded it into memory. I am not seeing any output once
control passes from wrapper to kernel. As you can see from logs mentioned
above.

While going through mail achieves I found two possible reasons for this
1) Wrong entries inside dts file
I am sure serial attributes are correctly defined inside the file. Also it
works for wrapper. It should work for linux also.

2) PPCboot not providing information.
I have built cuImage . Shouldn't kernel be getting its attributes from dtb
file rather then depending on bd_info structure.
I cannot upgrade to uboot. Is there some way I can make my board come up?

Thanks in advance,
Vijay

[-- Attachment #2: Type: text/html, Size: 2603 bytes --]

Re: PPCboot and latest kernel

[Wolfgang Denk]

Dear vijay sharma,

In message <e571380d0907191136j37d341d7k514f46396a38abc3@mail.gmail.com> you wrote:
> 
> I have been woking on upgrading an embedded system based on MPC8241 from
> 2.4.17 linux to 2.6.30 kernel.

Wow, that's a big leap...

You should also consider to update to the latest version of U-Boot;
the time when it was still called PPCBoot is long, long past.

> I am currently struck one point.
> 
> Here is the console output where I am struck:
> =================================
> cpboot> bootm
> ## Booting image at 08000000 ...
>    Image Name:   Linux-2.6.30
>    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>    Data Size:    21729342 Bytes = 21220 kB = 20 MB
>    Load Address: 01900000
>    Entry Point:  01900570
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK
> Memory <- <0x0 0x10000000> (256MB)
> CPU clock-frequency <- 0xbebc1fe (200MHz)
> CPU timebase-frequency <- 0x17d783f (25MHz)
> CPU bus-frequency <- 0x5f5e0ff (100MHz)
> 
> zImage starting: loaded at 0x01900000 (sp: 0x0fdc3a08)
> Allocating 0x165ca04 bytes for kernel ...
> gunzipping (0x00000000 <- 0x0190c000:0x02f58efc)...done 0x1637b54 bytes

You loaded the image at 01900000, but the uncompr4essed image extends
until 02f58efc, i. e. there is a good chance that you will overwrite
parts of the still uncompressed image.

> Linux/PowerPC load:
> Finalizing device tree... flat tree at 0x2f65300 <== Beyond this point no
> output is available.

Your device tree might be wrong, too.


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@denx.de
Any sufficiently advanced bug is indistinguishable from a feature.
                                                      - Rich Kulawiec

Re: PPCboot and latest kernel

[Scott Wood]

On Mon, Jul 20, 2009 at 07:40:41PM +0200, Wolfgang Denk wrote:
> > zImage starting: loaded at 0x01900000 (sp: 0x0fdc3a08)
> > Allocating 0x165ca04 bytes for kernel ...
> > gunzipping (0x00000000 <- 0x0190c000:0x02f58efc)...done 0x1637b54 bytes
> 
> You loaded the image at 01900000, but the uncompr4essed image extends
> until 02f58efc, i. e. there is a good chance that you will overwrite
> parts of the still uncompressed image.

I think the above output says that the compressed image extends to
0x02f58efc, and that the uncompressed image goes from zero to 0x165ca04. 
So no conflict (you should get an error message in case of conflict) with
0x01900000.

> > Linux/PowerPC load:
> > Finalizing device tree... flat tree at 0x2f65300 <== Beyond this point no
> > output is available.
> 
> Your device tree might be wrong, too.

Either that or something is wrong with the kernel itself.  This is the
point at which it transfers control to the main kernel.

-Scott

Re: PPCboot and latest kernel

[Scott Wood]

On Mon, Jul 20, 2009 at 12:06:42AM +0530, vijay sharma wrote:
> 2)Built cuImage and loaded it into memory. I am not seeing any output once
> control passes from wrapper to kernel. As you can see from logs mentioned
> above.

Try enabling early udbg console output.  Also, make sure that Linux is
using the correct baud rate (either with console= or by putting a
current-speed property in the serial node), and that your board file
matches the device tree's root compatible (i.e. the probe function will
succeed).

> While going through mail achieves I found two possible reasons for this
> 1) Wrong entries inside dts file
> I am sure serial attributes are correctly defined inside the file. Also it
> works for wrapper. It should work for linux also.

That does not follow.  There are many things that Linux depends on in the
tree that the wrapper does not care about.

> 2) PPCboot not providing information.
> I have built cuImage . Shouldn't kernel be getting its attributes from dtb
> file rather then depending on bd_info structure.
> I cannot upgrade to uboot. Is there some way I can make my board come up?

If you cannot upgrade to u-boot, then no, it should not be passing a
device tree since it is too old.  Dealing with old firmware that only
passes bd_t is what cuImage is for.

How about:

3) Something is wrong with the kernel port to this platform? :-)

-Scott