??? 06/07/06 03:31 Read: times |
#117919 - IE0 does not need EX0 enabled Responding to: ???'s previous message |
Yes, IE0 will latch edges even when EX0 is not enabled. You can use this feature to tell you if an edge has occurred in a particular interval without having to use any other resources.
The disabling EX0 at the beginning of the ISR and then reanabling it at the end as you have done has zero effect because you can't be reinterrupted (unless you play with the priority settings during the ISR). Stanley Lio said:
By the way, how would you consider one routine as a LONG one? Because it is spending such a substantial amount of time in the ISR (receiving the entire IR pulse) effectively destroying any other ISR concurrency. Only in very particular circumstances would I consider a design like this. |
Topic | Author | Date |
Receiving IR remote control code | 01/01/70 00:00 | |
What I would do | 01/01/70 00:00 | |
not the protocol | 01/01/70 00:00 | |
Not clearing IE0 | 01/01/70 00:00 | |
IE0 | 01/01/70 00:00 | |
IE0 does not need EX0 enabled | 01/01/70 00:00 | |
band-aids | 01/01/70 00:00 | |
timer in capture mode | 01/01/70 00:00 | |
"Long" pulses? | 01/01/70 00:00 | |
never use before![]() | 01/01/70 00:00 | |
how to prevent IE0 set | 01/01/70 00:00 |