View Single Post
  #11   Spotlight this post!  
Unread 07-03-2004, 23:07
KenWittlief KenWittlief is offline
.
no team
Team Role: Engineer
 
Join Date: Mar 2003
Location: Rochester, NY
Posts: 4,213
KenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond repute
Re: Nesting Interrupts - is it possible?

in this pic chip when an interupt occurs a flag is set for that interrupt - so even if a higher priority interrupt is being processed at the time

and the source of the second interrupt goes away

it will not be lost, the flag will remain set until that interrupt is serviced.

Its very rare that you need to allow interrupts to be interrupted

SW should be designed as if all these things will be polled - if you dont have time to poll the conditions, you dont have time to service interrupts either

and if you dont know how often all your different interrupts can happen, your code is likely to be buggy and unpredicable.

Design your system (SW) as if you dont have interrupts, and then use the interrupts as a convience only.