0000410: I2C fails if accessed from different threads

ID	Project	Category	View Status	Date Submitted	Last Update

0000410	NetDCU9	I2C	public	2010-10-11 10:08	2013-11-14 14:07

Reporter	Keller	Assigned To
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	new	Resolution	open
Product Version	V1.19
Target Version	V1.29

Summary	0000410: I2C fails if accessed from different threads
Description	If I2C driver is accessed from different threads, i.e. different threads do SCHEDULE and GET_RESULT calls, then the driver suddenly stops to work and no visible output on the I2C signal lines can be seen anymore. The bus stays idle. On the other hand, no error is reported to the calling threads.
Steps To Reproduce	Program using two or more threads, each heavily calling SCHEDULE and GET_RESULT of the I2C driver.
Additional Information	Maybe the results are not mapped correctly to the threads waiting in GET_RESULT. Or two waiting threads are both woken up by the "Result available" event, both take the same single result and the internal queue gets confused. We have to check again for the thread synchronization. Working with one thread alone seems to work OK.

Forum Link
Found Driver Version	V3.3
Fixed Driver Version