• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 34 subscribers
  • Views 169 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.

DS90UB960-Q1: [Baolong] TARGET_ID and TARGET_ALIAS

Mingkang Song
Expert 3320 points
Part Number: DS90UB960-Q1

Tool/software:

Dear team,

Baolong met a problem when configuring 935+960. Could you pls help on this? Thanks!
1. After mapping two sets of I2C (6C and A0), only the sensor address 6C is recognized, and the E2PROM address A0 on the camera side cannot be recognized. Only after commenting out the sensor's I2C address mapping 6C can A0 be recognized.
2. After swapping the address mapping of 6C and A0, still only the 6C device can be detected.

Regards,

Mingkang

  • 0
    TI__Guru** 107970 points

    Hi Mingkang,

    This looks like a limitation on the I2C master (SoC) or on the I2C bus in the camera. Our SER-DES do nothing more than forwarding the data in both directions. We do not change or gate.

    Can you try using different Aliases for both devices? For example, 0x65 = 0x30, 0x66 = 0x32 and see if that helps.

    Also, please double check the I2C strap voltage, pull-up resistors on the camera
     

  • 0 in reply to Hamzeh Jaradat
    Prodigy 10 points

    Hi Hamzeh,

    I'm He Dong, a development engineer from Baolong. Regarding the above issues, we've carried out the following investigations.

    1.There are two devices connected to the I2C bus, namely the Sensor and the E2PROM. The address of the Sensor is 0x6C, and the address of the E2PROM is 0xA0. Their addresses do not conflict.

    Our configuration is as follows.

       0x5D,0x6C         // Remote Slave Sensor Device  ID
   0x65,0x6C         // Remote Slave Sensor  Device Alias ID
   0x5E,0xA0         // Remote Slave E2PROM Device ID
   0x66,0xA0         // Remote Slave E2PROM Device Alias ID

    2.Also, we have checked the hardware, and the I2C is pulled up to 1.8V with a 2.2K resistor.

    My question now is why the I2C addresses of the two devices can't be mapped simultaneously. Is it necessary to configure other registers?

    Best Regards,

    Dong

  • 0 in reply to Dong He
    TI__Guru** 107970 points

    Hi He Dong,

    Nice e-meeting you.

    If your system has the I2C master attached to the DES, i.e. looks like this: Imager / EPROM <--> SER <--> DES <--> SoC (I2C master), the only configuration you need is to define the IDx and Aliases on the DES as you are doing, and enable I2C Pass-Through in reg 0x58.

    There are no other configurations needed from our side.

    Please refer to these two app notes:

    SNLA131A_I2C Communication over FPD-Link III with BCC.pdf

    6886.SNLA222_I2C Over DS90UB913-4 FPD-Link III with Bidirictional Control Channel.pdf