Errors starting 7 nvarguscamersrc pipeline in R32.7.1(Jetpack 4.6.1)

[ShaneCCC]

Doesn’t find any incorrect for the position.
Do you verify v4l2-ctl to launch 7 camera simultaneously?
Please also check with D3 if any new driver update.

Thanks

[shassan1]

Can you please provide pipeline to test verify v4l2-ctl to launch 7 camera simultaneously.
I am unable to currently launch even a single camera using v4l2-ctl.

gst-launch-1.0 --gst-debug-level=1 v4l2src device=/dev/video0 ! ‘video/x-raw,width=1920,height=1080,format=(string)UYVY’ ! nvvidconv ! ‘video/x-raw(memory:NVMM),width=1920,height=1080,format=(string)I420’ ! nvoverlaysink

Setting pipeline to PAUSED …
Pipeline is live and does not need PREROLL …
Setting pipeline to PLAYING …
ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Internal data stream error.
Additional debug info:
gstbasesrc.c(3055): gst_base_src_loop (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
streaming stopped, reason not-negotiated (-4)
Execution ended after 0:00:00.000126953
Setting pipeline to PAUSED …
Setting pipeline to READY …
Setting pipeline to NULL …
Freeing pipeline …

[ShaneCCC]

Should be the v4l2-ctl instead of v4l2src

v4l2-ctl --set-fmt-video=width=1936,height=1096 -c bypass_mode=0 --stream-mmap -d /dev/video0&
v4l2-ctl --set-fmt-video=width=1936,height=1096 -c bypass_mode=0 --stream-mmap -d /dev/video1&
v4l2-ctl --set-fmt-video=width=1936,height=1096 -c bypass_mode=0 --stream-mmap -d /dev/video2&
v4l2-ctl --set-fmt-video=width=1936,height=1096 -c bypass_mode=0 --stream-mmap -d /dev/video3&
v4l2-ctl --set-fmt-video=width=1936,height=1096 -c bypass_mode=0 --stream-mmap -d /dev/video4&
v4l2-ctl --set-fmt-video=width=1936,height=1096 -c bypass_mode=0 --stream-mmap -d /dev/video5&

[shassan1]

@ShaneCCC

v4l2-ctl --set-fmt-video=width=1936,height=1096 -c bypass_mode=0 --stream-mmap -d /dev/video0&
v4l2-ctl --set-fmt-video=width=1936,height=1096 -c bypass_mode=0 --stream-mmap -d /dev/video1&
v4l2-ctl --set-fmt-video=width=1936,height=1096 -c bypass_mode=0 --stream-mmap -d /dev/video2&
v4l2-ctl --set-fmt-video=width=1936,height=1096 -c bypass_mode=0 --stream-mmap -d /dev/video3&
v4l2-ctl --set-fmt-video=width=1936,height=1096 -c bypass_mode=0 --stream-mmap -d /dev/video4&
v4l2-ctl --set-fmt-video=width=1936,height=1096 -c bypass_mode=0 --stream-mmap -d /dev/video5&

[ShaneCCC]

Sorry this command can tell if both video node working well.
Could you launch the command in 7 console to confirm both of them are able show the 30.09fps?
You can launch each video node manually in each console.

Thanks

[shassan1]

I am able to launch them in 7 separate consoles. The maximum fps reading in all consoles is 30.09 and minimum is 30.02.

[shassan1]

6 of them are still running and one stopped automatically are 5 minutes.

[ShaneCCC]

Please consult with D3 if any driver update for it.

Thanks

[shassan1]

According to them, the version i am using has best support for FPD-||| link board.
What you have concluded from your analysis? your findings might help them understand the issue better.

[shassan1]

Tried to relaunch the one that stopped, gives following error
desktop:~$ v4l2-ctl --set-fmt-video=width=1936,height=1096 -c bypass_mode=0 --stream-mmap -d /dev/video4&
[2] 10655
desktop:~$ VIDIOC_S_FMT: failed: Device or resource busy
VIDIOC_REQBUFS: failed: Device or resource busy

[ShaneCCC]

The v4l2-ctl command help to confirm the sensor driver and HW, if can’t run stability we would suspect the sensor driver or HW problem.

Thanks