Hi Larry-
Thanks for responding.
I do not write to flash during acquisition. At one time I did (and that did
cause problems).
I introduced the 6MB array so I could avoid writing to flash until all reads
from
/dev/gps_pps were done. The program I posted (see original post) basically
reads from
/dev/gps_pps and stores in an array. And that's the only thing it does which
is time
critical. And yet I still get dropped interrupts.
I can't help thinking that the kernel goes off to do something every once in a
while and
doesn't return when my 1Khz interrupt comes. I believe the interrupt in the
kernel driver
is set to 59. Would changing this number help?
Thanks,
Peter
--- In Larry <> wrote:
>
> Could be the same issue I mentioned on another post where the poster was
> missing serial characters.
> Just for a test, make sure logging is disabled, or that it's logging to
> ramdisk.
> I've seen issues with writing to flash stalling operation for long
> enough to miss interrupts.
> If you are writing to the flash file system anywhere, it will eventually
> be flushed to flash.
> This process takes some time and I don't know the details, but it can
> take on the order of
> milliseconds or even longer. Maybe someone at TS can elaborate?
>
> Larry
>
> pgb_psu wrote:
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|