Jump to content


Photo

Interrupt Timers - not always on time


  • Please log in to reply
1 reply to this topic

#1 jim

jim

    Advanced Member

  • Administrators
  • 3,385 posts

Posted 13 February 2015 - 07:11 PM

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

http://learn.linkspr...upt-on-pcduino/

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?

Thanks,
HH



#2 jim

jim

    Advanced Member

  • Administrators
  • 3,385 posts

Posted 13 February 2015 - 07:12 PM

So I infer from your post, there is no non-maskable interrupt on the pcDuino board?   sad.gif






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users