public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: ecos <ecos-discuss@sourceware.cygnus.com>
Subject: [ECOS] ARM vectors.S question
Date: Tue, 26 Oct 1999 13:44:00 -0000	[thread overview]
Message-ID: <19991026154448.A15481@visi.com> (raw)

I'm in the process of getting eCOS to run on a Samsung SNDS eval board
(ARM7TDMI core w/ a bunch of on-chip Samsung peripherals).  The file
ecos-1.2.1/packages/hal/arm/arch/v1_2_1/src/vectors.S claims to be
platform independent, yet it seems to make assumptions about the
memory map that are platform-dependent.

For example, it assumes that there is RAM at address 0 so the
startup code initializes the exception vectors that are at address 0.

After reset, the SNDS board has ROM at address 0, as will any embedded
system (if I understand the processor startup sequence).  There are
two ways to deal with this:

 1) The SNDS ROM vectors interrupts via a table of addresses that is
    in RAM, so user code can install pointers to ISRs in RAM at a
    particular address (0x13fffd0, FWIW).

 2) The memory configuration can be altered after startup to re-map RAM
    to address 0 and ROM to somewhere else.

Either of these would require changes to "platform independent"
sections of eCOS. 

Am I missing something?

-- 
Grant Edwards
grante@visi.com

             reply	other threads:[~1999-10-26 13:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-26 13:44 Grant Edwards [this message]
1999-10-26 15:05 ` Gary Thomas
1999-10-26 18:42   ` Grant Edwards
1999-10-27  4:00     ` Hugo Tyson
1999-10-27  5:14     ` Gary Thomas
1999-10-27  7:01       ` Grant Edwards
1999-10-27  7:09         ` Gary Thomas
1999-10-27  1:04 ` Dan Hovang
2013-10-12 14:54 [ECOS] ARM Vectors.S Question Michael Jones

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=19991026154448.A15481@visi.com \
    --to=grante@visi.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    /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).