DS90UB913A-Q1: Connection problem with DS90UB954 using STP and CLOCK from Imager mode

RoyChen776

Part Number: DS90UB913A-Q1

We have some issues on ds90ub954, connect to ds90ub913. and the 913 is using PCLK from imager mode.

The lock signal is high, and we can get 913 address by using "Enable Pass through (write 0x58,0x58)"

But we can not ack the EEPROM and Imager. even we set reg 0x58=0xd8, the imager and EEPROM still no ack.

-EEPROM and imager can be ack by connected to our back-end system.
even we set reg 0x58=0xd8, the imager and EEPROM still no ack.

-We have designed several camera systems by using 913 and 954, but this is our first time for using STP+PCLK from imager mode

hope we can get some more information in here. Thanks.

//Enabled FWD for RX Port 1, disabled FWD for RX Port 0
w 0x20,0x10

//"FPD3_PORT_SEL" board.WriteReg(0x4c,0x12) # RX_PORT1
w 0x4c,0x12

//enable pass throu
0x58,0x58

# setup Serializer alias

//SER_ALIAS_ID 0x5c value ", hex(board.ReadReg(0x5c))
0x5c,0x18

# setup image sensor alias

# set image sensor ID
0x5d,0xc0

# map image sensor ID to 0xc0
0x65,0xc0

# setup EEPROM alias

# set EEPROM ID
0x5e,0xa0
# map EEPROM ID to 0xa0
0x66,0xa0

0 Steven(Shenzhen) Shi over 6 years ago

Hello,

some points for your reference:

1. 913/954 has same I2C communication setting as 953/954. Also, the "STP+PCLK selection" does NOT impact the I2C access in normal operation.

2. The i2c setting has no problem, you are selecting the port1's camera, and use the remote I2C alias ID 0xa0 and 0xc0 (these IDs are correct?)

3. pls check the link bit error: ub954's 0x4d/4e, and 913a's 0x0a/0x0b reg. (crc checking)

4. can you measure the SCL/SDA in 913A side to check whether the SCL/SDA signals in 954's pins can be transmitted to 913A side

regards,

Steven

Interface forum