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.

UCD90160: 35ms Communication Timeout

Part Number: UCD90160

Dear Sir/Madam,

We are encountering periodic Communication errors while reading the Voltage rails from a UCD90160.

We normally see some clock stretching on read operations.

Occasionally we see clock stretching for 35ms on read operations. 

After 35m and the clock is released, our driver completes the read and the data returns 0xFF, 0xFF as expected after the abort.

The next command appears to function correctly.

We have tried adding 1.1ms between commands, this reduces the error rate, but they still occur.

 What can cause the UCD90160 to abort a Command?

Thank you,

Mark

  • Hi

    First, did you host support clock stretching? without a clock stretching from host, the communication could not be reliable. 

    Could you pleas provide the scope capture of the followings, especially before the timeout?  I need a scope capture instead of capture from analyzer

    Regards

    Yihe