• State TI Thinks Resolved
  • Locked Locked
  • Replies 13 replies
  • Answers 3 answers
  • Subscribers 33 subscribers
  • Views 832 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: Ds90ub960 Ds90ub935/Ds90ub953 Initialization sequence

xinyu wu
Prodigy 115 points
Part Number: DS90UB960-Q1


Dear Ti Engineer，
My deserializer is ds90ub960, which needs to deserialize two different types of camera serializers: ds90ub935 and ds90ub953. I'd like to ask, is tids90ub960 the initialization sequence of these two serializers different? Can you help provide the initialization sequence that can drive these two serializers?
Thank you.
I wish you a happy life

  • 0
    TI__Mastermind 18755 points

    Hello,

    The 935 and 953 are both CSI serializers and the initialization sequence is the same.  Make sure you set the MODE straps of all devices correctly.  With out knowing your application I don't know what details I can provide but the most important thing is MODE strapping.

    Regards,

    Nick

  • 0 in reply to Nicholas Darash
    Prodigy 115 points

    Dear TI，

    All right. Well, uh, thanks for your time

    I have another question to ask for your help. The data output format of my 935 camera is raw16. I want to know whether 960 can support it and how to configure it?

  • 0 in reply to xinyu wu
    TI__Mastermind 18755 points

    Hi,

    The 935/960 pair only acts as a pipe and will not change any CSI data it receives.  What you can expect is that the CSI data input at the 935 will be recreated exactly as it is at the 960.  So as long as you do not go over the throughput capabilities of the devices we can support the format.

    Regards,

    Nick

  • 0 in reply to Nicholas Darash
    Prodigy 115 points

    Dear Nick,

    Okay, thank you very much for your answer.

    Also, because our Camera module data is valid for low 12 -bit data of RAW 16 data, do I need to configure 960 PORT_CONFIG Register (0x6D) to set the Mode to RAW12 Mode?

    Thanks.

    Wu

  • 0 in reply to xinyu wu
    TI__Mastermind 18755 points

    Hi Wu,

    I think it would depend on what the SoC is expecting but you should not need to change the data type.

    Regards,

    Nick

  • 0 in reply to Nicholas Darash
    Prodigy 115 points

    Hi, Nick

    Now I have configured the initialization sequence of 960 + 935 & 953, but the camera of 953 can detect, but the camera of 935 concatenator cannot detect

    The data format of my 953 camera output is YUV422@30fps ，
    The output data format of 935 camera is raw16 @ 20fps

    This is my initialization sequence. Can you help me see what the problem is?

    dev_addr = 0x7A
    ser_alias = 0x18
    slave_addr = 0x60
    slave_alias = 0x22
    port_config = you should select the value matching the used MODE
    board.WriteI2C(dev_addr,0x4C,0x01)
    board.WriteI2C(dev_addr,0x58,0x5E)
    board.WriteI2C(dev_addr,0x72,0x0)
    board.WriteI2C(dev_addr,0x5C,ser_alias)
    board.WriteI2C(dev_addr,0x5D,slave_addr)
    board.WriteI2C(dev_addr,0x65,slave_alias)
    board.WriteI2C(dev_addr,0x6D,port_config)
    board.WriteI2C(dev_addr,,0x01)
    board.WriteI2C(dev_addr,0x32,0x01)
    board.WriteI2C(dev_addr,0x33,0x03)
    board.WriteI2C(dev_addr,0x1F,0x00)
    board.WriteI2C(dev_addr,0x10，0x91)
    board.WriteI2C(dev_addr,0x19，0x15）
    board.WriteI2C(dev_addr,0x1A，0xB3)
    board.WriteI2C(dev_addr,0x1B, 0xC3)
    board.WriteI2C(dev_addr,0x1C, 0x4F)
    board.WriteI2C(dev_addr,0x18, 0x01)
    board.WriteI2C(dev_addr,0x20,0xE0)
  • 0 in reply to xinyu wu
    TI__Mastermind 18755 points

    Hi,

    Are you following the same init sequence for both parts?  Can you share the deserializer registers when using the 953(working) and 935(not working)?

    Regards,

    Nick

  • 0 in reply to Nicholas Darash
    Prodigy 115 points

    Hi Nick，

    The two cameras follow the same initialization sequence. They are connected to two ports of the same deserializer and share the same deserializer register.

    board.WriteI2C(dev_addr,0x4C,0x01) #fpd3 port select RX0:ti953-0x01/ti935--0x12
    board.WriteI2C(dev_addr,0x58,0x5E) # Enable Pass Through and set the back channel to 50Mbps
    board.WriteI2C(dev_addr,0x72,0x00+port)
    board.WriteI2C(dev_addr,0x5C, serializer_alias) # setup serialias address
    board.WriteI2C(dev_addr,0x65, sensor_alias）
    board.WriteI2C(dev_addr,0x6D,0x7c) # setup FPD3_MODE:CSI-2
    board.WriteI2C(dev_addr,0x7D,0x01) # set PASS_THRESHOLD=1
    board.WriteI2C(dev_addr,0x32,0x01) # select CSI0
    board.WriteI2C(dev_addr,0x33,0x03) # CSI_EN
    board.WriteI2C(dev_addr,0x1F,0x00) # set CSI_TX_SPEED to 1.6Gbps
    board.WriteI2C(dev_addr,0x18, 0x01) #Enable FrameSync
    board.WriteI2C(dev_addr,0x10，0x91)
    board.WriteI2C(dev_addr,0x19，0x15）
    board.WriteI2C(dev_addr,0x1A，0xB3)
    board.WriteI2C(dev_addr,0x1B, 0xC3)
    board.WriteI2C(dev_addr,0x1C, 0x4F)
    This is my modified ti960, which matches the initialization sequence of 935 and 953 at the same time.
    At the same time, I also want to ask whether the registers of the serializer chip need to be operated for the two different camera data formats mentioned above
    Best Regards,
    Xinyu
  • 0 in reply to xinyu wu
    TI__Mastermind 18755 points

    Hi Xinyu,

    Are you able to share the deserializer registers for both the working and non working versions of the setup?

    Regards,

    Nick

  • 0 in reply to Nicholas Darash
    Prodigy 115 points
    Hi Nick，

    I'm very sorry. Maybe I don't understand what you mean.

    The reply I sent above contains all my settings for the ti960 deserializer register. The 935 and 953 serializers share the above configuration.
    Do you want to ask me what configuration I have made for 953 and 935 serializers?

    Here are my register settings for the two serializers

    board.WriteI2C(dev_addr, 0x02, 0x73)
    board.WriteI2C(dev_addr, 0x0E, 0x10)
    board.WriteI2C(dev_addr, 0x0D, 0xD0)
    board.WriteI2C(dev_addr, 0x0D, 0x10)
    Best Regards,
    Xinyu
  • 0 in reply to xinyu wu
    TI__Mastermind 18755 points

    Hi Xinyu,

    All I am asking is that you read back every register on the deserializer and share all the values here.  I want to compare any possible differences in the case you have where everything is working and the case where it isn't working.

    Regards,

    Nick

  • 0 in reply to Nicholas Darash
    Prodigy 115 points

    Hi Nick,

    Sorry for the late recovery, the values read back to the deserializer are all consistent.
    But reading the value of the serializer is inconsistent

    935(failed to activate)

    -------------------------------------------------------------------

    Reg 0x02 == 0x33

    Reg 0x0e == 0x0f

     Reg 0x0d == 0xf0

    -------------------------------------------------------------------

    953 (success to activate)

    -------------------------------------------------------------------

    Reg 0x02 == 0x73

    Reg 0x0e == 0x10

    Reg 0x0d == 0x10

    ----------------------------------------------------------

    Des read back  data

    Reg 0x4c== 0x1f

    Reg 0x58 == 0x5e

    Reg 0x72 == 0x01

    Reg 0x5C == 0x22

    Reg 0x32 == 0x01

    Reg 0x33 == 0x01

    Reg 0x18 ==  0x01

    ---

    Thanks

    Xinyu.

  • 0 in reply to xinyu wu
    TI__Guru** 103215 points

    Xinyu,

    Are you connecting two serializers to the 960 at once? Or you are saying that you are testing one configuration at a time with 935 or 953 always connected to RX0?

    Best Regards,

    Casey