From: Eugene Surovegin <ebs@ebshome.net>
To: Frank Lautenbach <frank.lautenbach@gmx.de>
Cc: "linuxppc-embedded@ozlabs.org" <linuxppc-embedded@ozlabs.org>
Subject: Re: Getting a kernel to run on AMCC 440EP (Bamboo)
Date: Mon, 25 Jul 2005 10:00:17 -0700 [thread overview]
Message-ID: <20050725170017.GA29047@gate.ebshome.net> (raw)
In-Reply-To: <42E51849.7050800@gmx.de>
On Mon, Jul 25, 2005 at 06:50:17PM +0200, Frank Lautenbach wrote:
> 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?
>
Try PIBS specific image (made with mktree). This image has 'RPO'
letters at the beginning.
--
Eugene
prev parent reply other threads:[~2005-07-25 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 16:50 Getting a kernel to run on AMCC 440EP (Bamboo) Frank Lautenbach
2005-07-25 17:00 ` Eugene Surovegin [this message]
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=20050725170017.GA29047@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=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).