??? 03/20/09 19:02 Read: times |
#163707 - thats..... Responding to: ???'s previous message |
Exactly what i thought, but there is a problem....
You said: at begining interrupt is active - a low level in input produces interrupt - the service routine disables the interrupt - interrupt makes its work... - executes a RETI - the main program (or some periodic interrupt: timer) checks the input and reenable interrupt when pin is high I mean the microprocesor when you stablished yor TCON for interrupts it will do check every machine cicle the port you stablished at the start, i mean for every instruction done in the MAIN program it will check the port INT0 or INT1 for external interrupts, but what if the after the low level he detects another and another, over and over, cuz its in low for example 1hour? |
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 |