[U-Boot] Unable to boot Linux Kernel on Media5200

[U-Boot] Unable to boot Linux Kernel on Media5200

[Christopher Beley]

Hi,

I'm trying to gentoo running on the Media5200 but am running into issues
getting my kernel to boot.  I am able to boot the kernel that came with
freescale's BSP for the device, but when I boot my kernel things stall
after Uncompressing Kernel Image:

## Booting image at 00400000 ...
   Image Name:   Linux-2.6.30-mpc52xx
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    2315154 Bytes =  2.2 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

I'm not completely sure why my kernel isn't booting while freescale's is.  I should have all the correct drivers enabled, but after uncompress kernel Image nothing shows up in the console or on screen (the freescale logo/u-boot screen stays on the screen though).  I tried increasing the starting address for kicks, but that made no differnce.  I also tried doing something like:

tftp 400000; bootm 400000

but that gave me the same results as well.

Yes, I am using uImage and not cuImage.

When I compile my kernel I issue:


make ARCH="powerpc" CROSS_COMPILE="powerpc-unknown-linux-gnu-"
INSTALL_MOD_PATH="${SYSROOT}" "$@" EXTRAVERSION=-mpc52xx uImage

[U-Boot] Unable to boot Linux Kernel on Media5200

[Wolfgang Denk]

Dear Christopher Beley,

In message <4AC7ADA4.2080404@wisc.edu> you wrote:
> 
> I'm trying to gentoo running on the Media5200 but am running into issues
> getting my kernel to boot.  I am able to boot the kernel that came with
> freescale's BSP for the device, but when I boot my kernel things stall
> after Uncompressing Kernel Image:
> 
> ## Booting image at 00400000 ...
>    Image Name:   Linux-2.6.30-mpc52xx
>    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>    Data Size:    2315154 Bytes =  2.2 MB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK

I don't see any message about loading the device tree blob here?

> I'm not completely sure why my kernel isn't booting while freescale's is.  I should have all the correct drivers enabled, but after uncompress kernel Image nothing shows up in the console or on screen (the freescale logo/u-boot screen stays on the scree
> n though).  I tried increasing the starting address for kicks, but that made no differnce.  I also tried doing something like:

Maybe you are using different image types?

> tftp 400000; bootm 400000
> 
> but that gave me the same results as well.
> 
> Yes, I am using uImage and not cuImage.

With uImage, you need to load the device tree as well and pass it's
address as argument to bootm .

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
"If the code and  the  comments  disagree,  then  both  are  probably
wrong."                                                - Norm Schryer

[U-Boot] Unable to boot Linux Kernel on Media5200

[Christopher Beley]

Hi,

Thanks for the response.  I think that was it and also, I now see I
missed the FAQ that was similar to my question.  Sorry for not noticing
that.

Anyway, I haven't gotten things working just yet though.  I try to do
(for example):

setenv bootargs console=ttyPSC5,115200 root=/dev/nfs rw
nfsroot=$(serverip):$(rootpath)
tftp 900000 /tftpboot/media5200.dtb
tftp 500000 /tftpboot/uImage
bootm 500000 - 900000

However, after it uncompresses the kernel I get:

## Loading RAMDisk Image at 00000000 ...
Bad Magic Number

However, I do not have/want a RAMDisk and according to the FAQ I should
just be able to use a - to say I don't have one (since I need to specify
in the third argument the address of the dtb).  Any idea what I could be
doing wrong?  I guess I could always create a dummy ram disk and see if
it works...but...I shouldn't have to do that.

Also, more for curiosities sake, but I'm a little confused why I don't
need to upload a dtb when using the kernel freescale supplies and many
of the instructions I see online for different boards make no mention of
the dtb.  Is it just that the dtb is being appened to the end of the
kernel image in those cases maybe?

Thanks,
Chris


