linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* Getting a kernel to run on AMCC 440EP (Bamboo)
@ 2005-07-25 16:50 Frank Lautenbach
  2005-07-25 17:00 ` Eugene Surovegin
  0 siblings, 1 reply; 2+ messages in thread
From: Frank Lautenbach @ 2005-07-25 16:50 UTC (permalink / raw)
  To: linuxppc-embedded@ozlabs.org

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Getting a kernel to run on AMCC 440EP (Bamboo)
  2005-07-25 16:50 Getting a kernel to run on AMCC 440EP (Bamboo) Frank Lautenbach
@ 2005-07-25 17:00 ` Eugene Surovegin
  0 siblings, 0 replies; 2+ messages in thread
From: Eugene Surovegin @ 2005-07-25 17:00 UTC (permalink / raw)
  To: Frank Lautenbach; +Cc: linuxppc-embedded@ozlabs.org

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2005-07-25 17:00 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-07-25 16:50 Getting a kernel to run on AMCC 440EP (Bamboo) Frank Lautenbach
2005-07-25 17:00 ` Eugene Surovegin

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).