public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Vincent Leclaire <vleclaire@awox.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Maximum sampling rate
Date: Tue, 14 Oct 2003 17:19:00 -0000	[thread overview]
Message-ID: <1066151965.30453.115.camel@hermes> (raw)
In-Reply-To: <CE838B1FA9529449BDBA8951D3CD169F1560@sumatra.mop.awox.com>

On Tue, 2003-10-14 at 11:07, Vincent Leclaire wrote:
> 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) ?
> 

Is this some automatic sampling (i.e. triggered by an external clock or
timer), or must you do it "by hand?"  

If you have to do it manually, at these data rates, your processor 
won't be able to do much of anything except grab samples (one every 
2us).  I doubt that you could even write code which performs this
reliably:
  while (need_sample) {
    while (!sample_time) ;
    collect_sample()
  }
You might be able to use some sort of high speed timer to determine
"sample_time", but my guess is that you couldn't ask that question,
collect and store a piece of data and get around the loop again
fast enough (2us) to keep up.

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

  reply	other threads:[~2003-10-14 17:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-14 17:09 Vincent Leclaire
2003-10-14 17:19 ` Gary Thomas [this message]
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=1066151965.30453.115.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=vleclaire@awox.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).