[U-Boot] Problem booting image + device tree (MPC5200B)

[U-Boot] Problem booting image + device tree (MPC5200B)

[Nandini Hengen]

Dear listers,

                  I currently have a problem with the device tree - the 
kernel hangs after unpacking and trying to load the device tree.



Distribution: OpenSuse 11.1, IA-64

Kernel 2.6.29

ARCH = ppc

CROSS_COMPILE = powerpc-603e-gnu-gcc

Hardware-Revision: Phytec MPC5200B-tiny Revision PL1245.1A

U-Boot Version 1.2 incl. downloaded patches



I've tried compiling different kernel versions (2.4.x and 2.6.x in 
combination with U-Boot 1.1.4). I also found a thread which recommended 
using the newest U-Boot version and loading the dtb file using tftp into RAM 
separately. Since then I've been using U-Boot 1.2. Until now non of the 
kernel images generated seem to load (apart from the image the module was 
originally shipped with)



To create the Kernel-Image and the device tree I use:

make uImage

make filename.dtb

with the corresponding options for ARCH and CROSS_COMPILE



I tried this using two phytec modules - both of which are non-functional at 
the moment. I reckon the kernel-image or the device tree are faulty or some 
patches are missing. The Hardware-Revision of the phytec-modules is 1245.1 - 
is the hardware out of date or is my problem related to missing patches ? 
The wrapped version as well as the version with a separate device tree hang 
while loading.

I'm currently wondering whether to send back the modules to Phytec or 
compiling a different kernel and device tree would help.



I would be grateful for any suggestions in this regard!





Best Regards,



Nandini Hengen



____________
Virus checked by G DATA AntiVirusKit
Version: AVF 19.323 from 30.03.2009
Virus news: www.antiviruslab.com

[U-Boot] Problem booting image + device tree (MPC5200B)

[Wolfgang Denk]

Dear "Nandini Hengen",

In message <B11FC910ABEE42FDA27A3D279E222940@cerec> you wrote:
> 
>                   I currently have a problem with the device tree - the 
> kernel hangs after unpacking and trying to load the device tree.
...
> U-Boot Version 1.2 incl. downloaded patches
...
> combination with U-Boot 1.1.4). I also found a thread which recommended 
> using the newest U-Boot version and loading the dtb file using tftp into RAM 
> separately. Since then I've been using U-Boot 1.2. Until now non of the 
> kernel images generated seem to load (apart from the image the module was 
> originally shipped with)

Rigth. The U-Boot versions you mntion are way too old to know about
device tree handling.

> I tried this using two phytec modules - both of which are non-functional at 

Well, and incorrect kernel will not render a board non-functional.

> I'm currently wondering whether to send back the modules to Phytec or 
> compiling a different kernel and device tree would help.

I recommend to get a recent version of U-Boot running.

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
The night sky over the planet Krikkit is the least interesting  sight
in the entire Universe.
                 - Douglas Adams _Life, the Universe, and Everything_

[U-Boot] Problem booting image + device tree (MPC5200B)

[Nandini Hengen]

Hello,
         I have also downloaded U-Boot version u-boot-2009.3 Are any additional patches for the MPC5200b-tiny necessary? In case of U-Boot 1.2 I had u-boot-1.2.0.tar.bz2 and u-boot-1.2.0.mpc5200b-tiny-2.tar.gz which added a patches directory to my main directory.

A few corrections to my previous email:
  a.. I'm using the option ARCH=powerpc and the config and dtb options for pcm030 which were present in the 2.6.29 Kernel-Sources I downloaded 
  b.. The modules are basically functional (not toasted as yet ;-) - what I meant to convey was that the kernel images don't seem to be able to boot and the original images it shipped with are not there any longer. I can download a new U-Boot version however. U-Boot 1.2 also seems to recognize the device tree (pcm030.dtb transfered to 0x600000 and uImage to 0x400000 using tftp). I get the message "Booting using flat device tree at 0x600000" when I try booting with "bootm 0x400000 - 0x600000". After that it just hangs.
I've mailed the Oselas.Phytec group - thanks for the tip.

Did you try one of the kernels generated by our board support package for this 
target?
I tried the kernel image uImage-pcm032-2 from pengutronix (assuming it was wrapped) and another pcm030 image which I compiled (generated using the 2.6.x sources on the Kit-CD downloaded from Pengutronix). Both don't seem to work at the moment. Could you please provide me with some links to suitable kernels or images for this target which are definitely functional ? I vaguely remember having read somewhere about the hardware revision number of the mentioned module not being compatible with some kernels - not too sure about this.


Best regards

Nandini Hengen



----- Original Message ----- 
From: "Wolfgang Denk" <wd@denx.de>
To: "Nandini Hengen" <nhengen@hengen-ingenieure.de>
Cc: <u-boot@lists.denx.de>
Sent: Wednesday, April 01, 2009 3:53 PM
Subject: Re: [U-Boot] Problem booting image + device tree (MPC5200B)


> Dear "Nandini Hengen",
> 
> In message <B11FC910ABEE42FDA27A3D279E222940@cerec> you wrote:
>> 
>>                   I currently have a problem with the device tree - the 
>> kernel hangs after unpacking and trying to load the device tree.
> ...
>> U-Boot Version 1.2 incl. downloaded patches
> ...
>> combination with U-Boot 1.1.4). I also found a thread which recommended 
>> using the newest U-Boot version and loading the dtb file using tftp into RAM 
>> separately. Since then I've been using U-Boot 1.2. Until now non of the 
>> kernel images generated seem to load (apart from the image the module was 
>> originally shipped with)
> 
> Rigth. The U-Boot versions you mntion are way too old to know about
> device tree handling.
> 
>> I tried this using two phytec modules - both of which are non-functional at 
> 
> Well, and incorrect kernel will not render a board non-functional.
> 
>> I'm currently wondering whether to send back the modules to Phytec or 
>> compiling a different kernel and device tree would help.
> 
> I recommend to get a recent version of U-Boot running.
> 
> 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
> The night sky over the planet Krikkit is the least interesting  sight
> in the entire Universe.
>                 - Douglas Adams _Life, the Universe, and Everything_ 
____________
Virus checked by G DATA AntiVirusKit
Version: AVF 19.323 from 30.03.2009
Virus news: www.antiviruslab.com

[U-Boot] Problem booting image + device tree (MPC5200B)

[Marco]

You could try to see if the kernel hangs but it prints something
checking __log_buf. In this way you can try to understand the problem.

Marco

