From: Chris Dearman <chris@mips.com>
To: Roman Mashak <mrv@tusur.ru>
Cc: linux-mips@linux-mips.org
Subject: Re: Yamon compiling and linking
Date: Tue, 17 Aug 2004 11:45:51 +0100 [thread overview]
Message-ID: <4121E1DF.9020801@mips.com> (raw)
In-Reply-To: <001601c483fd$9e3ae180$1422bdd3@roman>
Roman Mashak wrote:
> When I compile little-endian only image, as far as I understood, I got image
> without RESET code at the beginning, so according to the memory map and link
> script (link_el.xn) - starting entry point is __RESET_HANDLER_END (locating
> in init.S) and its address is 0x9fc10000.
> So, I don't quite understand, how will be going after CPU reset? As
> documentation's saying "following a reset, hardware fetches instructions
> starting at the reset exception vector 0xBFC00000". But what is waiting at
> this address, because reset code (reset.S) is not compiled and is not
> linked?
I think you are using modified YAMON sources... I can tell you how
the build process works for the distributed version of YAMON:
Invoking make in the yamon/bin directory build two YAMON images (one
big-endian & one little-endian) in the EB & EL subdirectories. In
addition some endianess independent reset code (reset.o) is built in
yamon/bin. These three images are combined together to make a single
yamon-02.xx.rec image that can run in either endianess.
If you're only interested in running little-endian you should be able
to simply combine the reset-02.xx.rec and EL/yamon-02.xx_el.rec images.
Chris
--
Chris Dearman The Fruit Farm, Ely Road voice +44 1223 706206
MIPS Technologies (UK) Chittering, Cambs, CB5 9PH fax +44 1223 706250
next prev parent reply other threads:[~2004-08-17 10:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 1:57 Yamon compiling and linking Roman Mashak
2004-08-17 1:57 ` Roman Mashak
2004-08-17 10:45 ` Chris Dearman [this message]
2004-08-18 5:50 ` Roman Mashak
2004-08-18 5:50 ` Roman Mashak
-- strict thread matches above, loose matches on Subject: below --
2004-08-17 16:58 Saugata.Chatterjee
2004-08-18 5:53 ` Roman Mashak
2004-08-18 5:53 ` Roman Mashak
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=4121E1DF.9020801@mips.com \
--to=chris@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=mrv@tusur.ru \
/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