> I've not used the I2C module yet, however, it was my understanding
> that much of I2C is contained within the hardware.  I suspect that
> it's primarily interrupt driven.  From the I2C datasheet, I
> understand that all contention detection and arbitration is done in
> hardware.  My best advice for you at this point is to go through the
> datasheet for the 877 and set up what needs to be setup step by step.
>  After that, I believe that you could do it based on interrupts.  If
> it's only a 2 device bus, it should be easy to get everything
> working.  I recommend reading up on I2C, which you can do at the
> Philips website (grab the I2C spec from their buses section).  I
> expect someone else will give you more useful information

Before you get too far thinking that IIC will solve all communications
problems between PICs, note that the Microchip implementation only allows
for flow control from slave to master, not from master to slave.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.