How much work do you want to put in? The Philips PCF8584 is capable of spying on the I2C bus. I built a board with an 8051 and a PCF8584 (and a max232) and made a device that basically spies on the I2C and dumps the bytes it sees to the RS232 port (for collection on a PC or wherever). A logic analyzer can do the trick too. We use a PC-based LA here, but my "I2C Snooper" gets used every once in a while. See also http://www.mcc-us.com/index.html They might make something similar. GB ----- Original Message ----- From: "Jon M (Mike) Jones" To: Sent: Tuesday, January 21, 2003 3:04 PM Subject: Re: [PIC]: I2C debugging > I faced the same problem a year or two ago. My solution was to connect the > 16F877 to a 'know' good slave such as a DS1307 clock chip and started > debugging from there. > > Mike Jones > pmjones3@attbi.com > ----- Original Message ----- > From: "Lennart Sundberg" > To: > Sent: Tuesday, January 21, 2003 1:24 PM > Subject: [PIC]: I2C debugging > > > Hi > I have implemented an I2C routine in a 16F877 for communication to > another board with a PIC. But how do I know if my I2C routine is working > correct before I build up the other board. How can I do this? > I have looked around on the web and found a lot of I2C test equipment > but I don't want to pay a lot of money for some extra hw, that may be of > little use for me in the future. > Could you recommend a low cost debugger or how to test the I2C. > > -- > http://www.piclist.com hint: To leave the PICList > mailto:piclist-unsubscribe-request@mitvma.mit.edu > > -- > http://www.piclist.com hint: To leave the PICList > mailto:piclist-unsubscribe-request@mitvma.mit.edu > -- http://www.piclist.com hint: To leave the PICList mailto:piclist-unsubscribe-request@mitvma.mit.edu