Wolfgang Denk wrote:
> Dear Christopher Beley,
>
> In message <4AC7ADA4.2080404@wisc.edu> you wrote:
>   
>> I'm trying to gentoo running on the Media5200 but am running into issues
>> getting my kernel to boot.  I am able to boot the kernel that came with
>> freescale's BSP for the device, but when I boot my kernel things stall
>> after Uncompressing Kernel Image:
>>
>> ## Booting image at 00400000 ...
>>    Image Name:   Linux-2.6.30-mpc52xx
>>    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>>    Data Size:    2315154 Bytes =  2.2 MB
>>    Load Address: 00000000
>>    Entry Point:  00000000
>>    Verifying Checksum ... OK
>>    Uncompressing Kernel Image ... OK
>>     
>
> I don't see any message about loading the device tree blob here?
>
>   
>> I'm not completely sure why my kernel isn't booting while freescale's is.  I should have all the correct drivers enabled, but after uncompress kernel Image nothing shows up in the console or on screen (the freescale logo/u-boot screen stays on the scree
>> n though).  I tried increasing the starting address for kicks, but that made no differnce.  I also tried doing something like:
>>     
>
> Maybe you are using different image types?
>
>   
>> tftp 400000; bootm 400000
>>
>> but that gave me the same results as well.
>>
>> Yes, I am using uImage and not cuImage.
>>     
>
> With uImage, you need to load the device tree as well and pass it's
> address as argument to bootm .
>
> Best regards,
>
> Wolfgang Denk
>
>   

[U-Boot] Unable to boot Linux Kernel on Media5200

[Wolfgang Denk]

Dear Christopher Beley,

In message <4AC8FB3E.3050609@wisc.edu> you wrote:
> 
> setenv bootargs console=ttyPSC5,115200 root=/dev/nfs rw
> nfsroot=$(serverip):$(rootpath)
> tftp 900000 /tftpboot/media5200.dtb
> tftp 500000 /tftpboot/uImage
> bootm 500000 - 900000
> 
> However, after it uncompresses the kernel I get:
> 
> ## Loading RAMDisk Image at 00000000 ...
> Bad Magic Number

That means that you are running a very, very old version of U-Boot
which does not incorporate any device tree support at all.

> However, I do not have/want a RAMDisk and according to the FAQ I should
> just be able to use a - to say I don't have one (since I need to specify
> in the third argument the address of the dtb).  Any idea what I could be
> doing wrong?  I guess I could always create a dummy ram disk and see if
> it works...but...I shouldn't have to do that.

No, this is not needed. The problem here is that your old U-Boot does
not know about the thre argument  version  of  "bootm",  and  neither
knows  how  to  deal  with  the secoind argument of '-' - it tries to
convert it into a ramdisk address, which  reasults  in  the  :Loading
RAMDisk Image at 00000000" message, which fails.

> Also, more for curiosities sake, but I'm a little confused why I don't
> need to upload a dtb when using the kernel freescale supplies and many
> of the instructions I see online for different boards make no mention of

This is probably ancient code from the Stone Age as well, where the
Device Tree was not invented yet.


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
Quantum Mechanics is God's version of "Trust me."

[U-Boot] Unable to boot Linux Kernel on Media5200

[Grant Likely]

On Sat, Oct 3, 2009 at 2:01 PM, Christopher Beley <cbeley@wisc.edu> wrote:
> Hi,
>
> I'm trying to gentoo running on the Media5200 but am running into issues
> getting my kernel to boot. ?I am able to boot the kernel that came with
> freescale's BSP for the device, but when I boot my kernel things stall
> after Uncompressing Kernel Image:
>
> ## Booting image at 00400000 ...
> ? Image Name: ? Linux-2.6.30-mpc52xx
> ? Image Type: ? PowerPC Linux Kernel Image (gzip compressed)
> ? Data Size: ? ?2315154 Bytes = ?2.2 MB
> ? Load Address: 00000000
> ? Entry Point: ?00000000
> ? Verifying Checksum ... OK
> ? Uncompressing Kernel Image ... OK

Hi Christopher,

The version of u-boot that shipped with the media5200 does not include
device tree support, so you need to use the cuImage.media5200 to boot
the board.  Unfortunately, you cannot use media5200.dts file that is
currently in the kernel tree as-is because you first need to add a
'chosen' node to specify the console so that you can get boot output.
Also, the u-boot image is buggy, and it cannot handle kernel images
larger than about 1MB (from my brief experimentation).

I recently ported an up-to-date version of u-boot to the media5200,
but I accidentally deleted the branch.  I waspretty simple, so it
would be easy for you to reproduce.  Then you'd be able to use the
normal 'bootm <kerneladdr> - <dtbaddr>' command to boot the system
with a uImage.

> I'm not completely sure why my kernel isn't booting while freescale's is. ?I should have all the correct drivers enabled, but after uncompress kernel Image nothing shows up in the console or on screen (the freescale logo/u-boot screen stays on the screen though). ?I tried increasing the starting address for kicks, but that made no differnce. ?I also tried doing something like:

