I discovered a "lapse of implementation" in the T1 atmega I2C implementation, which is BTW entirely done in bit-banging software. I don't use or have access to a T2 tree and haven't looked at the MSP implementation, but I might be able to help if you describe your problem.
My problem was when reading multi-byte data from an I2C device. According to the spec the slave can request a "wait-state" between bytes. The TOS code was ignoring this and getting out of bit sync. MS Tommaso Montisci wrote: > Hi all, > > I'm working to write TinyOS 2.x drivers for a 3-axiss digital > compass(HMC6343). > This sensor communicates via a two-wire I2C bus system as a slave divice > with a microprocessor MSP430. > > I would like to know if someone just working in similar context couse > I'm in trouble to recive the ack from the compass. > > Thanks, > > Tommaso Montisci. > > > ------------------------------------------------------------------------ > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
