??? 03/20/09 14:16 Modified: 03/20/09 14:16 Read: times |
#163696 - Several options... Responding to: ???'s previous message |
There are several options:
As you told, by disabling the external interrupt and clearing the external interrupt flag in the interrupt service routine and later waiting for high state at /INT pin before activating the external interrupt again, or by using the edge triggered external interrupt, as Andy mentioned, or by inserting an /INT pin polling loop in the interrupt service routine and only leaving the interrupt routine, when the /INT input went high, which can result in a dramatic waste of time, of course. I guess this level triggered external interrupt with the interrupt flag not being cleared when serviced by the interrupt routine shall allow single-step operation for debugging. Kai |
Topic | Author | Date |
Question of level triggered interrupt | 01/01/70 00:00 | |
Edge Triggered Interrupt | 01/01/70 00:00 | |
Only Level triggered | 01/01/70 00:00 | |
It's not a "problem". | 01/01/70 00:00 | |
the problem is not technical... | 01/01/70 00:00 | |
Let me explain again | 01/01/70 00:00 | |
Idea | 01/01/70 00:00 | |
What the teacher wants... | 01/01/70 00:00 | |
Several options... | 01/01/70 00:00 | |
thats..... | 01/01/70 00:00 | |
May be you missunderstud | 01/01/70 00:00 | |
Use a while() trap | 01/01/70 00:00 | |
Yeah | 01/01/70 00:00 | |
Use a watchdog timer | 01/01/70 00:00 | |
How about this? | 01/01/70 00:00 | |
Wow | 01/01/70 00:00 | |
which derivative has this feature ? | 01/01/70 00:00 | |
Our friend the $ | 01/01/70 00:00 | |
Oooops![]() | 01/01/70 00:00 | |
Answer to my question | 01/01/70 00:00 | |
Thought about | 01/01/70 00:00 |