??? 01/25/07 13:08 Read: times |
#131464 - AH, now we get a good guess at the reason. The ex Responding to: ???'s previous message |
Does what you're stating hold regardless of the state of the signal on the I/O pin?
no, an external signal driving the pin high is a form of a "pullup" (not by standard meaning of the word, but it does "pull the pin up") Either way setting EX0 "later" in the assembly seems to fix the issue. It just strikes me as strange/I'm annoyed that I don't understand why my original code doesn't work. AH, now we get a good guess at the reason. The external signal does not go high fast enough after reset. Erik |
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 |