From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Problem booting image + device tree (MPC5200B)
Date: Wed, 01 Apr 2009 15:53:35 +0200 [thread overview]
Message-ID: <20090401135335.31A0F83797DC@gemini.denx.de> (raw)
In-Reply-To: <B11FC910ABEE42FDA27A3D279E222940@cerec>
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_
next prev parent reply other threads:[~2009-04-01 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 13:16 [U-Boot] Problem booting image + device tree (MPC5200B) Nandini Hengen
2009-04-01 13:53 ` Wolfgang Denk [this message]
2009-04-01 14:57 ` Nandini Hengen
2009-04-01 16:49 ` Marco
2009-04-02 13:14 ` Nandini Hengen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090401135335.31A0F83797DC@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox