linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andre Puschmann <andre.puschmann@tu-ilmenau.de>
To: linux-rt-users@vger.kernel.org
Subject: Re: Implementing real-time embedded system to sample from five SPI ADCs
Date: Thu, 04 Nov 2010 09:29:20 +0100	[thread overview]
Message-ID: <4CD26EE0.7040705@tu-ilmenau.de> (raw)
In-Reply-To: <4CD1EAF0.6030709@usask.ca>

Hi Nicholas,

according to what I understood, you want to use the data coming from 
your ADCs in a userspace application which implements the control loop.

I think there is a good chance you can then do all the steps (1)-(3) 
within an userspace application. However, I am not 100% certain about 
the best solution to implement (2) on this setup. May be anybody else
knows something about the maximum sample frequency, but this also 
depends on how complicated your algorithms are.

Here [1] you can find a good example on how to write a RT userspace 
application. Using the SPI character devices it should also be possible 
to talk to your hardware.

Regards,
Andre


[1] https://rt.wiki.kernel.org/index.php/RT_PREEMPT_HOWTO


On 11/04/2010 12:06 AM, Nicholas Kinar wrote:
> Hello,
>
> I would like to implement a real-time embedded Linux system on an
> AT91SAM ARM processor. Attached to the SPI bus of this processor are 5
> Analog-to-Digital converters (ADCs) that can be read using the Linux SPI
> bus subsystem.
>
> The ADCs are sampled by having the AT91SAM ARM processor toggle a GPIO
> at a rate of at least 1 KHz. The GPIO is attached to a pin on the ADC. A
> high voltage level on this pin instructs all of the ADCs to take a
> sample. The sample is then read over the SPI bus by the embedded system
> master. This implies that data will be read from each SPI slave device
> every (1 / 1000 Hz) = 1.0e-3 seconds.
>
> I am wondering if the following could be done with real-time Linux:
>
> (1) I would have to write a Linux kernel module to toggle the GPIO pin.
> The rate of toggling would be controlled by a high-resolution timer, and
> would occur with a period of at least 1 kHz.
> (2) After the GPIO is brought to a high voltage level, the master must
> wait for at least 3.7 microseconds before reading from the SPI bus.
> (3) Each ADC would be read in sequential order.
>
> The ADC being used is the AD7691 from Analog Devices
> (http://www.analog.com/static/imported-files/data_sheets/AD7691.pdf).
>
> The data from the ADCs could be used in a real-time control system loop.
> Can this be done with real-time Linux, or is the latency too high? What
> is the maximum rate at which I could read data from these ADCs? Could it
> be 10 kHz or even 100 kHz?
>
> Nicholas
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>



  reply	other threads:[~2010-11-04  8:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03 23:06 Implementing real-time embedded system to sample from five SPI ADCs Nicholas Kinar
2010-11-04  8:29 ` Andre Puschmann [this message]
2010-11-04 15:43   ` Nicholas Kinar

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=4CD26EE0.7040705@tu-ilmenau.de \
    --to=andre.puschmann@tu-ilmenau.de \
    --cc=linux-rt-users@vger.kernel.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 NNTP newsgroup(s).