Hi team,
953 CSI-2 input is 800 Mbps, 954 CSI-2 output setting is also 800 Mbps.
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.
Hi team,
953 CSI-2 input is 800 Mbps, 954 CSI-2 output setting is also 800 Mbps.
Hi Yoshida-san,
Buffer overflow means your input rate is faster than your output rate.
Indirect registers 0x44-0x48 controls your CSI timing. By adjusting those values, you are changing the CSI timing to allow for more data to be sampled in HS mode.
The figure below shows the timing parameters these registers are changing:
Best,
Jiashow
Hi Nao,
The reason why your LP-11 timing is different is because the output is running at a different rate than your input. Our 954 deserializer outputs CSI data at a fixed rate that isn't always the same as the input rate. You don't want to change the LP-11 value because the LP-11 timing is already correct for the specified CSI rate.
Refer to section 7.4.21 in the datasheet for more information:
Hi, Jiashow
Yes. My customer is using one sensor.
Here is packet waveform of my customer system.
The yellow is CSI input data of UB953).
The blue is CSI output data of UB954.
Data bit timing is almost same. (560ns)
But, Idle timing is difference. Input data is 240ns. Output data is 600ns.
Our customer want to know how to fix it?
Do you have any ideas?
Regards,
Nao
Hi, Jiashow
This is zoom-out waveform.
Could you check it? Please tell me the comment.
I will ask my customer about #1 and #2 question.
#1 Are you seeing any errors other than buffer overflow?
- Please tell me the address of registers to check just in case.
#2 Could you zoom-in on your input side to provide the timing relationship LP-11, LP-01, LP-00, HS transition and make sure they meet the CSI spec?
Regards,
Nao