Errr....ummm...what can I say....obviously my keyboard is putting in the wrong words again :o) *MASTER* mode is pretty easy to implement in software...... I had this exact problem though. I looked at the datasheet in it mentioned I2C support, so I thought,"great, just the job". It isn't at all obvious that *only* slave mode is supported in hardware. In fact, it took me ages to convince one of the engineer here that it didn't. I just let him find out for himself in the end! Cheers Mike Rigby-Jones > -----Original Message----- > From: jamesp@intertex.net [SMTP:jamesp@intertex.net] > Sent: Thursday, July 29, 1999 9:17 AM > To: Rigby-Jones, Michael [PAI01:4837:EXCH] > Subject: Re: Re: Adventure in realtime: PIC and the lost register > > > I must be missing something here. Are you saying that "SLAVE > MODE" is pretty easy to implement in software but "SLAVE MODE" > is hard to implement in software. That's why it's done with > hardware? Am I halucinating? I knew that coffee tasted funny > this morning. :-) > > Regards, > > Jim > > > > >Unfortunately you have to implement I2C master in software on most > midrange > > >PICs. > >I agree that slave mode is the one most people use, but it is also pretty > >easy to implement in software. Slave mode is very hard to do in software > >which is why the hardware supports this mode. > > > >Cheers > > > >Mike Rigby-Jones > > > > > >> -----Original Message----- > >> From: Andy Koessler [SMTP:Andreas.Koessler@ASCOM.CH] > >> Sent: Thursday, July 29, 1999 9:47 AM > >> To: PICLIST@MITVMA.MIT.EDU > >> Subject: Adventure in realtime: PIC and the lost register > >> > >> In the datasheet (reference_manual_DS33023) for PIC16/17 microchip > refer > > >> to a > >> register called SSPCON2. > >> This is used to set the PIC16Cxx as an I2C MASTER (which is the most > >> important > >> mode I think). It gives controll for all the protocoll handles like > ACK, > > >> NAK, > >> arbitration etc. > >> In the explizit datasheet for the 16Cxx this register ist missing. In > the > > >> reference manual they describe how to deal with it but don't write > which > > >> adress > >> it's got. They refer to the AN578 and AN554 - all I see in this I don't > >> want to > >> use! > >> > >> Do I really have to implement the I2C protocoll like there is no > special > > >> feature for this ?? (I really could do this on any pin of any port on > any > > >> microcontroller - why I bought the PIC?) > >> > >> Angry Andy (Newby, but I think I'm not going old with PIC...) > > >