• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 196 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.

DS90UB954-Q1: Regarding interfacing with DS90UB933

fabio ortolano
Intellectual 330 points
Part Number: DS90UB954-Q1

Hello

I'm tring to interface the DS90UB954 with a DS90UB933. I already tested the 933 board with a good link with the corrisponding 934 deserializer. For interfacing with a MIPI SoC board, I want to use a 954 deserializer and I developped a board with this device. The link seems to be good so PASS and LOCK are ok. The 933 is driven directly by a 48MHz clock sourced by the sensor. 

In the 933 I set the MODE to work in 12-bit mode with Rpu of 15K and Rpd of 56K (1.42V). In 954 the same.

What I'm facing is that on regs 0x73/0x74 I read the correct Line numbers but in 0x75/0x76 I read exactly 1.5 times the line lenght. Is this correct?

Thanks

  • 0
    TI__Guru** 103215 points

    Hello Fabio,

    That sounds correct since RAW12 data format uses 3 bytes for every 2 pixels and the line length is reported in bytes, not pixels. 

    Best Regards,

    Casey

  • 0 in reply to Casey McCrea
    Intellectual 330 points

    Hello, thanks for this clarification. Ok so....this is correct but, I can't see anything out from MIPI side.... I dont't know why because if I enable the Test it seems to send something....

  • 0 in reply to fabio ortolano
    TI__Guru** 103215 points

    Hello Fabio,

    Can you please send the programming steps that you are using here?

    Best Regards,

    Casey 

  • 0 in reply to Casey McCrea
    Intellectual 330 points

    Hello

    Actually I do nothing of different from what I tried with 934 deserializer, where the things goes well. A thing to take in account is that I did not use I2C inside the FPD packet but I have a dedicated couple of wires due to some restrictions. Due to this, I direct interface serializer and deserializer with the host master, but I think that this is not relevant for this situation.

    1- I program the serializer, forcing the reset of the sensor to start treaming via I2C

    2- I set the serializer to work with the ongoing Pixclock

    REG0x3: 0xc3

    REG0x35: 0x0

    3- Set the deserializer on channel 0 with

    REG0xD: 0xf9

    REG0x8: 0x9c

    REG0x4C: 0x0

    REG0x6E: 0x10

    REG0x6F: 0x82

    REG0x7C: 0x0     (Line and Frame valid hig during data)

    4- I set the MODE on deserializer to work in 12 bit HF mode because the clock of the sensor is 48MHz

    As you tell me, if i read the correct line count and the correct byte count it means that the receiver works (also PASS and LOCK are high). So this part I think is ok. On the other side, if I try the commands on chapter 7.5.11.4 something goes out from Mipi side. Is there something else to do?

    That's all. 

  • +1 in reply to fabio ortolano
    TI__Guru** 103215 points

    Hello Fabio,

    In order to get data output you must also assign the input streams to be forwarded to the CSI-2 output port, configure your desired CSI-2 speed/lane settings, and then enable the CSI-2 transmitter. See section 7.4.28 and 7.4.21 of the datasheet 

    Best Regards,

    Casey 

  • 0 in reply to Casey McCrea
    Intellectual 330 points

    Hello Casey, ok I tried and I found exactly what I need. Setting the registers as described in that chapter the system worked ok and I can grab an image correctly. Thanks