Barry Gershenfeld wrote:
> The problem then was, I would get one interrupt (when the slave saw
> its address) and then nothing afterward.

What did you expect?  You only addressed the slave once, so got one
interrupt.

> Turns out, I have to read the "received byte".

Of course, especially with slaves that do clock stretching.  How else would
the hardware know you got it and it was OK to proceed?  I'm pretty sure
other IIC implementations work similarly, although I often do IIC in
firmware.  It's one of the first things to give up in hardware if you need
the dedicated pins for something else.  If I remember right, your PIC has
remappable pins, so that's less of a issue.


********************************************************************
Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
(978) 742-9014.  Gold level PIC consultants since 2000.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist