• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 33 subscribers
  • Views 1603 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.

Original question:

Linux/DS90UB964-Q1: Linux Driver available?

Linux/DS90UB964-Q1: Linux Driver and Device Tree Support

Sneha James
Prodigy 60 points
Part Number: DS90UB964-Q1
Other Parts Discussed in Thread: DS90UB913A-Q1

Tool/software: Linux

Hi

We have a DS90UB964-Q1 deserializer chip integrated into Renesas RCar H3 SoC. We also have four camera modules containing DS90UB913A-Q1 serializer and OV10635 Camera which are connected to the deserializer via FPD Link 3.

Our problem is that we are not able to see the deserializer chip in i2cdetect. We confirmed that the I2C bus is working since it is showing other devices attached to it.

How can we add the deserializer node in the device tree? Can anyone share an example?

Are there any Linux device drivers available for DS90UB964-Q1 deserializer?

Thanks

Sneha

  • 0
    TI__Mastermind 19720 points
    Hello Sneha,

    We are not aware of any linux drivers for the DS90UB964 for the Renesas RCar H3 Soc.

    What is configuration are you using the DS90UB964 in? can you share the schematic? What I2C address do you have the device in? Can you check the voltage of the PDB pin?

    regards,
    Michael
  • 0 in reply to Michael.Walker
    Prodigy 60 points
    Hi Michael

    Thanks for replying back.

    DS90UB964 has been configured for RAW 12 HF, Coax mode.

    I2C address is 0x30(7-bit) and 0x60(8-bit).

    We checked the voltage across PDB pin. It was zero.

    Regards
    Sneha
  • 0 in reply to Sneha James
    TI__Mastermind 19720 points
    Hi Sneha,
    In order to read or write I2C to the 964 you have to power up the device by having PBD high. Here is what it says in the datasheet:
    "Power-down mode
    INPUT IS 3.3V TOLERANT
    PDB = 1.8 V, device is enabled (normal operation)
    PDB = 0, device is powered down."

    Regards,
    Michael W.
  • 0 in reply to Michael.Walker
    Prodigy 60 points

    Dear Michael

    Thanks for the information.
    We will check why voltage across PDB pin is zero and will make sure that PDB input is always high.

    After powering up the device, since it has no drivers, how can we check the functionality of the deserializer?
    How can we test Camera output?
    Are there any reference drivers or applications available to test the features?

    Regards
    Sneha

  • 0 in reply to Sneha James
    TI__Mastermind 19720 points
    Hello Sneha,
    I am not aware of any drivers that you could use as reference drivers. you can check the functionality of the deserializer by enabling the pattern generator and checking the CSI output.

    Regards,
    Michael W.
  • 0 in reply to Michael.Walker
    Prodigy 60 points

    Dear Michael

    We could enable DS90UB964-Q1 and the chip address 0x30 is now visible in i2cdetect output. We have connected four Serializer(DS90UB913A-Q1)+Camera(OV10635) modules and executed the script given in Page 22 of the DS90UB96XEVM user guide using i2c-tools instead of python scripts. i2cdetect output :

    # i2cdetect -r 6

    WARNING! This program can confuse your I2C bus, cause data loss and worse!

    I will probe file /dev/i2c-6 using receive byte commands.

    I will probe address range 0x03-0x77.

    Continue? [Y/n]

        0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f

    00:          -- -- -- -- -- -- -- -- -- 0c 0d 0e --

    10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

    20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

    30: 30 31 -- 33 -- -- -- -- -- -- -- -- -- -- -- --

    40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

    50: -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- --

    60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

    70: -- -- -- -- -- -- -- --                        

    0x30 is the deserializer chip address and 0x51 is an unrelated chip in the bus.

    How can we capture and view the CSI data coming from the cameras? Please help.

    Regards

    Sneha

  • 0 in reply to Sneha James
    TI__Mastermind 19720 points
    Hi Sneha,
    That is great that the 964 is recognized. If the cameras are outputing CSI to the 913A then there should be CSI output from the 964, but I am not familiar with the Renesas RCar H3 SoC. I would look here for help with the Renesas here: renesasrulz.com/.../synergy---forum

    Regards,
    Michael W.
  • 0 in reply to Michael.Walker
    Prodigy 60 points
    Hi Michael

    We would surely check the mentioned forum for support. Thank you.

    As you had suggested in the previous response, we tried to enable the pattern generator using the script given in Pg 48 of the DS90UB964-Q1 datasheet.

    Pattern Generation Data format is RGB888(0x24) as configured in the script.

    DS90UB964-Q1 is configured for RAW12 HF Coax mode. So Reg 0x6d is set to 0x7e for each RX port.
    Data format set in 0x70[5:0] is 0x1f (YUV 422 10-bit) for each RX port.
    Data format set in 0x71[5:0] is 0x2c (RAW12) for each RX port.

    But registers 0x73 - 0x76 are found to be set as 0x00.

    Can you please help with this?

    Regards
    Sneha