Robert Soubie wrote:
> Has anyone written a working (tested and testable)
> application programmed either in asm, Basic or C where the
> PIC would be used as an i2c slave?

Yes, several times.

> Specifically some calls from the master, a PC using two
> different i2C interfaces, are not "seen"; I do not have the
> least idea of why...

Then find out why.  Put the master (the PC apparently) into a loop send the
address byte of the slave that is not responding.  Look at the result on a
scope.  Since it should be just a start, address byte, NACK, and stop, it
should fit nicely on one screen with one trace showing the clock and the
other the data.  Does everything look right?  This will differentiate the
problem to the PC or the PIC.  Particularly make sure the address is right,
proper timing is observed, etc.

> I program in Basic

Any further help is a waste of time until you get the compiler out from
between you and the hardware.  It's tough enough trying to remotely debug
somebody's setup without added uncertainty about what some bugware compiler
is doing.


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

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body