This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DLPC3478: Instability issues, i2c communication fails after some hours of operation

Part Number: DLPC3478

We have observed from time to time that we need to restart the DLPC3478 chip because it stops responding to I2C commands. This has been difficult to reproduce, especially on the TI devkit, but now we have a way of reproducing on the TI devkit. If we just run the ReadValidateExposureTime() command in a loop it will stop responding after some hours. The python API responds back with "Read Validate Exposure Time Command Execution Failed". Please see attached python example.

8_255_read_timings.zip

  • Anders,

    With some commands which cause the DLPC3478 the fetch data from memory (such as on the external SPI flash device) there is a period during which the DLPC device is busy and cannot accept additional I2C commands. In these cases, sending too many commands too quickly may cause the bus to hang up.

    Have you tried adding a short delay to the Python commands you are using? You can confirm whether the above is contributing to your issue by doing so. I recommend starting with a larger delay of ~0.8 seconds and reducing it if you do not see problems.

    Best Regards,

    Philippe Dollo