i2c master/slave

[Luciano]

Hi!

Maybe these links will help you.
(Search with Google for more).

Microchip Application Note AN734:
Using the PICmicro SSP for Slave I2C Communication
http://www.microchip.com/stellent/i...ppnote=en011798

Picbasic Pro project for Slave I2C Communication:
http://www.astrosurf.com/soubie/pic_as_an_i2c_slave.htm
(See Microchip application note AN734 has errors).


Luciano

[mister_e]

Can someone explain to me why people choose I2C for a PIC to PIC comm when a simple serial comm is so much simple???

[Melanie]

Synchronous Communications (like I2C) is faster and more robust than Asynchronous Communications which in addition to wasteful Start and Stop Bits also requires stable clocks at each processor for fast data transfer. If you're already laying down an IC2 Bus for other devices, it seems logical to extend it to encompass your processors as well, and then your processors can happilly rely on internal oscillators freeing PIC pins. Remember that PICs internal oscillators are only guaranteed to be factory calibrated to 4MHz +/- 1% and regardlesswhat people say, that just doesn't cut it for Async speeds above 1200 Baud with any degree of reliability and repeatability... whereas I2C is happily interchanging data at between ten and forty times that speed without any regard to clock stability.

[mister_e]

That make sense. Thanks Melanie!