Jump to content
Sign in to follow this  

Interrupt Timers - not always on time

Recommended Posts

I am using the interrupt timers to fire a function every 20 mSecs.  see this page on how to create an interrupt timer


Problem:  If I am running the interrupt software on its own, the interrupt is dead nuts on.  However, if I fire up a Mono application congruent to the C++ timer interrupt program, the Interrupt timer starts to drift -- and very badly.  As you know, Mono is not a fully compiled machine code application, and being inefficient as it is, there may be some blocking calls going on in Mono (beyond my control).

Question, is the interrupt timer in the pcDuino just a "poor mans" interrupt package, or is it truly a hardware driven interrupt off of the real time clock?  And if unfortunately it is the former, then if I hook a real input into the hardware driven interrupt routines in C++, am I sill going to have the same problems?


Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this