SMFC 0 frame lost error interrupt

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

SMFC 0 frame lost error interrupt

Jump to solution
1,704 Views
suryag
Contributor II

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

Tags (3)
0 Kudos
1 Solution
995 Views
suryag
Contributor II

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

View solution in original post

0 Kudos
5 Replies
995 Views
Yuri
NXP Employee
NXP Employee

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).

995 Views
suryag
Contributor II

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.


Scenario 1:
Camera capture frame size: 1280x720 @30 FPS means 30 vsync per second
IDMAC CH0 frame size: 1280x720, IDMAC CH0 EOF interrupt is generating 30 times and there is no SMFC0 frame lost interrupt.

Scenario 2::
Camera capture frame size: 1280x360 @30 FPS means 30 vsync per second
IDMAC CH0 frame size: 1280x360, IDMAC CH0 EOF interrupt is generating only 15 times and SMFC0 frame lost interrupt is generating 15 times

Camera clock (Ipu csi clk) : 75 MHz

Camera VSYNC( IPU_CSI_VSYNC) : 30 fps

HSP CLK : 254 MHz

Scenario 3:
Camera capture frame size: 1280x720 @15 FPS means 15 vsync per second
IDMAC CH0 frame size: 1280x720, IDMAC CH0 EOF interrupt is generating 15 times and there is no SMFC0 frame lost interrupt.

Scenario 4::
Camera capture frame size: 1280x360 @15 FPS means 15 vsync per second
IDMAC CH0 frame size: 1280x360, IDMAC CH0 EOF interrupt is generating only 7.5 times and SMFC0 frame lost interrupt is generating 7.5 times

Could you please analyse the above scenario's and provide root cause of the problem?
Where can i get the SMFC DMA channels information?

0 Kudos
996 Views
suryag
Contributor II

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

0 Kudos
995 Views
aravinthkumarja
Senior Contributor II

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.

0 Kudos
995 Views
Yuri
NXP Employee
NXP Employee

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.

0 Kudos