• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 32 subscribers
  • Views 187 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

DS90UH948-Q1: DS90UH948-Q1 I2C Detect Problem

Brown Weng
Prodigy 50 points
Part Number: DS90UH948-Q1
Other Parts Discussed in Thread: DS90UB948-Q1EVM

Tool/software: 

DS90UB947 Setting:(1)Single-pixel OpenLDI interface, (2)Disable repeater mode, (3)SPWG bit mapping, (4)Enable FPD-Link III for twisted pair cabling.
DS90UH948 Setting:(1)Single-pixel OpenLDI interface, (2)Disable repeater mode, (3)SPWG bit mapping, (4)Enable FPD-Link III for twisted pair cabling.
The independent test result of DS90UH947 is successful and the driver can read successfully, but after connecting to DS90UB948 via Cable,
it is found that the I2C error is displayed in the log as follow:

[   13.367146] [   T7] ti948 2-002c: Failed to read device id. (error -6) 

  [   13.374691] [   T7] ti948 2-002c: ti948_device_check

  [   15.401791] [   T7] ti948 2-002c: Failed to read device id. (error -110)

[   15.409506] [   T7] ti948 2-002c: ti948_device_check

And there would be error messages continue to appear that I2C is pulled Low. A small piece of log captured as follow:

[  232.522893] [ T1787] i2c-rcar e6510000.i2c: error -16 : 16

[  232.528642] [ T1787] i2c i2c-2: SCL is stuck low, exit recovery

[  232.534520] [ T1787] i2c-rcar e6510000.i2c: error -16 : 16

[  232.540271] [ T1787] i2c i2c-2: SCL is stuck low, exit recovery

[  232.546178] [ T1787] i2c-rcar e6510000.i2c: error -16 : 16

[  232.551931] [ T1787] i2c i2c-2: SCL is stuck low, exit recovery

[  232.557831] [ T1787] i2c-rcar e6510000.i2c: error -16 : 16

[  232.563567] [ T1787] i2c i2c-2: SCL is stuck low, exit recovery

[  232.569461] [ T1787] i2c-rcar e6510000.i2c: error -16 : 16

[  237.284245] [ T1796] i2c-rcar e6510000.i2c: error -110 : 11

[  239.396432] [ T1796] i2c-rcar e6510000.i2c: error -110 : 11

[  239.402547] [ T1796] i2c-rcar e6510000.i2c: error -11 : e

You could see that I2C briefly detected DS90UH948 (0x2C) on the Display board through the command in software,
but the 948 Driver cannot correctly probe the components.

[   13.367146] [       T7] ti948 2-002c: Failed to read device id. (error -6)

[   13.374691] [        T7] ti948 2-002c: ti948_device_check

[   15.401791] [        T7] ti948 2-002c: Failed to read device id. (error -110)

[   15.409506] [        T7] ti948 2-002c: ti948_device_check

 

  • 0
    TI__Genius 13790 points

    Hi Brown,

    I may be able to assist with this I2C connection to the DS90UB948.

    Brown Weng said:
    but after connecting to DS90UB948 via Cable, it is found that the I2C error is displayed in the log as follow:

    Can you provide more information about this ;

    • Is this using a DS90UB948-Q1EVM, or custom board?
    • What is the interface for this cable, is this pinout directly to SCL and SDA of the device, or via USB/other connection?
    Brown Weng said:
    And there would be error messages continue to appear that I2C is pulled Low. A small piece of log captured as follow:

    Are you able to capture the SCL and SDA signals directly with a scope or a logic analyzer? I would like to confirm if the hardware is also representing this error on a waveform.

    Brown Weng said:
    You could see that I2C briefly detected DS90UH948 (0x2C) on the Display board through the command in software,

    How often does this occur, and what is the reproduction rate (out of a total number of cycles while testing)?

    Does this phenomenon happen on a number of units, or just one?

    Best,

    Miguel