You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In principle, this is bad logic as we are asking for the start of an I2C write and then immediately asking for the star of an I2C read... however, despite being bad, it shouldn't crash (lock up) the logic. When Wire.receiveFrom is called in this example, it locks up and does not return. Nothing is transmitted on the I2C bus.
The text was updated successfully, but these errors were encountered:
This is because of my thread safety implementation in cases whan you have threads running and two threads want to write to the Wire bus. Need to investigate that a bit further and maybe try to distinguish the threads and only when there are two or more threads trying to access it, then it should lock in between (the second thread that wants to gain access)
I recently came across a sketch that had coded:
In principle, this is bad logic as we are asking for the start of an I2C write and then immediately asking for the star of an I2C read... however, despite being bad, it shouldn't crash (lock up) the logic. When
Wire.receiveFrom
is called in this example, it locks up and does not return. Nothing is transmitted on the I2C bus.The text was updated successfully, but these errors were encountered: