And what that means is if you really want to have the interrupt on
change you can kiss off using PORT B for anything else.  What a waste of
port bits.  Bin ther, dun thet, don't want a tee shirt.

John

> "The PIC16C6X datasheet says that under certain conditions,
> Change-On-PortB interrupts may be missed. Is this true?
>
>  Yes. If the change occurs just as PORTB is being read, the
> interrupt flag  won't be set and no interrupt will be
> generated. What many people don't  realize is that every
> instruction that accesses PORTB will read it.
>
>  The upshot of all this is that you can't really depend on
> the  Change-On-PortB interrupt to be reliable for anything
> other than  waking-up the processor from sleep mode.
>
>  Sucks, don't it?"
>
> --
> http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu