JP 5.0.2 Mipi Camera Stream Not Opening

[burakozbek]

Hello all,

I have developed a camera sensor driver on Jetson Xavier NX Kernel 35.1. The camera driver is successfully probing. I2C communication is running successfully. There is no problem in writing and reading to registers. However, when I try to open a stream with gstreamer or when I try to record raw data with v4l2-ctl, the camera stream does not open.

When the stream cannot be opened, the kernel logs are as follows.

tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[  173.030123] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[  173.041955] (NULL device *): vi_capture_control_message: NULL VI channel received
[  173.042156] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=0, csi_port=0
[  173.042392] (NULL device *): vi_capture_control_message: NULL VI channel received
[  173.042550] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 0 vc- 0
[  173.043125] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[  175.557930] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[  175.558187] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[  175.559328] (NULL device *): vi_capture_control_message: NULL VI channel received
[  175.559491] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=0, csi_port=0
[  175.559698] (NULL device *): vi_capture_control_message: NULL VI channel received
[  175.559873] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 0 vc- 0
[  175.560486] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel

If anyone has had such a problem before, I would like your help.

[ShaneCCC]

Get the trace log to analysis.

https://elinux.org/Jetson/l4t/Camera_BringUp

[burakozbek]

Logs are located below.
Do you have any comments?

kworker/0:9-140     [000] ....   211.949025: rtcpu_string: tstamp:7377164991 id:0x04010000 str:"VM0 activating."
     kworker/0:9-140     [000] ....   211.949028: rtcpu_vinotify_event: tstamp:7377804674 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:236073147872 data:0xcd9ce50010000000
     kworker/0:9-140     [000] ....   211.949030: rtcpu_vinotify_event: tstamp:7377804832 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:236073159616 data:0x0000000031000001
     kworker/0:9-140     [000] ....   211.949030: rtcpu_vinotify_event: tstamp:7377805007 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:236073214720 data:0xcd9ce20010000000
     kworker/0:9-140     [000] ....   211.949031: rtcpu_vinotify_event: tstamp:7377805159 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:236073226656 data:0x0000000031000002
 vi-output, ar03-2840    [001] ....   214.527493: tegra_channel_capture_setup: vnc_id 0 W 1920 H 1536 fmt c4
     kworker/0:9-140     [000] ....   214.589377: rtcpu_vinotify_event: tstamp:7459728573 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:238696620736 data:0xcd9ce50010000000
     kworker/0:9-140     [000] ....   214.589381: rtcpu_vinotify_event: tstamp:7459728730 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:238696663520 data:0x0000000031000001
     kworker/0:9-140     [000] ....   214.589382: rtcpu_vinotify_event: tstamp:7459728904 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:238696682080 data:0xcd9ce20010000000
     kworker/0:9-140     [000] ....   214.589383: rtcpu_vinotify_event: tstamp:7459729054 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:238696742496 data:0x0000000031000002

[ShaneCCC]

Looks like NVCSI/VI didn’t receive any validate data from MIPI bus.
You may need to probe the MIPI signal to confirm.