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.

What is the meaning of ds90ub954 register change?

Other Parts Discussed in Thread: DS90UB954-Q1, DS90UB953-Q1

register 0x4D 0x4E 0x7A 0x7B ,Normal Value is 00; 

The value changes to 0x4D=0x13; 0x4E=0x6D; 0x7A=0xF or 0x4; 0x7B=0x14 or 0x1 in case of error.

Please tell me where the problem is? Whether 953 coding is abnormal?

  • Hi,

    0x4D = 0x13; Lock status changed but system is locked to input and Pass bit is high.

    0x4E = 0x6D; Line length changed, FPD3 encoder error, CSI error, freq is stable and line count changed.

    0x7A = 0xF or 0x4; Different CSI errors

    0x7B = 0x14 or 0x1. CSI error count

    What this is pointing to is that you are getting CSI errors. What is your set-up? Imager->SER->DES->SoC?

    Also, what is the value of registers 0x04, 0x1f, 0x35, 0x4c, 0x4d, 0x4e, 0x58, 0x6d, 0x7d on the ds90UB954? Please read these registers twice because there's some Clear on read registers so we want to know which errors are recurring, so you can post both results in your response. For example, read these registers, wait about 10 secs, then read these registers again. Pleas post results from both times you read these registers in your response.

    These registers are also available in our DS90UB954-Q1 Datasheet for future reference.

    Regards,
    Mandeep Singh

  • Hi 

    0x4E = 0x6D; Line length changed, FPD3 encoder error, CSI error, freq is stable and line count changed.

    0x7A = 0xF or 0x4; Different CSI errors

    0x7B = 0x14 or 0x1. CSI error count;

    So, It's mean that have a trouble betwen 953 and 954?

  • Please check the log!

    Can I say there are some connect-problem about 953 &954?

    CrashLog_Case4.rar

  • How Understand the sentence "What this is pointing to is that you are getting CSI errors."

    Who make the "CSI errors" ?

  • Hi,

    I went through your log and I noticed that during your initialization you are getting some errors but they immediately disappear which is normal to occur because you are initializing the imager and devices, so this is okay.


    The log file shows that you are getting some forward channel and back channel errors from: 08:25:09.797 -  08:36:38.916

    - I'm not sure what you were doing here before this happened but these go away towards the end and from time 08:36:40.377- 08:46:46.137, it shows that the system is running well without any issues.

    0x04 = 0xDf; Valid Refclk, lock good
    0x1f = ?
    0x35 = 0x00; No CSI Data at the TX port.
    0x4c = 0x1; Read/Write port 0
    0x4D = 0x3; LOCK and Port status good, no errors.
    0x4e = 0x4; Freq is stable. no csi error. Good.
    0x58 = ?
    0x6d = ?
    0x7D = ?
    0x33 = ?
    0x34 = ?
    0x20 = ?

    However, I noticed that there's no CSI data being forwarded to the CSI TX port. Are you forwarding the CSI data to the AP Qualcomm? and capturing that information? If not, you can follow the steps below from the datasheet.

     

    Regards,
    Mandeep Singh

    P.S. To answer your other questions.

    How Understand the sentence "What this is pointing to is that you are getting CSI errors."

    - What that means is that those registers are showing that you are getting CSI errors.

    Who make the "CSI errors" ?

    - The imager as it is the CSI source.

    So, It's mean that have a trouble betwen 953 and 954?

    - No, it does not mean that.

  • In case the image didn't get copied for how to enable/disable CSI output from 954, so please refer to section 7.4.28.1 in the DS90UB954-Q1 Datasheet.

  • Hello Mandeep Singh

    Today, a crash occurs in the customer test. The latest abnormal register values are as follows.

    Please help to analyze the reasons.

    I have a summary.

    953 Register
    0x5E = 0x04( should be 0x00) 
    0x5F = 0x44( should be 0x00) 
    954 Register
    0x0E = 0x5( should be 0x4);GPIO_PIN_STS
    0x4D = 0x3( should be 0x3) ; RX_PORT_STS1;Lock status changed but system is locked to input and Pass bit is high.
    0x4E = 0xC( should be 0x4); RX_PORT_STS2 ;Line length changed, FPD3 encoder error, CSI error, freq is stable and line count changed.
    0x54 = 0x2( should be 0x0)  SENSOR_STS_3
    0x7A = 0x4 ( should be 0x0)  CSI_RX_STS 
    0x7B = 0x1 ( should be 0x0)  CSI error count.
  • Hello Mandeep Singh

    I have a statistical table and Log file named  Case 11.


     

    CrashLog_Case11.rar

  • Hello,

    My suggestion would be to not look at the initial values but read these registers twice as I had mentioned earlier. Errors that keep recurring are the ones that should be addressed. Nevertheless, I think we've already established that you are seeing CSI errors. Did you do anything differently in this last test? In case 7, when there's no crash, are you able to capture video?

    We need to narrow down where the issue is occurring.

    1) Can you enable PatGen (Pattern generation) in the DS90UB954-Q1 and try to capture that video output? Please share the reg dump of Des when you do this and please read the register twice.

    2) Once this is completed, please disable PatGen on the DS90UB954-Q1 and enable it on the DS90UB953-Q1 and share the reg dump of that both Ser and Des in that Case. Please read the registers twice. For example, read registers, wait 10secs then read again.

    Regards,
    Mandeep Singh

  • Hello,

    Any update on Mandeep's questions? Or is this issue resolved?

    Thanks,

    Casey