Chief Delphi - interupts 3-6??

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)

- Programming (http://www.chiefdelphi.com/forums/forumdisplay.php?f=51)

- - interupts 3-6?? (http://www.chiefdelphi.com/forums/showthread.php?t=52709)

I am currently trying to develope some code for multiple encoders and I need to use interupts 3-6

I have some code from kevin watson's site and it works, but I don't know why

How do you differentite between the interupt 3-6 even though it is the same register?

thanx

Re: interupts 3-6??

3-6 are interrupt-on-change, so they interrupt when anything on there changes. Kevin's code determines which pin changed by saving the old state of the port. You XOR the old port state with the current port state to see which bits have flipped and act accordingly. Then you save the current port state as the old port state (that you'll use the next time it interrupts).

Re: interupts 3-6??

so what you are saying is that INTCONbits.RBIF (RB Port Change Interrupt Flag bit) is actually a set of bits instead of just a single one?

or are you checking secondary bits to detrmine which pin is flagged after the RBIF is a 1?

Re: interupts 3-6??

RBIF is a single bit that tells you that some bit in PORTB (the state of all the interrupt 3-6 pins) has flipped. You actually have to read PORTB before RBIF can be cleared. So now that you have the current value of PORTB, you compare it to the value of PORTB the last time something changed, and that tells you what's changed to cause this interrupt.

Re: interupts 3-6??

couldn't you just look at the specific pin to see if it is the pin that is activated?

such as

Quote:

if(INCONbits.RBIF)
{
if(PORTBbits.RB7)
{
yadda yaddaa
}
if(PORTBbits.RB6)
{
yadda yadda
}
etc. etc.
}

I've been muddling through the pic18f8722 data sheet and I think that PORTB is just another set of bits that refer to the pins RB0 thru RB7. Is that a valid way to isolate the interrupts in INTCONbits.RBIF?

Re: interupts 3-6??

I think you have to read the entire port to be able to clear the flag, but reading a single pin might work. What happens is if you don't clear the mismatch by reading the entire port, or maybe reading one pin, is the flag continues to be set over and over, and you'll keep jumping back into your ISR. So if you try your way and get a red light of death, you'll know why.

Second point. Your method works if you only care about 0 to 1 transitions on the pin. 1 to 0 transitions will still cause interrupts and you'll still have to service them, however. So using interrupts 3-6 when you only care about 0 to 1 transitions is pretty wasteful of your resources and you'll only be able to service half as many interrupts as you'd other wise be able to.

Re: interupts 3-6??

What if some other pin changed on the port and that pin was already high (it was high before and is continued to be high) that would give a false impression of that pin changing, right?

Re: interupts 3-6??

ummmm.. true. a good point. missed that one.

Re: interupts 3-6??

John, Kevin, Gustavo, et al,

Look at Kevin Watson's example here. Look at the way he uses the static variable "Old_Port_B" in user_rourtines_fast.c and you will begin to understand...

Regards,

Mike

Re: interupts 3-6??

Quote:

Originally Posted by Joohoo (Post 564838)

This is the code Mike is referring to:

-Kevin

Code:

 

if (INTCONbits.RBIF && INTCONbits.RBIE) // external interrupts 3 through 6?

 {

 

// This does two things. First we grab a copy of PORTB, which 

// contains the states of the four interrupts. Secondly, reading

// this register resets an internal flag that would otherwise cause 

// another interrupt to fire-off when you cleared the interrupt 

// flag in the next instruction...

  Port_B = PORTB;          

 

// This clears the interrupt flag, informing the processor that you've

// handled the interrupt

  INTCONbits.RBIF = 0;

 

// This line of code updates a variable using the exclusive-or operation.

// If the state of one of the interrupts has changed between the last

// time this function was called and now, a bit in Port_B_Delta will be

// set to one, signaling that that interrupt service routine needs to be

// called

  Port_B_Delta = Port_B ^ Old_Port_B;

 

// Now that we know which inputs have changed, save a copy of the

// current state so we'll know which one(s) changed next time.

  Old_Port_B = Port_B;

 

// This checks to see if the bit associated with interrupt 3 has changed

// and if it has, call the interrupt service routine

  if(Port_B_Delta & 0x10)

  {

// Call the interrupt 3 handler and include the current state of the

// interrupt pin. The wacky bit of code "Port_B & 0x10 ? 1 : 0" is the

// same thing as:

//

// if(Port_B & 0x10)

// {

// return(1)

// }

// else

// {

// return(0)

// }

// This is done to ensure the value sent into the interrupt

// handler is either 0 or 1.

   Int_3_Handler(Port_B & 0x10 ? 1 : 0);

  }

 

// Each one must be checked individually because more than one may

// have changed

  if(Port_B_Delta & 0x20)

  {

   Int_4_Handler(Port_B & 0x20 ? 1 : 0);

  }

  if(Port_B_Delta & 0x40)

  {

   Int_5_Handler(Port_B & 0x40 ? 1 : 0);

  }

  if(Port_B_Delta & 0x80)

  {

   Int_6_Handler(Port_B & 0x80 ? 1 : 0);

  }

 }