Sandip Bapat wrote:
a DAC module would either have to wire to Msp430RefVoltArbiterP (in which case
it also has to provide the
AdcConfigure interface) or be expected to provide wiring for these interfaces.
This is fine for apps that just want to use the DAC and not ADC but what if
both are us
The access to the refvolt generator has to be properly arbitrated between
the ADC and the DAC. Pins, timers, etc. are all potential shared resource
between the two. Jan, who is responsible for the msp430 ADC stack, is at a
project meeting and probably has not read the thread. Please get in touch
wi
Currently Msp430RefVoltArbiterImplP intercept the requests of ADC
clients to the Resource interface, it is not really arbitrating access
itself. If the DAC needs access to the RefVolt component too, then we
might need a real arbiter for the RefVolt component that is
independent of the actual ADC ar
Jan,
In the latter approach you outlined, where they share the same arbiter, if we
assume that the ADC and DAC require the same reference voltage, would they
still not be able to run in parallel?
Here's one scenario which might be common to a lot of sensing apps: An app uses
RefVolt via Msp43
> In the latter approach you outlined, where they share the same arbiter, if
> we assume that the ADC and DAC require the same reference voltage, would
> they still not be able to run in parallel?
By parallel I meant "at the same time": in the second approach if two
components would request to use
I like Sandip's idea to create an arbiter that reserves use of refvolt to the
first
process that asks, but also responds to queries about the refvolt value.
Do arbiters as they are now allow for keeping a queue of asking routines
satisfied
with a resource with no breaks?
Would a shared arbiter
What we really need I think is a way of allowing the reference voltage
component have "multiple" owners simultaneously. Most components that
provide the Resource interface are used to grant exclusive access to a
device that is used to perform some operation. The reference voltage
component is a b
I don't really like the idea of having two arbiters (one for ADC and
one for DAC) and in addition another one for RefVolt, because that
would force (some) clients to make two successful requests before they
can actually start their operations. We have never really discussed
this, but resource starv
If you don't have separate arbiters for the ADC and the DAC how can
you ever allow them to perform operations in parallel? And this sort
of cascading through multiple levels of arbitration happens all the
time. Think about how the flash drivers on telos work. There is
arbitration to the flash op
> If you don't have separate arbiters for the ADC and the DAC how can
> you ever allow them to perform operations in parallel? And this sort
> of cascading through multiple levels of arbitration happens all the
> time. Think about how the flash drivers on telos work. There is
> arbitration t
Why would you ever allow AdcClient2 to successfully be granted the ADC
before it was granted the RefVolt? You would need to make sure that
it had access to the refvolt before signaling a granted for the ADC
woudn't you?
Kevin
On Fri, Feb 15, 2008 at 1:45 AM, Jan Hauer <[EMAIL PROTECTED]> wrote:
> Why would you ever allow AdcClient2 to successfully be granted the ADC
> before it was granted the RefVolt? You would need to make sure that
> it had access to the refvolt before signaling a granted for the ADC
> woudn't you?
If we have separate ADC, DAC and RefVolt components/arbitration th
Sure I guess I was just assuming the wrapper approach then
Kevin
On Fri, Feb 15, 2008 at 2:33 AM, Jan Hauer <[EMAIL PROTECTED]> wrote:
> > Why would you ever allow AdcClient2 to successfully be granted the ADC
> > before it was granted the RefVolt? You would need to make sure that
> > it
On Feb 15, 2008, at 1:45 AM, Jan Hauer wrote:
If you don't have separate arbiters for the ADC and the DAC how can
you ever allow them to perform operations in parallel? And this
sort
of cascading through multiple levels of arbitration happens all the
time. Think about how the flash driv
Thats fine, but I think the point is that if the ADC reading you are
about to take needs to use the refernece voltage, access should NOT be
granted to the ADC until access to the reference voltage has been
granted. If you use VCC, you don't need to wait for this. The
information about which volta
On Feb 15, 2008 7:59 PM, Kevin Klues <[EMAIL PROTECTED]> wrote:
> Thats fine, but I think the point is that if the ADC reading you are
> about to take needs to use the refernece voltage, access should NOT be
> granted to the ADC until access to the reference voltage has been
> granted. If you use
Philip Levis:
On Feb 15, 2008, at 1:45 AM, Jan Hauer wrote:
If you don't have separate arbiters for the ADC and the DAC how can
you ever allow them to perform operations in parallel? And this sort
of cascading through multiple levels of arbitration happens all the
time. Think about how th
On Feb 15, 2008, at 10:48 AM, Andreas Koepke wrote:
Philip Levis:
On Feb 15, 2008, at 1:45 AM, Jan Hauer wrote:
If you don't have separate arbiters for the ADC and the DAC how can
you ever allow them to perform operations in parallel? And
this sort
of cascading through multiple levels of
18 matches
Mail list logo
