Hi. The issue with holding the clock line low is I have multiple slaves, so I don't think the master will get a word in inchwise with all the slaves pulling the clock low...
|
Hi. The issue with holding the clock line low is I have multiple slaves, so I don't think the master will get a word in inchwise with all the slaves pulling the clock low...
|
Yes, with muli slaves that could get nasty. I thought about that but had re-read your first line in the top post and it said 2 pics. I thought this was just a 2 pic i2c system.Originally Posted by cpayne
No, I'm not Superman, but I did stay at a Holiday Inn Express last night!
|
Yes, I am trying to get two working for now, then as soon as I get one good slave, I plan on adding...
|
Maybe I'm missing something, but it looks like you are polling for the Interrupt Staus Bit in MAIN, and when it is set, you go off and read the receive register. Because you are using a polled operation, not an interrupt-driven one, you can't catch data as soon as it arrives. If you use Darrel's Instant Interrupts and make your I2C routine an ISR, you should be able to receive data any time - even halfway through an A/D conversion.
Charles Linquist
Members who have read this thread : 0You do not have permission to view the list of names.
Posting Permissions
Bookmarks