From: "Martin Laabs" <martin.laabs@mailbox.tu-dresden.de>
To: "ecos-devel@ecos.sourceware.org" <ecos-devel@ecos.sourceware.org>
Subject: Re: How to handle very fast repeating interrupts?
Date: Mon, 16 Feb 2009 10:29:00 -0000 [thread overview]
Message-ID: <op.upfwqqs8724k7f@martin_pc.home> (raw)
In-Reply-To: <AE37CDDF7D55EB4AB77E0D63F38594CBF40F@ny2545.corp.bloomberg.com>
Hello,
On Sun, 15 Feb 2009 23:33:55 +0100, Chris Zimman <czimman@bloomberg.com> wrote:
[Interrupt every 12us]
> Not to get of topic, but are you running eCos w/o the scheduler? Because if
> you're not, I don't see how you are going to be able to keep up with the time
> interval that you need.
I use the scheduler...
> That said, I would suggest just pointing the FIQ vector directly, and
> managing your own stack. You could just carve out a piece of memory for
> yourself (many ways to do this, depending on your application) and use that.
Yes - this was my idea too. Just beginnig a pice of assembler code at the
FIQ adress. (Even without a jump because it is at the end of the vector table)
Since the FIQ has 8 banked registers I fortunately do not even need a stack.
I'd like to place the ring-buffer into the fast onchip sram.
Can I just define some symbols in the linker script for that purpose? Or
can I tell the assembler to generate some symbols in a special section
like
.section ".sram_data"
_adc_buffer:
.rept 64
.long 0
.endr
_adc_buffer_start:
.long 0
_adc_buffer_end:
.long 0
Greetings,
Martin L.
next prev parent reply other threads:[~2009-02-16 10:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 18:13 Martin Laabs
2009-02-15 22:34 ` Chris Zimman
2009-02-16 10:29 ` Martin Laabs [this message]
2009-02-16 12:09 ` Chris Zimman
2009-02-16 12:32 ` Martin Laabs
2009-02-16 12:49 ` Chris Zimman
2009-02-16 12:57 ` Martin Laabs
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=op.upfwqqs8724k7f@martin_pc.home \
--to=martin.laabs@mailbox.tu-dresden.de \
--cc=ecos-devel@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).