Hi,
We are working on i.MX6 S platform.
We are getting SMFC0 Frame lost error interrupt while doing the below operation
Camera --> CSI--> SMFC --> IDMAC CH0 --> Memory.
Could anyone provide the information about cause of the problem? Is there any document related SMFC FIFO?
How to fix the issue?
Thanks in advance.
SuryaG
Solved! Go to Solution.
Hi Yuri,
The above mentioned issue got solved.
Earlier, we are not updating the IPU_CSI0_SENS_FRM_SIZE register value with respect to capture frame size. We fixed the sensor frame size to 1280x720.
When we updating the IPU_CSI0_SENS_FRM_SIZE values, IDMAC CH0 EOF interrupt is generating perfectly what we expect.
Thanks & Regards
SuryaG
Perhaps we have a performance issue in the case ; please use Table 38-35 (Error
Interrupts Summary) of the i.MX6 S Reference Manual to define what registers can be
checked.
According to section 38.4.12.3 (Interrupt Generator) of the Reference Manual :
“The table below describes the error interrupts. The panic column indicates if
this signal is part of the logic generating the ipu_panic signal. The ipu_panic
signal can be used for indicating about errors that are result of data rate
problems. Such problems may be a result of the IPU running in slower clock then
required by the use case. This signal can be used in order to indicate the
system that the IPU can't handle the desired data rate. In that case the system
may need to increase the clock to the IPU or simplify the use case.”
If the panic signals are asserted for the case, please try to decrease screen
resolution and / or frame rate. Also, other system resource consuming processes,
such as USB / SD / SATA transfer, may affect. As result a general performance
issue may take place in the case. Perhaps it makes sense to try system prioritization
(such as provided by Linux nice command).
Hi Yuri,
Thanks for your response.
Currently we are working on LCD and Camera interfaces only. We are not using any other peripherals like USB/SD/SATA.
Please find the below environment settings:
Default:
Camera clock (Ipu csi clk) : 75 MHz
Camera VSYNC( IPU_CSI_VSYNC) : 30 fps
HSP CLK : 254 MHz
Camera will support different resolution (frame size) and different FPS.
When we change the frame height value only SMFC frame lose interrupt is generating.
Camera clock (Ipu csi clk) : 75 MHz
Camera VSYNC( IPU_CSI_VSYNC) : 30 fps
HSP CLK : 254 MHz
Scenario 3:Hi Yuri,
The above mentioned issue got solved.
Earlier, we are not updating the IPU_CSI0_SENS_FRM_SIZE register value with respect to capture frame size. We fixed the sensor frame size to 1280x720.
When we updating the IPU_CSI0_SENS_FRM_SIZE values, IDMAC CH0 EOF interrupt is generating perfectly what we expect.
Thanks & Regards
SuryaG
Hi all,
I am using same Camera --> CSI--> SMFC --> IDMAC CH0 --> Memory method, But i didn't get EOF interrupt.
i got this error
ERROR: v4l2 capture: mxc_v4l_dqueue timeout enc_counter 0
VIDIOC_DQBUF failed.
ERROR: v4l2 capture: VIDIOC_QBUF: buffer already queued
VIDIOC_QBUF failed
Can you help me how to fix this.
Hello,
The following may be helpful :
”Unable to capture video on IMX6Q”
< https://community.freescale.com/message/607111#607111 >
“CSI preview demo not working!”
< https://community.freescale.com/message/610124#610124 >
~Yuri.