DS90UB914A-Q1：I2C communication with S90UB953-Q1 and DS90UB914A-Q1

Hello Steven.

Thanks to your quickly response!!

now your issue is that you can visit UB914a but can't visit UB953's i2c register, is it right?

 ->Yes. This is our problem.

1. please check what is the UB953's IDX, this is designed by the UB953's external circuit

  @ Yes.

2. read ub914a's reg. 0x06, this is ub953's IDX, is it correct or not?

  @ Yes. After Link up, We read ub914a's address 0x06 reg. 

      We get data 0x30.

    I mistook I wrote.

   [a:sensor]  <I2C >  [b:953]  <I2C>  [c:914]  <I2C>  [d:I2C Host Controller]

    slave address

        a:sensor = 0x1A

        b:953 = 0x18

        c:914 = 0x60 

Mabey I think  ub914a's address 0x06 is 0x30,  ub914a's IDX is 0x18 and the shift <<1(0x18 x 2 = 0x30)

3. write the alias idx of ub953 to ub914a's reg. 0x07.

  @ Yes. We write 0x30 to ub914a's address 0x07 reg. 

      Data 0x30 is getting ub914a's address 0x06 reg.

4. set the remote idx to reg. 0x8/0x10

  @  Mabey I think , write ub914a's  0x8/0x10 address to sensor's IDX(ub953's peripheral).

       Is it right?

if you can't read ub914a's reg. 0x06, pls check if the link is working or not? what is the DVP clock?

->We can read/write whole of ub914a's reg.

  UB953's  external clock is 50Mhz. 

We will continue to check the operation.

Are there any other possible problems?


Best regards.

Hello, Steven. Thank you for your reply

Our circuit block is the following.

 Our problem is I2C(No.2). can not access UB953's register via FPDL3 and UB914A from uPC.

 I2C(No.3) hasn't tried yet because I2C(No.2) doesn't work.

UB953's circuit is the following.

UB914a's circuit is the following.

1.UB953' circuit does not have a microcomputer.

   UB953's mode and SlaveID are specified from the external pin.

    MODE : Marking voltage 1.2V, DVP mode.

    SLAVE ID : 0x18

2. The uPC access whole of 914a's registers via I2C(No.1) .

    read data 0x30 from register 0x6.  (SER slave address, 0x18 <<1 shift = 0x30 )

    read data 0x03 from register 0x1C.(Link up & signal detected)

    write data 0x30 to register 0x7.(for access to 953's register)

3. The uPC tried to access  953's register by I2C.

    But all of response were NAK...

So in order to observe what is happening inside UB953, we connected the controller to the UB9537s I2C and checked the following registers.

read data 0x00 from register 0x52. 

So UB953 status is not "back chennel link detect",  "HS_PLL_LOCK" flag was bad condition and "RX_LOCK_DETECT" was different UB914A's status.

Maybe I think  there is something missing from the initial settings for 953.

I have some question.

Q1. On UB953' register 0x52, What should be the value of A for proper operation?
Q.2 Does the UB953 have contents to be set from the microcomputer?
Q.3 Is it safe to connect UB14A to UB953?

best regards

Hi, Steven

We tried to check, I found a problem.

I bought "DS90UB953-Q1EVM" and checked something.

UB953's 0x52 register was following.(ALP window)

( It works the same with my 953's camera )

It was good condition HS_PLL_LOCK, but LINK_DET and RX_LOCK_DETECT were bad condition.

Maybe I think, our problem was POC circuit, we tried to FPDL3 Link operation on non POC.

So we can access 953's register via FLDL3 cable and 914 from uPC.

As a result, there were no problems with mode settings or register settings.

Thanks to your sincere reply !

And we have new question.

Q.I think this issue is due to the influence of POC.

　We need POC(from 914's power source).

@914's POC circuit( the areas marked in green)

@934's POC circuit( the areas marked in green,"DS90UB953-Q1EVM" )

Please I need some advice for specific parameters for POC between UB914 and UB953.

best regards,

Hiroshi Kamizono