Nandini Hengen ha scritto:
> Hello,
>          I have also downloaded U-Boot version u-boot-2009.3 Are any additional patches for the MPC5200b-tiny necessary? In case of U-Boot 1.2 I had u-boot-1.2.0.tar.bz2 and u-boot-1.2.0.mpc5200b-tiny-2.tar.gz which added a patches directory to my main directory.
> 
> A few corrections to my previous email:
>   a.. I'm using the option ARCH=powerpc and the config and dtb options for pcm030 which were present in the 2.6.29 Kernel-Sources I downloaded 
>   b.. The modules are basically functional (not toasted as yet ;-) - what I meant to convey was that the kernel images don't seem to be able to boot and the original images it shipped with are not there any longer. I can download a new U-Boot version however. U-Boot 1.2 also seems to recognize the device tree (pcm030.dtb transfered to 0x600000 and uImage to 0x400000 using tftp). I get the message "Booting using flat device tree at 0x600000" when I try booting with "bootm 0x400000 - 0x600000". After that it just hangs.
> I've mailed the Oselas.Phytec group - thanks for the tip.
> 
> Did you try one of the kernels generated by our board support package for this 
> target?
> I tried the kernel image uImage-pcm032-2 from pengutronix (assuming it was wrapped) and another pcm030 image which I compiled (generated using the 2.6.x sources on the Kit-CD downloaded from Pengutronix). Both don't seem to work at the moment. Could you please provide me with some links to suitable kernels or images for this target which are definitely functional ? I vaguely remember having read somewhere about the hardware revision number of the mentioned module not being compatible with some kernels - not too sure about this.
> 
> 
> Best regards
> 
> Nandini Hengen
> 
> 
> 
> ----- Original Message ----- 
> From: "Wolfgang Denk" <wd@denx.de>
> To: "Nandini Hengen" <nhengen@hengen-ingenieure.de>
> Cc: <u-boot@lists.denx.de>
> Sent: Wednesday, April 01, 2009 3:53 PM
> Subject: Re: [U-Boot] Problem booting image + device tree (MPC5200B)
> 
> 
>> Dear "Nandini Hengen",
>>
>> In message <B11FC910ABEE42FDA27A3D279E222940@cerec> you wrote:
>>>                   I currently have a problem with the device tree - the 
>>> kernel hangs after unpacking and trying to load the device tree.
>> ...
>>> U-Boot Version 1.2 incl. downloaded patches
>> ...
>>> combination with U-Boot 1.1.4). I also found a thread which recommended 
>>> using the newest U-Boot version and loading the dtb file using tftp into RAM 
>>> separately. Since then I've been using U-Boot 1.2. Until now non of the 
>>> kernel images generated seem to load (apart from the image the module was 
>>> originally shipped with)
>> Rigth. The U-Boot versions you mntion are way too old to know about
>> device tree handling.
>>
>>> I tried this using two phytec modules - both of which are non-functional at 
>> Well, and incorrect kernel will not render a board non-functional.
>>
>>> I'm currently wondering whether to send back the modules to Phytec or 
>>> compiling a different kernel and device tree would help.
>> I recommend to get a recent version of U-Boot running.
>>
>> 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
>> The night sky over the planet Krikkit is the least interesting  sight
>> in the entire Universe.
>>                 - Douglas Adams _Life, the Universe, and Everything_ 
> ____________
> Virus checked by G DATA AntiVirusKit
> Version: AVF 19.323 from 30.03.2009
> Virus news: www.antiviruslab.com
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] Problem booting image + device tree (MPC5200B)

[Nandini Hengen]

Thanks for the tip. I gather that the U-Boot version I'm using (1.2.0) is
appropriate for my hardware revision
in combination with the phycore-MPC5200B-tiny module as per the link sent by
Pengutronix

> The OSELAS.BSP-Phytec-phyCORE-MPC5200B-tiny-5 release should be still
> sufficient for you. If you can use this board support package (userland
> and
> kernel), you can start to try more recent kernels as the next step.

I also installed 2.6.20 from kernel.org and applied the kernel-patches from
the OSELAS.BSP-Phytec-phyCORE-MPC5200B-tiny-5.
I created a kernel image with ARCH=powerpc and
CROSS_COMPILE=powerpc-603e-linux-gnu- and the config file as present in
configs/phytec.......defconfig
The dtb file was created using the installation of dtc present by default
with the 2.6.29 kernel sources. The same problem occurs even with kernel
2.6.20.

I have not used the Oselas tool-chain or ptxdist as yet. U-Boot 1.2.0 with
patches could be installed onto flash memory and images transmitted even
without. Is this essential to get a kernel image to boot on the module? I'm
enclosing a logfile with my boot messages in case it's some very evident
version conflict I've overlooked.


Best regards,

Nandini

----- Original Message ----- 
From: "Marco" <marco.stornelli@gmail.com>
To: "Nandini Hengen" <nhengen@hengen-ingenieure.de>
Cc: <u-boot@lists.denx.de>
Sent: Wednesday, April 01, 2009 6:49 PM
Subject: Re: [U-Boot] Problem booting image + device tree (MPC5200B)


