• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 34 subscribers
  • Views 405 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: data conversion failed

Denny Huang
Expert 7170 points
Part Number: DS90UB954-Q1


Dear team

The customer working for a second source camera, os02h10.

But we got failed on your data conversion below.

Please help have a look and then provide how to fix the issue.

Thank you so much.

 

Note:

You will see only the head and tail of sensor mipi data converted.

(MDP1 is sensor’s data lane 1 p and CAM1_CSI1_LANE1_P is TI954’s output on data lane 1 p.)

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

Could you help make sure whether TI954 can not support os02h10_12bit?

Please see the test result of item 3 below:

1.ov2718_12bit:(Preview normally.)

01-01 00:01:06.397     0     0 I __show  : 57 0x4e = 0x45

01-01 00:01:08.956     0     0 I __show  : 57 0x4e = 0x4

01-01 00:01:10.862     0     0 I __show  : 57 0x4e = 0x4

01-01 00:01:12.818     0     0 I __show  : 57 0x4e = 0x4

01-01 00:01:14.900     0     0 I __show  : 57 0x4e = 0x4

 

2.ov2718_10bit:(Preview normally.)

07-17 18:15:17.143     0     0 I __show  : 57 0x4e = 0x45

07-17 18:15:19.676     0     0 I __show  : 57 0x4e = 0x4

07-17 18:15:21.512     0     0 I __show  : 57 0x4e = 0x4

07-17 18:15:23.118     0     0 I __show  : 57 0x4e = 0x4

07-17 18:15:24.503     0     0 I __show  : 57 0x4e = 0x4

 

3.os02h10_12bit:(No preview.)

01-01 00:02:41.912     0     0 I __show  : 57 0x4e = 0x55

01-01 00:02:43.883     0     0 I __show  : 57 0x4e = 0x15

01-01 00:02:44.787     0     0 I __show  : 57 0x4e = 0x15

01-01 00:02:45.648     0     0 I __show  : 57 0x4e = 0x15

01-01 00:02:46.507     0     0 I __show  : 57 0x4e = 0x15

 

4.os02h10_10bit:(No preview.)

07-14 08:23:58.082     0     0 I __show  : 57 0x4e = 0x45

07-14 08:23:59.135     0     0 I __show  : 57 0x4e = 0x4

07-14 08:24:00.031     0     0 I __show  : 57 0x4e = 0x4

07-14 08:24:00.857     0     0 I __show  : 57 0x4e = 0x4

07-14 08:24:01.634     0     0 I __show  : 57 0x4e = 0x4

Note:

Many thanks

