Datasheet, section 10.3.1 and later will give you the answer
Datasheet, section 10.3.1 and later will give you the answer
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Well as I read it, the only time a NACK is sent for valid data is when the Master is requesting a sequential read. The Master sends a NACK on the last read to say he is done. But there is no reason why the Master couldn't ACK the last read and then send a STOP. Also note that the NACK/ACK is sent by the master on a read, not the slave.
Tim Barr
Have you looked here?
http://www.picbasic.co.uk/forum/content.php?r=69
Dave
Always wear safety glasses while programming.
Bookmarks