From: "Vincent Leclaire" <vleclaire@awox.com>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Maximum sampling rate
Date: Tue, 14 Oct 2003 17:09:00 -0000 [thread overview]
Message-ID: <CE838B1FA9529449BDBA8951D3CD169F1560@sumatra.mop.awox.com> (raw)
Hi folks,
I have to design an application that will sample a given pin in order to
"reproduce" the recorded sequence. The signal might go up to 500KHz
(sampling at 1MHz+), target is ARM7 100MHz clock (or more).
From your experience, does this seem feasible safely ? What's the best
way to proceed (I will probably have to use some sort of interrupt/timer
so I'm talking about eCos relationship with interrupt handlers and the
like) ?
Many thanks
VL
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2003-10-14 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 17:09 Vincent Leclaire [this message]
2003-10-14 17:19 ` Gary Thomas
2003-10-14 17:25 Vincent Leclaire
2003-10-15 6:54 ` Eric de Jong
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=CE838B1FA9529449BDBA8951D3CD169F1560@sumatra.mop.awox.com \
--to=vleclaire@awox.com \
--cc=ecos-discuss@sources.redhat.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).