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.

RTOS/TDA2: SDK ov10635 I2C address not make sense with datasheet.

Part Number: TDA2

Tool/software: TI-RTOS

Hi Sir,

I find OV10635 salve device default address is 0x30.

But I found SDK use 0x38 to communication with OV10635. (Vision board cam1 <-> OV10635)

Why they are different? 

  • Hi,

    The lower 3 bits of the i2c address is controlled by GPIO[2:0]/SID[2:0] pins. so because of them, i2c address can change.

    Rgds,
    Brijesh
  • Hi Brijesh,

    Thanks for your reply.

    I know you mean. But same camera module just connect to different CAM port of vision board that will change I2C address of camera module.(Seem not relative with GPIO[2:0] or SID[2:0])

    FW log show SOC use 0x38 to communication with OV10635

    Do you know why use 0x38 (0x70 /2) ?

  • These are aliased I2C address. In case of multi-deserializer board, the sensor is connected to the serializer at the remote end through the FPD link. There is no sensors directly connected to the I2C bus on the EVM end. The communication is done through the deserializer, serializer and then to the sensor. We can program a suitable I2C address in the desrializer. Once the programming is done, any read/write to this aliased address is communicated to the remote sensor via the FPD link. The addresses are chosen in a such a way that it doesn't conflict with any of the I2C address connected to this I2C bus in the EVM side.
    For more details go through 913/914 reference manual.
  • Hi Sivaraj R3681,
    Understand.

    Many thanks.