??? 01/24/07 06:56 Read: times |
#131355 - tried clr IE0... Responding to: ???'s previous message |
So I tried:
Interrupts_Init: clr IE0 mov IE, #0D1h mov IP, #0D0h mov IT01CF, #007h ret but that didn't work either. The only solution I have come up with (which I don't like simply because I don't understand what's wrong with the above) is to do mov IE, #0D0 (not enable external interrupt) in the Interrupts_Init and in the main code (after I do all this initialization) say setb EX0 (IE.0). Any explanation for the reasoning behind this would be much appreciated. Thanks, D |
Topic | Author | Date |
External Interrupt triggering on initialization | 01/01/70 00:00 | |
Simple! | 01/01/70 00:00 | |
yes, but..... | 01/01/70 00:00 | |
There's probably a good reason. | 01/01/70 00:00 | |
worth a shot...but | 01/01/70 00:00 | |
Understanding interrupts | 01/01/70 00:00 | |
Yes, I Know | 01/01/70 00:00 | |
terse response | 01/01/70 00:00 | |
tried clr IE0... | 01/01/70 00:00 | |
clr IE ?? | 01/01/70 00:00 | |
I do not use the SILabs deviates, but | 01/01/70 00:00 | |
Interesting.... | 01/01/70 00:00 | |
AH, now we get a good guess at the reason. The ex | 01/01/70 00:00 | |
Maybe it is the part | 01/01/70 00:00 | |
are you sure | 01/01/70 00:00 | |
hmmm..... | 01/01/70 00:00 | |
Hardware bug | 01/01/70 00:00 | |
down memory lane | 01/01/70 00:00 | |
INT0 is assigned to P0.1 as the default![]() | 01/01/70 00:00 |