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.storne...@gmail.com>
To: "Nandini Hengen" <nhen...@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" <w...@denx.de>
To: "Nandini Hengen" <nhen...@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 <b11fc910abee42fda27a3d279e222...@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: w...@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@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
BOOT Messages when bootm is called without arguments for device tree blob:
-----------------------------------------------------------------------------------
U-Boot 1.2.0-mpc5200b-tiny-2 (Mar 30 2009 - 15:53:57)
CPU: MPC5200 v2.2, Core v1.4 at 399.999 MHz
Bus 133 MHz, IPB 133 MHz, PCI 66 MHz
Board: phyCORE-MPC5200B-tiny
I2C: ready
DRAM: 64 MB
FLASH: 16 MB
In: serial
Out: serial
Err: serial
Net: FEC ETHERNET
Type "run net_nfs" to load Kernel over TFTP and to mount root filesystem over
NFS
Hit any key to stop autoboot: 0
Using FEC ETHERNET device
TFTP from server 192.168.2.85; our IP address is 192.168.2.37
Filename 'uImage'.
Load address: 0x200000
Loading: T #################################################################
#################################################################
#################################################################
###########################################
done
Bytes transferred = 1214755 (128923 hex)
## Booting image at 00200000 ...
Image Name: Linux-2.6.20-rt3-pcm030-4
Created: 2009-04-02 7:36:44 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1214691 Bytes = 1.2 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
BOOT Messages when bootm is called with arguments for device tree blob:
-----------------------------------------------------------------------------------
U-Boot 1.2.0-mpc5200b-tiny-2 (Mar 30 2009 - 15:53:57)
CPU: MPC5200 v2.2, Core v1.4 at 399.999 MHz
Bus 133 MHz, IPB 133 MHz, PCI 66 MHz
Board: phyCORE-MPC5200B-tiny
I2C: ready
DRAM: 64 MB
FLASH: 16 MB
In: serial
Out: serial
Err: serial
Net: FEC ETHERNET
Type "run net_nfs" to load Kernel over TFTP and to mount root filesystem over
NFS
Hit any key to stop autoboot: 0
uboot> tftp 0x800000 pcm030new.dtb
Using FEC ETHERNET device
TFTP from server 192.168.2.85; our IP address is 192.168.2.37
Filename 'pcm030new.dtb'.
Load address: 0x800000
Loading: T ##
done
Bytes transferred = 6115 (17e3 hex)
uboot> bootm 0x400000 - 0x800000
## Booting image at 00400000 ...
Bad Magic Number
uboot> tftp 0x400000 uImage
Using FEC ETHERNET device
TFTP from server 192.168.2.85; our IP address is 192.168.2.37
Filename 'uImage'.
Load address: 0x400000
Loading: #################################################################
#################################################################
#################################################################
###########################################
done
Bytes transferred = 1214755 (128923 hex)
uboot> bootm 0x400000 - 0x800000
## Booting image at 00400000 ...
Image Name: Linux-2.6.20-rt3-pcm030-4
Created: 2009-04-02 7:36:44 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1214691 Bytes = 1.2 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Booting using flat device tree at 0x800000
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