> You could try to see if the kernel hangs but it prints something
> checking __log_buf. In this way you can try to understand the problem.
>
> Marco
>
> Nandini Hengen ha scritto:
>> Hello,
>>          I have also downloaded U-Boot version u-boot-2009.3 Are any 
>> additional patches for the MPC5200b-tiny necessary? In case of U-Boot 1.2 
>> I had u-boot-1.2.0.tar.bz2 and u-boot-1.2.0.mpc5200b-tiny-2.tar.gz which 
>> added a patches directory to my main directory.
>>
>> A few corrections to my previous email:
>>   a.. I'm using the option ARCH=powerpc and the config and dtb options 
>> for pcm030 which were present in the 2.6.29 Kernel-Sources I downloaded
>>   b.. The modules are basically functional (not toasted as yet ;-) - what 
>> I meant to convey was that the kernel images don't seem to be able to 
>> boot and the original images it shipped with are not there any longer. I 
>> can download a new U-Boot version however. U-Boot 1.2 also seems to 
>> recognize the device tree (pcm030.dtb transfered to 0x600000 and uImage 
>> to 0x400000 using tftp). I get the message "Booting using flat device 
>> tree at 0x600000" when I try booting with "bootm 0x400000 - 0x600000". 
>> After that it just hangs.
>> I've mailed the Oselas.Phytec group - thanks for the tip.
>>
>> Did you try one of the kernels generated by our board support package for 
>> this
>> target?
>> I tried the kernel image uImage-pcm032-2 from pengutronix (assuming it 
>> was wrapped) and another pcm030 image which I compiled (generated using 
>> the 2.6.x sources on the Kit-CD downloaded from Pengutronix). Both don't 
>> seem to work at the moment. Could you please provide me with some links 
>> to suitable kernels or images for this target which are definitely 
>> functional ? I vaguely remember having read somewhere about the hardware 
>> revision number of the mentioned module not being compatible with some 
>> kernels - not too sure about this.
>>
>>
>> Best regards
>>
>> Nandini Hengen
>>
>>
>>
>> ----- Original Message ----- 
>> From: "Wolfgang Denk" <wd@denx.de>
>> To: "Nandini Hengen" <nhengen@hengen-ingenieure.de>
>> Cc: <u-boot@lists.denx.de>
>> Sent: Wednesday, April 01, 2009 3:53 PM
>> Subject: Re: [U-Boot] Problem booting image + device tree (MPC5200B)
>>
>>
>>> Dear "Nandini Hengen",
>>>
>>> In message <B11FC910ABEE42FDA27A3D279E222940@cerec> you wrote:
>>>>                   I currently have a problem with the device tree - the
>>>> kernel hangs after unpacking and trying to load the device tree.
>>> ...
>>>> U-Boot Version 1.2 incl. downloaded patches
>>> ...
>>>> combination with U-Boot 1.1.4). I also found a thread which recommended
>>>> using the newest U-Boot version and loading the dtb file using tftp 
>>>> into RAM
>>>> separately. Since then I've been using U-Boot 1.2. Until now non of the
>>>> kernel images generated seem to load (apart from the image the module 
>>>> was
>>>> originally shipped with)
>>> Rigth. The U-Boot versions you mntion are way too old to know about
>>> device tree handling.
>>>
>>>> I tried this using two phytec modules - both of which are 
>>>> non-functional at
>>> Well, and incorrect kernel will not render a board non-functional.
>>>
>>>> I'm currently wondering whether to send back the modules to Phytec or
>>>> compiling a different kernel and device tree would help.
>>> I recommend to get a recent version of U-Boot running.
>>>
>>> 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
>>> The night sky over the planet Krikkit is the least interesting  sight
>>> in the entire Universe.
>>>                 - Douglas Adams _Life, the Universe, and Everything_
>> ____________
>> Virus checked by G DATA AntiVirusKit
>> Version: AVF 19.323 from 30.03.2009
>> Virus news: www.antiviruslab.com
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot 

____________
Virus checked by G DATA AntiVirusKit
Version: AVF 19.323 from 30.03.2009
Virus news: www.antiviruslab.com

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: bootmessages.txt
Url: http://lists.denx.de/pipermail/u-boot/attachments/20090402/b6f2c877/attachment-0001.txt