Issue 24: Migration: i2c http://code.google.com/p/jallib/issues/detail?id=24
Comment #4 by jsuijs: An other issue: In i2c, a slave device can the clock low when it needs a bit of time. It turns out that Stef's lib do not check for this. As a result, communication errors can occur when there is a slow device on the bus. I intend to use Wouters i2ci.jal, which does check for this. However I can't test if this realy works (don't know how to create such a slow situation). (I first thought this could hang the i2c bus. But that's not true: a slave can hang the i2c bus, wether the master checks for it or not. The other code does however change the behaviour of the master: the lib does not ignore the blocked bus any more, but blocks the i2c call...) Joep -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
