• State TI Thinks Resolved
  • Locked Locked
  • Replies 21 replies
  • Answers 8 answers
  • Subscribers 34 subscribers
  • Views 950 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: DS90UB954

peiyq
Expert 1400 points
Part Number: DS90UB954-Q1
There have some decvices have AEQ flicker issue, AEQ normal date such like : 0x2, 0x1/0x3, etc.
But When flicker happending , AEQ data change to 0xF/0x17, Could you help me know why it change to 0x17? 
The EQ value of AEQ seems to change dynamically. What's the reason for the change?

  • 0
    TI__Genius 11340 points

    Hi peiyq,

    The AEQ might be changing because there's unstable lock or parity errors in the link. I recommend running the Margin Analysis tool to check the eye margin of your system and set the best EQ range. Take a look at this app note: http://www.ti.com/lit/an/snla301/snla301.pdf

    Best,

    Jiashow

  • 0 in reply to Jiashow Ho
    Expert 1400 points

    Hi Jiashow

    I have ran the MAP tool to set the AEQ range (AEQ_MIN_MAX Address 0xD5) to 0xE0.

    And I print AEQ_STATUS value (Address 0xD3).

    Sometimes the AEQ_STATUS is 0xF or 0x17.

    Why is AEQ_STATUS out of the AEQ range I set?

  • 0 in reply to peiyq
    TI__Genius 11340 points

    Hello,

    You are setting your EQ level to 14.

    From the AEQ_STATUS register, EQ Stage1 is bits 5:3, EQ Stage2 is bits 2:0.

    Please refer to table 4 in the app note: http://www.ti.com/lit/an/snla301/snla301.pdf 

    Jiashow

  • 0 in reply to Jiashow Ho
    Expert 1400 points

    Hi Jiashow

    > From the AEQ_STATUS register, EQ Stage1 is bits 5:3, EQ Stage2 is bits 2:0.

    > Please refer to table 4 in the app note: http://www.ti.com/lit/an/snla301/snla301.pdf

    I have seen snla301 document.

    I think that you mentioned is opposite.

    For AEQ_STATUS register, EQ Stage2 is bits 5:3, EQ Stage1 is bits 2:0, is that right?

    I can't find the document specification about this.

    Could you show me that?

  • 0 in reply to peiyq
    TI__Genius 11340 points

    Hello,

    I've verified with my team. For AEQ_STATUS register, EQ Stage2 is bits 5:3, EQ Stage1 is bits 2:0.

    Jiashow

  • 0 in reply to Jiashow Ho
    Expert 1400 points

    From our customer question， could you help to answer？

    If you check the log of the image cracking, AEQ_STATUS changes even in the PowerOn state, so please send the following sentence to TI and ask for confirmation.

    <Description>
    Unexplained image cracking has occurred rarely. The log at that time is as attached (Please attach the log of # 5). AEQ_STATUS is incremented by a communication error,
    and then a communication error occurs again and AEQ_STATUS is further incremented. This behavior makes AEQ_STATUS appear to be increasingly far from optimal.
    Please answer the following questions.
    <Question>
    1. From the log, AEQ_STATUS appears to be transitioning to the Increment Inner Loop in Figure.5 if the error register is set even in the PowerOn state.
    Although this route is not described in the Flow Chart, is there actually a route, and is this state transition correct?
    2. Currently, the loop range is set to the full range 0 to F according to the recommendation of TI (Taiwan), but 0 to 5 is an appropriate range in TI Tool.
    It seems wise to set this to 0-5 to avoid this phenomenon, is that correct?

    Logcat as below shown:

    Kernel_1970-01-01-09_00_35_356.log

    01-01 09:00:54.232 0 0 I CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 1155 CAM_START_DEV Success, sensor_id:0x4688, sensor_slave_addr:0x6c
    01-01 09:00:54.288 0 0 I CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 1155 CAM_START_DEV Success, sensor_id:0x2770, sensor_slave_addr:0x6c

    01-01 09:00:56.958 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 738 ov2718: ret=0, read 0x7A=0x0 0x4E=0x4
    01-01 09:00:56.959 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 763 ov2718: read DEVICE_STS=0xDF, AEQ_STATUS=0x2
    01-01 09:00:56.959 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 767 ov2718: read STS1=0x3, STS2=0x4
    01-01 09:00:56.959 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 771 ov2718: read RX_PAR_ERR_HI=0x0, RX_PAR_ERR_LO=0x0
    01-01 09:00:56.991 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2884 CSID:1 UNBOUNDED_FRAME
    01-01 09:00:57.018 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 738 ov2718: ret=0, read 0x7A=0xE 0x4E=0xE5
    01-01 09:00:57.019 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 763 ov2718: read DEVICE_STS=0xDF, AEQ_STATUS=0x4
    01-01 09:00:57.019 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 767 ov2718: read STS1=0x3, STS2=0x4
    01-01 09:00:57.021 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 771 ov2718: read RX_PAR_ERR_HI=0x0, RX_PAR_ERR_LO=0x1A

    01-01 09:00:58.338 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 738 ov2718: ret=0, read 0x7A=0x0 0x4E=0x4
    01-01 09:00:58.339 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 763 ov2718: read DEVICE_STS=0xDF, AEQ_STATUS=0x4
    01-01 09:00:58.339 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 767 ov2718: read STS1=0x3, STS2=0x4
    01-01 09:00:58.348 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 771 ov2718: read RX_PAR_ERR_HI=0x0, RX_PAR_ERR_LO=0x0
    01-01 09:00:58.372 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2884 CSID:1 UNBOUNDED_FRAME
    01-01 09:00:58.397 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2884 CSID:1 UNBOUNDED_FRAME
    01-01 09:00:58.409 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 738 ov2718: ret=0, read 0x7A=0xF 0x4E=0x25
    01-01 09:00:58.410 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 763 ov2718: read DEVICE_STS=0xDF, AEQ_STATUS=0x5
    01-01 09:00:58.410 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 767 ov2718: read STS1=0x3, STS2=0x4
    01-01 09:00:58.411 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 771 ov2718: read RX_PAR_ERR_HI=0x0, RX_PAR_ERR_LO=0x3C

    01-01 09:00:59.618 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 738 ov2718: ret=0, read 0x7A=0x0 0x4E=0x4
    01-01 09:00:59.619 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 763 ov2718: read DEVICE_STS=0xDF, AEQ_STATUS=0x5
    01-01 09:00:59.620 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 767 ov2718: read STS1=0x3, STS2=0x4
    01-01 09:00:59.621 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 771 ov2718: read RX_PAR_ERR_HI=0x0, RX_PAR_ERR_LO=0x0
    01-01 09:00:59.656 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2884 CSID:1 UNBOUNDED_FRAME
    01-01 09:00:59.678 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 738 ov2718: ret=0, read 0x7A=0x4 0x4E=0x4
    01-01 09:00:59.678 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 763 ov2718: read DEVICE_STS=0xDF, AEQ_STATUS=0x7
    01-01 09:00:59.678 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 767 ov2718: read STS1=0x3, STS2=0x4
    01-01 09:00:59.679 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 771 ov2718: read RX_PAR_ERR_HI=0x0, RX_PAR_ERR_LO=0x8

    01-01 09:00:59.858 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 738 ov2718: ret=0, read 0x7A=0x0 0x4E=0x4
    01-01 09:00:59.858 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 763 ov2718: read DEVICE_STS=0xDF, AEQ_STATUS=0x7
    01-01 09:00:59.858 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 767 ov2718: read STS1=0x3, STS2=0x4
    01-01 09:00:59.859 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 771 ov2718: read RX_PAR_ERR_HI=0x0, RX_PAR_ERR_LO=0x0
    01-01 09:00:59.863 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2884 CSID:1 UNBOUNDED_FRAME
    01-01 09:00:59.878 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2884 CSID:1 UNBOUNDED_FRAME
    01-01 09:00:59.918 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 738 ov2718: ret=0, read 0x7A=0xF 0x4E=0x65
    01-01 09:00:59.919 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 763 ov2718: read DEVICE_STS=0xDF, AEQ_STATUS=0xF
    01-01 09:00:59.919 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 767 ov2718: read STS1=0x7, STS2=0x4
    01-01 09:00:59.920 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 771 ov2718: read RX_PAR_ERR_HI=0x1, RX_PAR_ERR_LO=0x3B

    01-01 09:01:01.989 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 738 ov2718: ret=0, read 0x7A=0x0 0x4E=0x4
    01-01 09:01:01.990 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 763 ov2718: read DEVICE_STS=0xDF, AEQ_STATUS=0xF
    01-01 09:01:01.990 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 767 ov2718: read STS1=0x3, STS2=0x4
    01-01 09:01:01.992 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 771 ov2718: read RX_PAR_ERR_HI=0x0, RX_PAR_ERR_LO=0x0
    01-01 09:01:02.045 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2884 CSID:1 UNBOUNDED_FRAME
    01-01 09:01:02.052 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2871 CSID:1 ERROR_ECC
    01-01 09:01:02.059 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2884 CSID:1 UNBOUNDED_FRAME
    01-01 09:01:02.062 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 738 ov2718: ret=0, read 0x7A=0xF 0x4E=0x24
    01-01 09:01:02.063 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 763 ov2718: read DEVICE_STS=0xDF, AEQ_STATUS=0x17
    01-01 09:01:02.063 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 767 ov2718: read STS1=0x13, STS2=0x4
    01-01 09:01:02.063 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 771 ov2718: read RX_PAR_ERR_HI=0x0, RX_PAR_ERR_LO=0x0
    01-01 09:01:02.066 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2884 CSID:1 UNBOUNDED_FRAME
    01-01 09:01:02.100 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2884 CSID:1 UNBOUNDED_FRAME
    01-01 09:01:02.107 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2871 CSID:1 ERROR_ECC
    01-01 09:01:02.114 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2884 CSID:1 UNBOUNDED_FRAME
    01-01 09:01:02.118 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 738 ov2718: ret=0, read 0x7A=0xF 0x4E=0x65
    01-01 09:01:02.118 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 763 ov2718: read DEVICE_STS=0xDF, AEQ_STATUS=0x1F
    01-01 09:01:02.119 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 767 ov2718: read STS1=0x27, STS2=0x4
    01-01 09:01:02.119 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 771 ov2718: read RX_PAR_ERR_HI=0x9, RX_PAR_ERR_LO=0xFC
    01-01 09:01:02.136 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2884 CSID:1 UNBOUNDED_FRAME
    01-01 09:01:02.151 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2871 CSID:1 ERROR_ECC
    01-01 09:01:02.158 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2884 CSID:1 UNBOUNDED_FRAME
    01-01 09:01:02.173 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2884 CSID:1 UNBOUNDED_FRAME
    01-01 09:01:02.178 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 738 ov2718: ret=0, read 0x7A=0xF 0x4E=0x25
    01-01 09:01:02.178 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 763 ov2718: read DEVICE_STS=0xDF, AEQ_STATUS=0x0
    01-01 09:01:02.179 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 767 ov2718: read STS1=0x13, STS2=0x4
    01-01 09:01:02.181 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 771 ov2718: read RX_PAR_ERR_HI=0x0, RX_PAR_ERR_LO=0x0

    01-01 09:03:56.028 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 738 ov2718: ret=0, read 0x7A=0x0 0x4E=0x4
    01-01 09:03:56.029 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 763 ov2718: read DEVICE_STS=0xDF, AEQ_STATUS=0x0
    01-01 09:03:56.029 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 767 ov2718: read STS1=0x3, STS2=0x4
    01-01 09:03:56.029 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 771 ov2718: read RX_PAR_ERR_HI=0x0, RX_PAR_ERR_LO=0x0
    01-01 09:03:56.036 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2866 CSID:1 ERROR_CRC
    01-01 09:03:56.088 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 738 ov2718: ret=0, read 0x7A=0xF 0x4E=0x2

    01-01 09:03:56.576 0 0 I CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 1189 CAM_STOP_DEV Success, sensor_id:0x4688, sensor_slave_addr:0x6c
    01-01 09:03:56.743 0 0 I CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 1189 CAM_STOP_DEV Success, sensor_id:0x2770, sensor_slave_addr:0x6c

  • 0 in reply to peiyq
    TI__Genius 11340 points

    Hi Peiyq,

    The AEQ range should be set based on the the MAP results. Has the customer run the MAP tool? Could you share the results?

    Jiashow

  • 0 in reply to Jiashow Ho
    Expert 1400 points

    Hello Jiashow,

    Could you help to double check it？ Map will be upload shortly.

    In addition, could you help to confirm below screenshot ？

    In this figure, it seems that only when powerup reaches AEQ stop, it will end. But in fact, after AEQ stop, if there are errors in the normal operation process, the log will continue to look for the appropriate EQ value.

    Please help to confirm whether the flowchart should not go directly to the end after AEQ stop, but will wait. If there is an error, you will continue to adjust the EQ value (as seen from the log)

  • 0 in reply to peiyq
    Expert 1400 points

    Hello Dear, 

    Please help to reply this question. Thanks a lot.

  • 0 in reply to peiyq
    TI__Genius 11340 points

    Hi peiyq,

    You're right, AEQ will continue to check for errors even after it stabilizes.

    The results look good to me, just make sure you set the EQ range based on the results.

    Jiashow

  • 0 in reply to Jiashow Ho
    Expert 1400 points

    Hi Jiashow,

    Can you update  flow chart for above analysis？ 

  • 0 in reply to peiyq
    TI__Genius 11340 points

    Hi peiyq,

    I'll note it down.

    Jiashow

  • 0 in reply to Jiashow Ho
    Expert 1400 points

    Hi Jiashow,

    Please help to update flow chart.

    In additional, Could you let me know what the root cause for: 

    01-01 09:00:56.991 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2884 CSID:1 UNBOUNDED_FRAME
    01-01 09:00:57.018 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 738 ov2718: ret=0, read 0x7A=0xE 0x4E=0xE5
    01-01 09:00:57.019 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 763 ov2718: read DEVICE_STS=0xDF, AEQ_STATUS=0x4
    01-01 09:00:57.019 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 767 ov2718: read STS1=0x3, STS2=0x4
    01-01 09:00:57.021 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 771 ov2718: read RX_PAR_ERR_HI=0x0, RX_PAR_ERR_LO=0x1A

     

    What is the principle of this error? If the map value is good, why still have this problem? Is this kind of problem inevitable?

     

  • 0 in reply to peiyq
    TI__Genius 11340 points

    Hello,

    It looks like you have some CSI errors. Could you check registers on 0x5C - 0x60 on the serializer side? Check the camera output if you are seeing CSI errors at the serializer.

    Jiashow

  • 0 in reply to Jiashow Ho
    Expert 1400 points

    Hi Jiashow,

    We have checked MIPI waveform.

    There is no error from SER side when occurred flicker issue (DES side has error).

    Is there any other reason of FPDLink III to cause the flicker issue?

  • 0 in reply to peiyq
    TI__Genius 11340 points

    Hi Peiyq,

    Let me clarify, there's no errors on the SER error registers?

    Which errors are you seeing on the DES side? Did you read registers 0x4D, 0x4E, 0x55, 0x56?

    Best,

    Jiashow

  • 0 in reply to Jiashow Ho
    Expert 1400 points

    Hi Jiashow

    > there's no errors on the SER error registers?

    I have not read SER error registers (0x5C-0x60).

    I checked the MIPI waveform with Oscilloscope.

    > Which errors are you seeing on the DES side? Did you read registers 0x4D, 0x4E, 0x55, 0x56?

    Yes, I read these registers. Following is the log.

    01-01 09:00:56.991 0 0 E CAM_ERR : CAM-ISP: cam_ife_csid_irq: 2884 CSID:1 UNBOUNDED_FRAME
    01-01 09:00:57.018 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 738 ov2718: ret=0, read 0x7A=0xE 0x4E=0xE5
    01-01 09:00:57.019 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 763 ov2718: read DEVICE_STS=0xDF, AEQ_STATUS=0x4
    01-01 09:00:57.019 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 767 ov2718: read STS1(0x4D)=0x3, STS2(0x4E)=0x4
    01-01 09:00:57.021 0 0 I CAM_INFO: CAM-SENSOR: check_ds953_status: 771 ov2718: read RX_PAR_ERR_HI(0x55)=0x0, RX_PAR_ERR_LO(0x56)=0x1A

  • 0 in reply to peiyq
    TI__Genius 11340 points

    Hi peiyq,

    After you initialize the system, could you first read 0x4D, 0x4E, 0x55, and 0x56 to clear any errors that may have occurred during initialization? And then you read the same registers again once you see flicker?

    Right now it's hard to tell whether the errors in those registers are due to system initialization or the flicker.

    Jiashow

  • 0 in reply to Jiashow Ho
    Expert 1400 points

    Hi Jiashow

    I read registers 0x4D, 0x4E, 0x55 and 0x56 every 60ms interval.

    So the result has already been cleared.

  • 0 in reply to peiyq
    TI__Genius 11340 points

    Hello,

    It looks like the issue is with the camera. Are you seeing CSI errors on the 953 side? When you use 953 pattern generation are you still seeing the same issues?