• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 40 subscribers
  • Views 847 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TIDA-00421: Serializer Physical Address

Blessy Abraham
Intellectual 585 points
Part Number: TIDA-00421

Hi,

There is an address mentioned in the schematics, tidrjx7 (OV10640 interface with Serializer) - 0111101x. Is this the address of the serializer? I just wanted to know whether it is right, because i found it as 0xB0. 

If the address mentioned is correct could you tell me how you have got it.?

Your help is appreciated.

  • 0
    TI__Intellectual 1930 points
    Hi Blessy,

    You are correct; the serializer will be found at 0xB0. The 0111101x shown in the schematic must be an error, as there shouldn't be any devices in this design with that address. The serializer datasheet shows 0xB0 (8-bit) or 0x58 (7-bit) to be the address set by the resistor divider shown in the schematic, and the Omnivision imager can only have address 0x20 or 0x30.

    Thanks for bringing this to our attention. We will get this corrected ASAP.
  • 0 in reply to Luis Cordova
    Intellectual 585 points
    Hi Luis,

    Thank you for your time. One more thing. In one of the code in VisionSDK 3.1, i had found this

    BspUtils_Ub960I2cParams gUb960Cfg_IMI[] = {
    /* IMI OV10640 1 */
    {0x4C, 0x01, 0x0},
    {0x58, 0x58, 0x0},
    {0x6D, 0x7D, 0x0},
    {0x5D, 0xB0, 0x0}, ---------> Serializer address given to deserializer
    {0x65, ((UInt8) (IMI_PORT_0_SER_ADDR << 1U)), 0x0},
    {0x5E, 0x62,0}, --------------> This is the part where the sensor address is given to the deserializer. Why 0x62? Why not 0x60 (8-bit)?

    We are using TIDA-00421 as the interface and we are getting the video output with 0X62. I tried changing this value to 0x60, but couldn't get the output.

    Will be grateful for your help.
  • 0 in reply to Blessy Abraham
    TI__Intellectual 1930 points
    Hi Blessy,

    As we did not have any part in the code that runs in VisionSDK 3.1, I cannot comment on this, unfortunately.

    For further questions on VisionSDK, please refer to TI's Embedded Processing support.