From: Davide Ciminaghi <ciminaghi@gnudd.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] ARM interrupt handling
Date: Wed, 23 Jun 2004 14:34:00 -0000 [thread overview]
Message-ID: <20040623143736.GA10686@mail.gnudd.com> (raw)
Hi,
I have an ARM7 (Samsung s3c44b0x) target with no RAM at address 0 and,
as far as I know, no way to remap RAM at address 0.
I'd like to run a RAM application "on top" of redboot (compiled with
ROM startup).
There will also be a flash region with some data read/written by the
application and maybe initialized by redboot.
The application needs interrupts and kernel support.
The question is: how can Redboot invoke the application's irq handlers ?
My problem is that the application cannot overwrite the redboot vectors
because there's flash at address 0. Shall I modify the hal (vectors.S)
adding some "trampoline" code with a jump to the application's handlers ?
Thanks and regards
Davide
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2004-06-23 14:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040623143736.GA10686@mail.gnudd.com \
--to=ciminaghi@gnudd.com \
--cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).