Denny

  • 0
    TI__Guru** 109840 points

    Hello Denny,

    are you sure you are configuring the sensor in the correct way?

    Which SER are you using?

    How many CSI-2 lanes are you using?

    Which Clocking mode are you using on SER and DES?

  • 0 in reply to Hamzeh Jaradat
    TI__Expert 7170 points

    Hi Hamzeh

    Thanks your reply. the customer's reply as below

    1.Are you sure you are configuring the sensor in the correct way?

    Ans: Yes, it could work well without Serdes.

    2.Which SER are you using?

    Ans: ds90ub953/ds90ub954.

    3.How many CSI-2 lanes are you using?

    Ans: Two data lanes and one clock lane.

    4.Which Clocking mode are you using on SER and DES?

    Ans: We used ds90ub954 external clock, 24MHz .

    Many thanks

    Denny

  • 0 in reply to Denny Huang
    TI__Guru** 109840 points

    Hello Denny,

    which resolution, data type and frame rate are you using?

  • 0 in reply to Hamzeh Jaradat
    TI__Expert 7170 points

    Hi Hamzeh

    Thanks your reply. the customer's reply as below

    1. which resolution, data type and frame rate are you using?

    Ans: 1920x1080, CSI_RAW12, and 30 frames.

    Many thanks

    Denny

  • 0 in reply to Denny Huang
    TI__Guru** 109840 points

    Hello Denny,

    you may try another image sensor with the same data type, or you may try the following script to generate a pattern on the UB953 and send it to the DES, without the image sensor.

    board.WriteReg(0xB0, 0x02) # IA_AUTO_INC=1
    board.WriteReg(0xB1, 0x01) # PGEN_CTL

    board.WriteReg(0xB2, 0x01) # PGEN_ENABLE=1
    board.WriteReg(0xB2, 0x33) # PGEN_CFG
    board.WriteReg(0xB2, 0x2C) # PGEN_CSI_DI
    board.WriteReg(0xB2, 0x0B) # PGEN_LINE_SIZE1
    board.WriteReg(0xB2, 0x40) # PGEN_LINE_SIZE0
    board.WriteReg(0xB2, 0x01) # PGEN_BAR_SIZE1
    board.WriteReg(0xB2, 0x68) # PGEN_BAR_SIZE0
    board.WriteReg(0xB2, 0x04) # PGEN_ACT_LPF1
    board.WriteReg(0xB2, 0x38) # PGEN_ACT_LPF0
    board.WriteReg(0xB2, 0x04) # PGEN_TOT_LPF1
    board.WriteReg(0xB2, 0x65) # PGEN_TOT_LPF0
    board.WriteReg(0xB2, 0x0B) # PGEN_LINE_PD1
    board.WriteReg(0xB2, 0x93) # PGEN_LINE_PD0
    board.WriteReg(0xB2, 0x0A) # PGEN_VBP
    board.WriteReg(0xB2, 0x0A) # PGEN_VFP
    board.WriteReg(0xB2, 0xAA) # PGEN_COLOR0
    board.WriteReg(0xB2, 0x33) # PGEN_COLOR1
    board.WriteReg(0xB2, 0xF0) # PGEN_COLOR2
    board.WriteReg(0xB2, 0x7F) # PGEN_COLOR3
    board.WriteReg(0xB2, 0x55) # PGEN_COLOR4
    board.WriteReg(0xB2, 0xCC) # PGEN_COLOR5
    board.WriteReg(0xB2, 0x0F) # PGEN_COLOR6
    board.WriteReg(0xB2, 0x80) # PGEN_COLOR7
    board.WriteReg(0xB2, 0x00) # PGEN_COLOR8
    board.WriteReg(0xB2, 0x00) # PGEN_COLOR9
    board.WriteReg(0xB2, 0x00) # PGEN_COLOR10
    board.WriteReg(0xB2, 0x00) # PGEN_COLOR11
    board.WriteReg(0xB2, 0x00) # PGEN_COLOR12
    board.WriteReg(0xB2, 0x00) # PGEN_COLOR13
    board.WriteReg(0xB2, 0x00) # PGEN_COLOR14
    board.WriteReg(0xB2, 0x00) # Reserved

  • 0 in reply to Hamzeh Jaradat
    TI__Expert 7170 points

    Hi Hamzeh

    Thanks your reply. the customer's reply as below

    The issue has been fixed by changing to 0x4e from 0x5e in the 0x61 register of os02h10 sensor. 

    It seems to be related to mipi serial clock and mipi pixel clock.

    you may try another image sensor with the same data type, or you may try the following script to generate a pattern on the UB953 and send it to the DES, without the image sensor.

    Ans: I had tried it before:

    1.ov2718_12bit:(Preview normally.)

    01-01 00:01:06.397     0     0 I __show  : 57 0x4e = 0x45

    01-01 00:01:08.956     0     0 I __show  : 57 0x4e = 0x4

    01-01 00:01:10.862     0     0 I __show  : 57 0x4e = 0x4

    01-01 00:01:12.818     0     0 I __show  : 57 0x4e = 0x4

    01-01 00:01:14.900     0     0 I __show  : 57 0x4e = 0x4

     

    Many thanks

    Denny

  • 0 in reply to Denny Huang
    TI__Guru** 109840 points

    Hello Denny,

    thanks for the update and glad that it was solved by changing the sensor settings!

  • 0 in reply to Hamzeh Jaradat
    TI__Expert 7170 points

    Hi Hamzeh

    Thanks your reply. the customer's reply as below

    Below are my checks about the mipi clock with different sensors:

    1. os02h10_12bit mipi clock=902.4MHz.

    Ans: No preview.

    2.os02h10_10bit mipi clock=748.8MHz.

    Ans: Could preview normally.

    3.ov2718_12bit mipi clock=768MHz.

    Ans: Could preview normally.

    4.ov2718_10bit mipi clock=768MHz.

    Ans: Could preview normally.

     

    Can you help check what the limitation of the mipi clock is in your spec?

    Many thanks

    Denny

  • 0 in reply to Denny Huang
    TI__Guru** 109840 points

    Hello Denny,

    It is expected that you do not get the correct signal due to the higher CSI PCLK.
    Our UB953 can support a max CSI PCLK = 416MHz, and the UB954 can support a max CSI PCLK = 832MHz.