IMX415 3480*2160 60fpsjet

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1 
tegra-vi4 15700000.vi: Status:  4 channel:00 frame:00B5
[  529.896502] tegra-vi4 15700000.vi:      timestamp sof 537715891904 eof 537715900192 data 0x00000100
[  529.905630] tegra-vi4 15700000.vi:      capture_id 209 stream  4 vchan  0
[  530.092673] tegra-vi4 15700000.vi: PXL_SOF syncpt timeout! err = -11
[  530.099251] tegra-vi4 15700000.vi: tegra_channel_error_recovery: attempting to reset the capture channel
[  530.109456] nvcsi 150c0000.nvcsi: csi4_stream_check_status (4) INTR_STATUS 0x00000004
[  530.117386] nvcsi 150c0000.nvcsi: csi4_stream_check_status (4) ERR_INTR_STATUS 0x00000004
[  530.126603] nvcsi 150c0000.nvcsi: csi4_stream_check_status (4) INTR_STATUS 0x00000004
[  530.134686] nvcsi 150c0000.nvcsi: csi4_stream_check_status (4) ERR_INTR_STATUS 0x00000004

This is the printed information of the operation of the device. May I ask what problem should I locate based on this information? Before, I have checked" Jetson/l4t/Camera BringUp - eLinux.org", it seems that I do not have this situation, the following is my device tree information:

				mode0 {
					mclk_khz = "24000";
					num_lanes = "4";
					tegra_sinterface = "serial_e";
					phy_mode = "DPHY";
					discontinuous_clk = "no";
					dpcm_enable = "false";
					cil_settletime = "0";

					active_w = "3840";
					active_h = "2160";
					pixel_t = "bayer_rggb10";
					csi_pixel_bit_depth = "10";
					readout_orientation = "90";
					line_length = "2250";
					inherent_gain = "1";
					mclk_multiplier = "24";
					pix_clk_hz = "576000000";

					gain_factor = "1000000";
					min_gain_val = "1000000";
					max_gain_val = "72000000";
					step_gain_val = "300000";
					default_gain = "1000000";
					min_hdr_ratio = "1";
					max_hdr_ratio = "1";
					framerate_factor = "1000000";
					min_framerate = "60400000";
					max_framerate = "60400000";
					step_framerate = "1";
					default_framerate= "60400000";
					exposure_factor = "1";
					min_exp_time = "44";
					max_exp_time = "100000";
					step_exp_time = "1";
					default_exp_time = "16667";/* us */
					embedded_metadata_height = "1";
				};```
2

I checked the mipi signal and found a signal in the data channel and mclk, and no signal in csi_clk

3

I used the TX2NX to drive the 4 lanes camera

4

Which Jetson device are you using @fary_young? Because then I can move this post over to the Jetson forums where you will likely find more information on this topic.

Thanks!

5

I’m using TX2 NX

6

Thank you!

8

hello fary_young,

basically, it’s due to capture engine cannot wait start-of-frame and report such failure.
could you please try review the MIPI signaling for the settle time, and you may tune this via device tree property setting, cil_settletime.

9

The imx415 data sheet mentioned that it needs to wait 8 frames, which is about 133308894 nanoseconds, but I still reported this error

[  158.667883] tegra-vi4 15700000.vi: PXL_SOF syncpt timeout! err = -11
[  158.674522] tegra-vi4 15700000.vi: tegra_channel_error_recovery: attempting to reset the capture channel
[  158.684988] nvcsi 150c0000.nvcsi: csi4_stream_check_status (4) ERROR_STATUS2VI_VC0 = 0x00000002
[  158.693832] nvcsi 150c0000.nvcsi: csi4_stream_check_status (4) ERROR_STATUS2VI_VC1 = 0x00000006
[  158.702571] nvcsi 150c0000.nvcsi: csi4_stream_check_status (4) ERROR_STATUS2VI_VC2 = 0x0000000e
[  158.711318] nvcsi 150c0000.nvcsi: csi4_stream_check_status (4) ERROR_STATUS2VI_VC2 = 0x0000000e
[  158.720126] nvcsi 150c0000.nvcsi: csi4_stream_check_status (4) INTR_STATUS 0x0001ee6a
[  158.728039] nvcsi 150c0000.nvcsi: csi4_stream_check_status (4) ERR_INTR_STATUS 0x0001ee6a
[  158.939958] tegra-vi4 15700000.vi: PXL_SOF syncpt timeout! err = -11
10

I don’t have IMX415 data sheet.
may I know what’s 8-fame actually means here… is it need to ignore first 8-frames, starting 9th frame for CSI channel?
if yes, you’ll need to program the VI driver to increase timeout values.

11

image
image906×812 76.4 KB

12

hello fary_young,

please try adding set_mode_delay_ms to configure the wait time for the first frame after capture starts, the unit is in milliseconds.

13

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.