Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
04/08/04 09:29
Read: times


 
#68160 - RE: Changing Interrupt Priority
Responding to: ???'s previous message
hi,
it is not need to change the priority of interrupts. There are others methods for you:
- you may completely disable all interrupts with CLR EA. This way none interrupt will be processed for that time while you do not allow them again with SETB EA;
- you may [temporally ]disable only that interrupt you do not need with. For example, if you do not need that timer 0 ISR has been executed then you just disable it with CLR ET0. This way timer0 still works but its ISR will be executed only after you allow it with SETB ET0 (if TF0 is set due the timer overflows).
- finally, there is "semaphore" system. This way you define a bit, let say BIT_DO_NOT_MODIFY_DATA which is set/reset inside timer2 ISR. ISR of timer 0 just checks this bit and if it is set then timer 0 does not modify your data. It may be useful when you does not need to "block" any interrupts because, for example, their accuracy timings (RTC, etc)

Regards,
Oleg

List of 6 messages in thread
TopicAuthorDate
Changing Interrupt Priority            01/01/70 00:00      
   RE: Changing Interrupt Priority            01/01/70 00:00      
   RE: Changing Interrupt Priority            01/01/70 00:00      
      RE: Changing Interrupt Priority            01/01/70 00:00      
         RE: Changing Interrupt Priority            01/01/70 00:00      
            RE: Changing Interrupt Priority -Thanks            01/01/70 00:00      

Back to Subject List