ok. Thanks. That actually does answer my question.
On 6/24/06, Dave Hylands <firstname.lastname@example.org> wrote:
> I don't think i was very precise with my NACK question.
> In the case that the master fails to recieve a signal, a NACK will be
> returned in like 8 clock cycles (Im not sure about 8 but w.e). So the
> question is: is the data transmission consistent, i.e will data packets
> dissapear and I will get back NACKs when I just sent a byte of data or will
> it be like I sent a byte and get an ACK (if the where I am sending is
> expecting data) no matter what?
I don't understand what you mean by consistent.
i2c doesn't specify any NACKs other than the ones I mentioned (where
it uses a NACK on a byte by byte basis).
i2c has no notion of retrying. You need to build this layer yourself
if you want (although this would only work for devices where you can
control both sides).
i2c also has no notion of message integrity. SMBus introduces a CRC,
but the way its implemented only partially ensures message integrity.
Vancouver, BC, Canada
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server
v.1.0.1 based on Apache Geronimo
gumstix-users mailing list