Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
06/20/08 12:11
Read: times


 
#156068 - Ok, I do recall, but
Responding to: ???'s previous message
Simutanous is the key word. So in that respect it there should not be any issues, but it still confused as to why when I toggle the INT1 pin to interrupt the MPU that it never breaks out to go to do the ISR call. INT0 does every time, but INT1 does not.

You had the ???? > Pin 9 of the 924 is SDA/INT0/P1.3 So if it is dedicated to the I2C bus, it can not be used as an input for the INT0 falling edge trigger. That is why I used Pin 8 INT1/P1.4. I think this is what the ???? was for?

I didn't have to program the pins as bidirectional, input, output or push pull for INT0 to work, I'm wondering if I have to do it for INT1 to make it an input???

It doesn't mention anywhere that this needs to be done and the standalone tests didn't need it either. Which is why I'm scratching my head. If the standalone tests didn't work then I'd be like yeah, I'm doing something wrong, but that isn't he case here.

I used this example to do the standalones and its from a "known" source:

http://www.keil.com/download/docs/188.asp

I changed the EX0 to EX1 and so forth and monitored the interrupt plugin, and they both worked the same way with some simple source in the ISR routine. I plug it back into my I2C receiver....nothing on INT1.

Any other thoughts Erik? Thanks
Chris


List of 5 messages in thread
TopicAuthorDate
Interrupt arbitration hardware issue/question            01/01/70 00:00      
   ??? and a misunderstanding            01/01/70 00:00      
      Ok, I do recall, but            01/01/70 00:00      
         Never Mind I figured it out            01/01/70 00:00      
         when in doubt, leave the pins in quasi            01/01/70 00:00      

Back to Subject List