linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Frank Lautenbach <frank.lautenbach@gmx.de>
To: "linuxppc-embedded@ozlabs.org" <linuxppc-embedded@ozlabs.org>
Subject: Getting a kernel to run on AMCC 440EP (Bamboo)
Date: Mon, 25 Jul 2005 18:50:17 +0200	[thread overview]
Message-ID: <42E51849.7050800@gmx.de> (raw)

Hi folks,

I want to bring up a linux kernel on the AMCC 440EP board (Bamboo). 
(still!  ;-) )

I managed to compile the kernel sources from kernel.org (2.6.12.3) with 
a cross tool chain created with
this great script from kegel.com (using demo-ppc440.sh). I set ARCH=ppc 
and CROSS_COMPILE=powerpc-440-linux-gnu-
during the configuration procedure (using xconfig) as well as for the 
actual buil process. Of course, I also
added the path to the ppc-crosstools to my PATH variable. Seems I did 
all that right, because the build process succeeded.

Finally I got an zImage.elf file (among some other variants) after the 
make process in .../arch/ppc/boot/images which I tried to load
via TFTP of the PIBS ROM Monitor. After the image has been loaded into 
RAM I get
a lapidar "error: can not process ELF program header, status: command 
rc=-1" and that's it...

When I examine the image file with readelf everything seems to be all 
right. All data seems to be plausible
and it is in fact a binary for PPC.

Anyhow seems to be wrong with the header format... Has anyone a guess 
what's the problem? Is PIBS
not able to load kernel images at all? Or do I have to create another 
kind of image format?

By the way:

Do I have to rearrange the default memory mapping of this board to get 
at least some success with the linux kernel?


Thanks for your help and sorry for my lame questioning... I am just new 
to this domain...

Bests,
    Frank

             reply	other threads:[~2005-07-25 16:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25 16:50 Frank Lautenbach [this message]
2005-07-25 17:00 ` Getting a kernel to run on AMCC 440EP (Bamboo) Eugene Surovegin

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=42E51849.7050800@gmx.de \
    --to=frank.lautenbach@gmx.de \
    --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).