The freescale kernel image is a much older image from the arch/ppc
branch which doesn't use the device tree.  There was a fair bit of
upheaval as mpc5200 support moved from arch/ppc to arch/powerpc.

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

[U-Boot] Unable to boot Linux Kernel on Media5200

[Christopher Beley]

Hi,

Thanks for getting back to me (sorry for the late response, I've had a
lot going on).   To be honest though, a lot of this is a little over my
head.  I was looking at some of your old patches and  taking a look at
the source for the total5200, which  I think is pretty similar to the
media5200, but am not totally sure how to go about it all.  Could you
maybe suggest some reading sources or tips on how to go about this? 
I've been looking at some documentation which describes what and where
everything is, but I'm not really sure where to go from there.  I'll
probally have to do a fair amount of reading either way for this.

I never tried bringing the kernel down to 1MB, but i'm not sure what to
do about the dts file either way.

--Chris

P.S. You know though, from the little I can find about the Media5200,
I'm beginning to think it was never very popular. 

Grant Likely wrote:
> On Sat, Oct 3, 2009 at 2:01 PM, Christopher Beley <cbeley@wisc.edu> wrote:
>   
>> Hi,
>>
>> I'm trying to gentoo running on the Media5200 but am running into issues
>> getting my kernel to boot.  I am able to boot the kernel that came with
>> freescale's BSP for the device, but when I boot my kernel things stall
>> after Uncompressing Kernel Image:
>>
>> ## Booting image at 00400000 ...
>>   Image Name:   Linux-2.6.30-mpc52xx
>>   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>>   Data Size:    2315154 Bytes =  2.2 MB
>>   Load Address: 00000000
>>   Entry Point:  00000000
>>   Verifying Checksum ... OK
>>   Uncompressing Kernel Image ... OK
>>     
>
> Hi Christopher,
>
> The version of u-boot that shipped with the media5200 does not include
> device tree support, so you need to use the cuImage.media5200 to boot
> the board.  Unfortunately, you cannot use media5200.dts file that is
> currently in the kernel tree as-is because you first need to add a
> 'chosen' node to specify the console so that you can get boot output.
> Also, the u-boot image is buggy, and it cannot handle kernel images
> larger than about 1MB (from my brief experimentation).
>
> I recently ported an up-to-date version of u-boot to the media5200,
> but I accidentally deleted the branch.  I waspretty simple, so it
> would be easy for you to reproduce.  Then you'd be able to use the
> normal 'bootm <kerneladdr> - <dtbaddr>' command to boot the system
> with a uImage.
>
>   
>> I'm not completely sure why my kernel isn't booting while freescale's is.  I should have all the correct drivers enabled, but after uncompress kernel Image nothing shows up in the console or on screen (the freescale logo/u-boot screen stays on the screen though).  I tried increasing the starting address for kicks, but that made no differnce.  I also tried doing something like:
>>     
>
> The freescale kernel image is a much older image from the arch/ppc
> branch which doesn't use the device tree.  There was a fair bit of
> upheaval as mpc5200 support moved from arch/ppc to arch/powerpc.
>
> g.
>
>   

[U-Boot] Unable to boot Linux Kernel on Media5200

[Grant Likely]

On Wed, Oct 14, 2009 at 5:04 PM, Christopher Beley <cbeley@wisc.edu> wrote:
> Hi,
>
> Thanks for getting back to me (sorry for the late response, I've had a
> lot going on). ? To be honest though, a lot of this is a little over my
> head. ?I was looking at some of your old patches and ?taking a look at
> the source for the total5200, which ?I think is pretty similar to the
> media5200, but am not totally sure how to go about it all. ?Could you
> maybe suggest some reading sources or tips on how to go about this?
> I've been looking at some documentation which describes what and where
> everything is, but I'm not really sure where to go from there. ?I'll
> probally have to do a fair amount of reading either way for this.

Look at an existing MPC5200 u-boot board port (like the phytec pcm030)
and duplicate it.  It also helps to look at the original media5200
u-boot patches that Freescale shipped on the software CD-ROM.

> I never tried bringing the kernel down to 1MB, but i'm not sure what to
> do about the dts file either way.

You really need to update u-boot I think.  Getting the kernel down
below 1MB and still be useful will be hard.  I would do it for you,
it's not really all that hard, but I don't really have any time at the
moment.

> P.S. You know though, from the little I can find about the Media5200,
> I'm beginning to think it was never very popular.

It really wasn't.  I've got one, and you're the only person I know
outside of Freescale who has another.

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.