From: LiuTao <tliu@ict.ac.cn>
To: Jim Chapman <jim.chapman@iname.com>
Cc: LinuxPPC Developers List <linuxppc-dev@lists.linuxppc.org>,
"linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: need suggestions
Date: Wed, 24 Nov 1999 16:25:03 +0800 [thread overview]
Message-ID: <383BA0DF.510AA33E@ict.ac.cn> (raw)
In-Reply-To: 383AF067.2B8EB961@iname.com
Hi Jim:
I have a bootrom of vxWorks and I want to use it to download any
files that I need through FTP or TFTP. When I try to do it, I found
some problems.
If I use it to download vxWorks's image through FTP, that's all right.
If I use it to download vxWorks's image through TFTP, there is error.
If I use it to download a test image(ELF file), there is error too.
I think there must be some requirements to the download files, right?
Maybe the format of ELF is not correct?
I also want to make a bootrom of Linux, can you tell me how to do it?
I am a newbie, so if you can, tell me something in detail please.
Thanks!
LiuTao
Jim Chapman wrote:
>
> Re: using a vxworks bootrom to load zImage
>
> I am using a standard vxworks bootrom to load a zImage, but I had to
> make a few modifications to the zImage startup code to make it work. For
> us, it is useful to share the same target hardware between vxworks and
> linux developers, without having to reblow the flash bootrom each time
> we switch. And by building BOOTP into the vxworks bootrom, we simply
> change the BOOTP server entry to have the target boot vxWorks or zImage
> without changing the bootrom. However, once we're rid of vxworks
> altogether, then a linux-centric bootrom would be a much better
> solution.
>
> It turns out that the vxworks bootrom ELF support doesn't handle named
> ELF sections (it's yet another undocumented feature of Wind River code
> -- it silently ignores sections that aren't ".text" or ".data"...), and
> since the compressed vmlinux image is objcopy'd into a special "image"
> section by arch/ppc/mbxboot/Makefile, I had to find a way to put the
> image section inside the text segment so that the image data would be
> copied by the vxworks bootrom. There may be a clever way to do that
> using ld scripts, but I ended up converting the image data to assembly,
> and used a couple of public symbols at the start/end of the data so that
> (a modified) decompress_kernel() could find the image. The
> binary-to-assembly convertor is a simple perl script which does almost
> the same thing as vxWorks' binToAsm tool.
>
> The initrd stuff would need similar treatment, but since I don't use
> initrd, I haven't implemented it.
>
> If you want more details (and the binToAsm perl script) let me know.
>
> -Jim
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-11-24 8:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-23 19:52 need suggestions Jim Chapman
1999-11-23 20:54 ` Frank McPherson
1999-11-24 8:25 ` LiuTao [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-04-14 18:23 Need suggestions Ihor Lys
1999-11-23 21:57 need suggestions Brian Kuschak
1999-11-23 1:42 LiuTao
1999-11-23 3:46 ` Dan Malek
1999-11-23 3:46 ` LiuTao
1999-11-23 6:14 ` Dan Malek
1999-11-23 18:47 ` Geert Uytterhoeven
1999-11-24 8:34 ` LiuTao
1999-11-24 10:26 ` Magnus Damm
1999-11-24 8:56 ` Neil Russell
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=383BA0DF.510AA33E@ict.ac.cn \
--to=tliu@ict.ac.cn \
--cc=jim.chapman@iname.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-embedded@lists.linuxppc.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).