Mipi csi2 problem

I have currently succeeded in generating the image using mipicsi2. However, sometimes it fails and I have to restart it. Here is the log printed by the system when it fails. Please take a look and help me out. Thank you.

hello Towe_Roll,

may I know which Jetpack release version you’re working with?
may I know what’s the actual use-case to reproduce such failure?

FYI,
we’ve seen an issue with JP-5.1.4/r35.6.0, and fix kernel panic when VI trying to recover camera stream.
please refer to Topic 305007 for the patches.

1、 R36 (release), REVISION: 5.0, GCID: 43688277, BOARD: generic, EABI: aarch64, DATE: Fri Jan 16 03:50:45 UTC 2026

KERNEL_VARIANT: oot

TARGET_USERSPACE_LIB_DIR=nvidia
TARGET_USERSPACE_LIB_DIR_PATH=usr/lib/aarch64-linux-gnu/nvidia

2、It’s just a nvarguscamerasrc pipeline. The problem usually occurs after multiple starts and stops of the pipeline.

One more thing to note, my sensor uses external triggering. The signal is provided to it via the PWM on the 40-pin connector of the Jetson.

That’s weird nvarguscamerasrc shouldn’t use vb2 buffer.

Should be v4l2 APP?

For the trigger mode try set timeout to infinite.

v4l2-ctl -c override_capture_timeout_ms=-1  

gst pipeline outpu

and then i use

v4l2-ctl -d /dev/video0 --set-fmt-video=width=1920,height=1200 --stream-mmap

Wha’t the format? nvarguscamerasrc don’t support YUV/RGB888.

And need -c bypass_mode=0 to switch to VI mode for v4l2-ctl command.

v4l2-ctl -d /dev/video0 --set-fmt-video=width=1920,height=1200 --stream-mmap -c bypass_mode=0

Sorry, ShaneCCC and JerryChang, let me restate my question. I used the following pipeline,

pipe = (
f"nvarguscamerasrc sensor-id={dev} wbmode=1 ! "
f"video/x-raw(memory:NVMM),width={width},height={height} ! "
"nvvidconv ! "
"nvv4l2h264enc bitrate=2000000 preset-level=1 maxperf-enable=true ! "
“h264parse ! rtph264pay name=pay0 pt=127 config-interval=1”
)

After some time, when I restarted the pipeline, I encountered this problem.

Then I used,

v4l2-ctl -d /dev/video0 --set-fmt-video=width=1920,height=1200 --stream-mmap

After testing whether the flow was normal, we encountered the same kernel error problem that we had faced at the beginning.

The argus log tell unable capture frame from the sensor and timeout. What’s the failed rate?

When you using v4l2-ctl to verify the sensor driver need -c bypass_mode=0 after launch argus camera.