• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 33 subscribers
  • Views 545 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

DS90UB953-Q1: RTOS/TDA2PXEVM: Serializer and Sensor not getting detected using I2C Back channel

DS90UB962-Q1: I2C Read/Write DS90UB953-Q1 through DS90UB962-Q1 Back channel

Sentinen.Chen
Expert 2415 points
Part Number: DS90UB962-Q1
Other Parts Discussed in Thread: DS90UB953-Q1,

Hi TI members:

I get one Sony IMX490 Camera Module (with use DS90UB953-Q1 serializer).

And our customer board have one DS90UB962-Q1 Deserializer.

So I try to connect IMX490 to DS90UB962. 

Right now, Our EE let DS90UB962 FPD-Link's Vpoc output is 10V / 0.3A.

After I connect camera module to DS90UB962-Q1,

I change belw DS90UB962 register value, 

i2cset -f -y 3 0x34 0x01 0x02 

i2cset -f -y 3 0x34 0x4C 0x01
i2cset -f -y 3 0x34 0x58 0x5E

i2cset -f -y 3 0x34 0x5C 0x18

After this,  I can see 0x5B register value is auto loaded as 0x30.

Please see below register dump value

root@j7-evm:~# i2cdump -y -f 3 0x34
No size specified (using byte-data access)
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 68 00 1e 40 d0 01 00 fe 1c 10 7a 7a 0f b9 00 ff    h.?@??.???zz??..
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 02    ..............??
20: f0 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ??..............
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
40: 00 a9 71 01 00 00 20 00 00 00 00 12 01 10 02 00    .?q?.. ....????.
50: 00 00 00 04 00 00 00 00 5e 00 00 30 18 00 00 00    ...?....^..0?...
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 7a 88 88    .............z??
70: 2b 2c e4 00 00 00 00 c5 00 01 00 00 20 00 00 00    +,?....?.?.. ...
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
a0: 00 00 00 00 00 1f 00 00 00 00 00 00 00 00 00 00    .....?..........
b0: 1c 3a 15 08 25 00 18 00 aa 33 83 74 80 00 00 00    ?:??%.?.?3?t?...
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 43 94 02 60 f2 00 03 00 00 00 00 00 00 00 00    .C??`?.?........
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 5f 55 42 39 36 30 00 00 00 00 00 00 00 00 00 00    _UB960..........

So far I think I should can use SER_ALIAS_ID to access DS90UB953

But I failed, no matter I use i2cdetect or i2cdump, the slave address 0x0C all have no response.

Does I miss any register config?

BR

Sentinen Chen

  • 0
    TI__Guru** 108100 points

    Hello Sentinen,

    are you using the same MODE configurations on both devices? They need to be in the same MODE to work.

    Do you have local I2C access to the SER?

    You need to check the device status in reg 0x04 ?

  • 0 in reply to Hamzeh Jaradat
    Expert 2415 points

    Hi Hamzeh:

    Thanks your information. 

    although we don't have local I2C access to the SER,

    But after compare 962 register table,

    I try to modify the 962 register 0x6D (PORT_CONFIG Register), and set FPD3_MODE to 00: CSI-2 Mode.

    Now I can detect 953 when i2c scan and dump 953 register value successfully.

    below is the 953 register 0x03 & 0x04 value 

    root@j7-evm:~# i2cdump -y -f 3 0x74
No size specified (using byte-data access)
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 30 00 33 48 00 03 41 28 fe 1e 10 7f 7f f0 0f 00    0.3H.?A(???????.

    BR

    Sentinen Chen