From: Jesper Skov <jskov@redhat.com>
To: "Eric Fradette" <emf8@po.cwru.edu>
Cc: "Ecos-Discuss" <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] Stub startup in Ram
Date: Wed, 05 Jul 2000 09:37:00 -0000 [thread overview]
Message-ID: <otn1jw1qld.fsf@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: <NEBBLBCPCLNPKNANBKIKGELBCAAA.emf8@po.cwru.edu>
>>>>> "Eric" == Eric Fradette <emf8@po.cwru.edu> writes:
Eric> Hi, I am trying to use the AEB-1 stub image as a basis for a
Eric> port to a different board that uses the same microcontroller.
Eric> My board has the angle debug monitor so I want to first try the
Eric> stub out running in RAM under angel control. I used the
Eric> configuration tool to choose the aeb-1 stub template and then
Eric> changed the startup to ram. When I use gdb to download the
Eric> created image to the board it downloads to an address of
Eric> 0xfc007fac with a starting address of 0xfc000060. My question
Eric> is where is this address coming from? I can't find it defined
Eric> anywhere in the ecos files, and it is outside of the memory map
Eric> for my board. Am I doing something wrong in how I configure the
Eric> stub for Ram startup? I have read the new hal platform porting
Eric> process web page and followed the directions for creating a stub
Eric> for Ram startup.
The runes for building a stub relocates the image. See the build rules
under CYGBLD_BUILD_GDB_STUBS and hack it to your needs. The code was
never inteded to be run from RAM, so it doesn't cater for it.
Jesper
prev parent reply other threads:[~2000-07-05 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-05 7:35 Eric Fradette
2000-07-05 9:37 ` Jesper Skov [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=otn1jw1qld.fsf@thinktwice.zoftcorp.dk \
--to=jskov@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=emf8@po.cwru.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).