linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ben Warren <bwarren@qstreams.com>
To: Gary Kenaley <gkenaley@echelon.com>, linuxppc-embedded@ozlabs.org
Subject: RE: Unable to Boot 2.6.19.2 from ELDK 4.1 on MPC8349E MDS
Date: Mon, 9 Apr 2007 19:31:03 -0700 (PDT)	[thread overview]
Message-ID: <871602.42517.qm@web303.biz.mail.mud.yahoo.com> (raw)
In-Reply-To: <DDBD7B17DB2ECE48BCD94C593F7255B4046E9F23@monk.echelon.echcorp.com>

Gary,

--- Gary Kenaley <gkenaley@echelon.com> wrote:

> I have been evaluating Freescale 2.6.11, Wind River
> 2.6.14, and am now
> attempting Denx 2.6.19 (from ELDK 4.1) - running on
> the Rev 1.0 MPC8349E
> MDS (V1.1 CPU). I boot 2.6.19.2 using the factory
> u-boot 1.1.3 and the
> kernel immediately hangs:
> Uncompressing Kernel Image ... OK {hangs forever}

This version of U-boot is very old.  It is too old to 
boot a Linux kernel that was built using ARCH=powerpc.
 
On to your questions...  
<snip>

> Questions, please:
> ------------------
> 1. Should I expect this kernel to boot on the
> MPC8349E MDS, or do I need
> to find and apply a variety of patches?
> 
This kernel will boot on this board (I have the same
board), but you need to do a few things:

1. Get the latest U-boot.  It's available via git
from:
git://www.denx.de/git/u-boot.git.
2. Get 'dtc', the device tree compiler.  It's
available at www.jdl.com
3. Compile the device tree file for your board, which
is in /arch/powerpc/boot/dts/mpc8349emds.dtc of the
Linux source.
4. From U-boot, load the .dtb file that was generated
in step 3 either into memory or flash.
5. Modify whatever U-boot command you're using to boot
Linux to call 'bootm <kernel address> - <dtb address>
6. Try to not get frustrated about this device tree
stuff.  It's not very well documented, but several
people recognize this and are working to remedy it.

> 2. Any idea why I have problems doing the "ELDK 4.1
> full source rebuild
> from scratch"?
> 
Can't comment.  I'm still on ELDK 4.0.
> 3. Do you see anything else important that I should
> change in my
> process?
> 
> Since I am a bit of a newbie, I'll be grateful to
> get a lot of specific
> advice.
> 
> Thanks, Gary

Feel free to ping the U-boot list if you need help. 
It's very possible that I missed something here or
wrote something incorrectly.  Please ask again if you
still have difficulty.

regards,
Ben

  reply	other threads:[~2007-04-10  2:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-09 17:33 Simple experiment with, ML403, running 2.6 kernel , kernel.org source Mohammad Sadegh Sadri
2007-04-10  1:33 ` Unable to Boot 2.6.19.2 from ELDK 4.1 on MPC8349E MDS Gary Kenaley
2007-04-10  2:31   ` Ben Warren [this message]
2007-04-10 16:13   ` David Hawkins
2007-04-10 17:17   ` Wolfgang Denk
2007-04-11  1:30     ` Gary Kenaley

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=871602.42517.qm@web303.biz.mail.mud.yahoo.com \
    --to=bwarren@qstreams.com \
    --cc=gkenaley@echelon.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).