• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 4 answers
  • Subscribers 32 subscribers
  • Views 859 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.

Original question:

I2C Setting for DS90UB914A / 913A using TI eval boad

DS90UB913A-CXEVM: I2C Setting for DS90UB914A / 913A using TI eval boad

Chirinjeev Singh
Prodigy 30 points
Part Number: DS90UB913A-CXEVM
Other Parts Discussed in Thread: USB2ANY, ALP

I have a UB913 talking to AR0132 camera module which has a camera sensor and the deserializer.

I am able to access the local I2C registers of the serializer as well as the remote registers of the serializer (914).

But I am having trouble accessing camera sensor i2c registers which are mapped to 16-bit address space (0x3000 - 0x3FFFF).

I am using USB2ANY module connected to my laptop to act as a Host for I2C.

If I do :

print "Value = ", (board.ReadI2C(0x21, 0x3000)), the entire system has to be rebooted.

Please help as currently I cannot talk to the sensor at all. I dont know if my device ID is incorrect or the way I am addressing is incorrect.

  • 0
    TI__Mastermind 21685 points
    Hi,

    ALP can supports 16bit i2c address write operation. For example to write address 0x300C of AR1032 with value 0x55, you can use

    board.WriteI2C(AR1032, 0x30, [0x0C, 0x55])

    Unfortunately ALP can't support 16bit I2C address read operation. If you want to read you can use for example "Aardvark I2C/SPI" from Total phase.

    Thanks,
    Vishy
  • 0 in reply to Vishy Viswanathan
    Prodigy 30 points

    I set the SER_ID and SER_ALIAS in the De-serialzer registers (address 0x08 and 0x10)  to a value 0x20 and tried.

    And tried writing to the reset register of the sensor 0x301A to a value of 0x5C to get it out of standby.

    Since I can't read I am not sure what is getting written.

    board.WriteI2C(0x20, 0x30, [0x1A, 0x5C])

    All I want is Pixel clock. Currently the sw says that PCLK is not detected. Any idea why PCLK would not come?

  • 0 in reply to Chirinjeev Singh
    TI__Mastermind 21685 points

    >>>All I want is Pixel clock. Currently the sw says that PCLK is not detected. Any idea why PCLK would not come?

    Please check mode select switch S2 on the serializer board: whether Serializer is in "PCLK from imager" mode or "External oscillator" mode. Page 9 of the EVM user guide shows the selection settings. 

    If PCLK from imager mode is selected and imager is initialized correctly you should see PCLK detected on the info tab.

    Thanks,

    Vishy

  • 0 in reply to Vishy Viswanathan
    TI__Mastermind 21685 points

    Hi,

    I checked it on a 914a/913a EVM and please note switch setting correction below.

    ALP is connected to 914A and have lock detected LED on. OV10635 imager is connected to the Serializer and switch settings is in the External Oscillator mode (not PCLK from imager mode)

    Once I run script to initialize the imager, I do see on the info tab PCLK detected. Please see screen shot below

    So in external oscillator mode, you should see PCLK status as detected if the script initialization is correct. 

    Thanks,

    Vishy

  • 0 in reply to Vishy Viswanathan
    Prodigy 30 points

    Yes, I am in External Oscillator mode.

    Can you please share the initialization script for the imager that you mentioned.

    Thanks

    Chirinjeev

  • 0 in reply to Chirinjeev Singh
    TI__Mastermind 21685 points

    Hi,

    Please check imager slave ID and slave alias. See script snippet below. Imager OVT i2c address is 0x60. Slave ID0 and alias0 registers are initialized to this value so you can access imager registers correctly from 914a side. Rest of the script initializations are OVT specific.

    Thanks,

    Vishy