1
Discussion - Drivers / FT4222_FAILED_TO_READ_DEVICE ... every now and then.
« on: March 28, 2024, 09:19:04 PM »
We have systems communication over I2C with a Windows machine acting as master. The system will chug along doing millions of messages over weeks or months just fine, or it may run for a few hours then get an FTDI error. When this happens, the program is usually locked up (spinny blue donut) and we have to force quit or restart Windows.
When that happens, I do not expect there is anything we can do about it.
But other times, we'll sometimes get back the error 1011 (failed to read device) error and not lock up, but all further I2C writes will be failing with errors.
Do we have any hope of finding a way to prevent this from happening?
When that happens, I do not expect there is anything we can do about it.
But other times, we'll sometimes get back the error 1011 (failed to read device) error and not lock up, but all further I2C writes will be failing with errors.
Do we have any hope of finding a way to prevent this from happening?