From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Guillaume Dargaud" <dargaud@lpsc.in2p3.fr>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: zImage.embedded
Date: Fri, 11 Apr 2008 07:55:31 -0600 [thread overview]
Message-ID: <fa686aa40804110655x48120e84tde01a52d8bb39a3@mail.gmail.com> (raw)
In-Reply-To: <014701c89bda$09380060$ad289e86@LPSC0173W>
On Fri, Apr 11, 2008 at 7:43 AM, Guillaume Dargaud
<dargaud@lpsc.in2p3.fr> wrote:
> Hello all,
>
> I'm not sure what kind of error this is. I'm trying to generate a kernel
> image suitable for network boot and it seems to fail at the very end (wrong
> target ?)
>
> $ make ARCH=ppc CROSS_COMPILE=powerpc-linux-uclibc- znetboot
>
> powerpc-linux-uclibc-objcopy -O elf32-powerpc arch/ppc/boot/simple/zvmlinux
> arch/ppc/boot/simple/zvmlinux -R .comment -R .stab \
> -R .stabstr -R .ramdisk
> cp -f arch/ppc/boot/simple/zvmlinux arch/ppc/boot/images/zImage.elf
> rm -f arch/ppc/boot/simple/zvmlinux
> cp arch/ppc/boot/images/zImage.embedded /tftpboot/zImage.embedded
> cp: cannot stat `arch/ppc/boot/images/zImage.embedded': No such file or
> directory
> make[2]: *** [znetboot] Error 1
> make[1]: *** [simple] Error 2
> make: *** [znetboot] Error 2
>
> is the file zImage.elf my proper network image ?
What bootloader is on your board? zImage.elf *might* be the proper
image. If you're using u-boot, then you want to build a uImage
instead.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-04-11 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 13:43 zImage.embedded Guillaume Dargaud
2008-04-11 13:55 ` Grant Likely [this message]
2008-04-11 15:51 ` zImage.embedded Guillaume Dargaud
2008-04-11 16:04 ` zImage.embedded Grant Likely
2008-04-14 16:05 ` zImage.embedded Guillaume Dargaud
2008-04-14 20:55 ` [Buildroot] zImage.embedded Ulf Samuelsson
2008-04-15 9:33 ` Guillaume Dargaud
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=fa686aa40804110655x48120e84tde01a52d8bb39a3@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=dargaud@lpsc.in2p3.fr \
--cc=linuxppc-dev@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).