STOPSTATEDAT: error for 2nd capture in imx8mp in ISI interface.

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

STOPSTATEDAT: error for 2nd capture in imx8mp in ISI interface.

1,431 Views
mukesh_kumar
Contributor III

Hi,

In imx8mplus with isi interface, when i capture the raw image using the command :

v4l2-ctl -d 1 -v width=1920,height=1080,pixelformat=GB12 --stream-mmap --stream-count=1 --stream-to=gbrg_test.raw

the first capture was proper, but when i try to capture the again using the same command it is throwing the dphy status error mentioning : STOPSTATEDAT and STOPSTATECLK.

the logs for second capture are as below:


isi-capture 32e00000.isi:cap_device: mxc_isi_cap_g_selection
isi-capture 32e00000.isi:cap_device: mxc_isi_cap_g_fmt_mplane
isi-capture 32e00000.isi:cap_device: mxc_isi_cap_enum_fmt
isi-capture 32e00000.isi:cap_device: mxc_isi_cap_enum_fmt
isi-capture 32e00000.isi:cap_device: mxc_isi_cap_s_fmt_mplane, fmt=0x32314247
isi-capture 32e00000.isi:cap_device: mxc_isi_cap_try_fmt_mplane
isi-capture 32e00000.isi:cap_device: mxc_isi_cap_g_selection
isi-capture 32e00000.isi:cap_device: mxc_isi_cap_g_selection
isi-capture 32e00000.isi:cap_device: cap_vb2_queue_setup, buf_n=4, size=4147200
cap_vb2_queue_setup, buf_n=4, size=4147200
isi-capture 32e00000.isi:cap_device: cap_vb2_buffer_prepare
isi-capture 32e00000.isi:cap_device: cap_vb2_buffer_prepare
isi-capture 32e00000.isi:cap_device: cap_vb2_buffer_prepare
isi-capture 32e00000.isi:cap_device: cap_vb2_buffer_prepare
isi-capture 32e00000.isi:cap_device: mxc_isi_cap_g_fmt_mplane
isi-capture 32e00000.isi:cap_device: mxc_isi_cap_streamon

input fmt RGB4
output fmt GB12
isi-capture 32e00000.isi:cap_device: cap_vb2_start_streaming
isi-capture 32e00000.isi:cap_device: cap_vb2_start_streaming: num_plane=0 discard_size=4149248 discard_buffer=0000000012832bde

mxc-mipi-csi2.0: mipi_csis_s_stream: 1, state: 0x0

mxc-mipi-csi2.0: fmt: 0x3012, 1920 x 1080

mxc-mipi-csi2.0: --- mipi_csis_s_stream ---
mxc-mipi-csi2.0: CSIS_VERSION[0]: 0x03060301
mxc-mipi-csi2.0: CSIS_CMN_CTRL[4]: 0x00004b05
mxc-mipi-csi2.0: CSIS_CLK_CTRL[8]: 0x000f0000
mxc-mipi-csi2.0: CSIS_INTMSK[10]: 0x0fffff1f
mxc-mipi-csi2.0: CSIS_INTSRC[14]: 0x00000000
mxc-mipi-csi2.0: CSIS_DPHYSTATUS[20]: 0x000000f1
mxc-mipi-csi2.0: CSIS_DPHYCTRL[24]: 0x0980001f
mxc-mipi-csi2.0: CSIS_DPHYBCTRL_L[30]: 0x000001f4
mxc-mipi-csi2.0: CSIS_DPHYBCTRL_H[34]: 0x00000000
mxc-mipi-csi2.0: CSIS_DPHYSCTRL_L[38]: 0x00000000
mxc-mipi-csi2.0: CSIS_DPHYSCTRL_H[3c]: 0x00000000
mxc-mipi-csi2.0: CSIS_ISPCONFIG_CH0[40]: 0x000000b0
mxc-mipi-csi2.0: CSIS_ISPCONFIG_CH1[50]: 0x000008fd
mxc-mipi-csi2.0: CSIS_ISPCONFIG_CH2[60]: 0x000008fe
mxc-mipi-csi2.0: CSIS_ISPCONFIG_CH3[70]: 0x000008ff
mxc-mipi-csi2.0: CSIS_ISPRESOL_CH0[44]: 0x04380780
mxc-mipi-csi2.0: CSIS_ISPRESOL_CH1[54]: 0x80008000
mxc-mipi-csi2.0: CSIS_ISPRESOL_CH2[64]: 0x80008000
mxc-mipi-csi2.0: CSIS_ISPRESOL_CH3[74]: 0x80008000
mxc-mipi-csi2.0: CSIS_ISPSYNC_CH0[48]: 0x00000000
mxc-mipi-csi2.0: CSIS_ISPSYNC_CH1[58]: 0x00000000
mxc-mipi-csi2.0: CSIS_ISPSYNC_CH2[68]: 0x00000000
mxc-mipi-csi2.0: CSIS_ISPSYNC_CH3[78]: 0x00000000
mxc-mipi-csi2.0: --- mipi_csis_s_stream ---
mxc-mipi-csi2.0: GPR_GASKET_0_CTRL[60]: 0xffff8000
mxc-mipi-csi2.0: GPR_GASKET_0_HSIZE[64]: 0xffff8000
mxc-mipi-csi2.0: GPR_GASKET_0_VSIZE[68]: 0xffff8000
isi-capture 32e00000.isi:cap_device: mxc_isi.0.capture is no v4l2 subdev
isi-capture 32e00000.isi:cap_device: mxc_isi_cap_g_fmt_mplane

 

the logs for first capture is exact same except below change:

mxc-mipi-csi2.0: CSIS_DPHYSTATUS[20]: 0x0000000

can anyone help me to resolve this issue.

Thanks and regards,

Mukesh

 

Tags (3)
0 Kudos
Reply
3 Replies

1,424 Views
quercuspau
Contributor II

Hi,

Im facing the same problem with CSIS_DPHYSTATUS when i trying to capture RAW10 with ov5640 or imx290. The first capture is fine, but the second one (third, fourth...) are blocked.  The only way to capture data again is reboot system or reboot camera, CSI and IMX8_media_dev driver modules.

BR

0 Kudos
Reply

1,415 Views
quercuspau
Contributor II

Hi @mukesh_kumar ,

I was having this issue with kernel 5.10.35 with kernel 5.10.52, this problem is gone

BR

0 Kudos
Reply

1,373 Views
Bio_TICFSL
NXP TechSupport
NXP TechSupport

Good

0 Kudos
Reply