Maurizio Crozzoli wrote
>
> Marcus Müller-3 wrote
>> So: you'll really have to define a maximum time that a GPIO toggle may
>> stay undetected. This shouldn't be hard -- I mean, in the end, there's
>> some application's needs that you'll want to satisfy.
> Is it a way to suggest me to use a sleep
Marcus Müller-3 wrote
> So: you'll really have to define a maximum time that a GPIO toggle may
> stay undetected. This shouldn't be hard -- I mean, in the end, there's
> some application's needs that you'll want to satisfy.
Is it a way to suggest me to use a sleep instruction during the poll loop?
Hi Maurizio,
> To be honest, currently I do not really know anything about the latency
> requirement. I would say that in this proof-of-concept stage of the design,
> the "best-we-can-do" approach could be acceptable.
well, in that case, I'd say: just go ahead and try with the polling
method. It
-Messaggio originale-
Da: Moritz Fischer [mailto:moritz.fisc...@ettus.com]
Inviato: lunedì 31 agosto 2015 19:35
A: Crozzoli Maurizio
Cc: discuss-gnuradio@gnu.org; Disco Daniele
Oggetto: Re: [Discuss-gnuradio] Front Panel GPIO on Ettus X310
Ciao Maurizio,
On Mon, Aug 31, 2015 at 9:03 AM,
Moritz,
if you wanted to scare me, you succeeded!
What you propose goes far beyond my current skills and it also looks
excessively complicated compared to my needs: really no easier way to detect an
external trigger?
Furthermore I cannot understand the meaning of the example in "The E3x0/X3x0
