NV Power Mode: v4l2-ctl -d /dev/video0 -set-fmt-video=width=4032,height=3040,pixelformat=RG10 -set-ctrl bypass_mode=0,sensor_mode=0 dmesg Here’s what I ran (dmesg output is abbreviated): sudo jetson_clocks -show The primary difference being that Argus interfaces with the ISP while v4l2 does not: Given my albeit limited understanding of the Argus and v4l2 camera pipelines, I believe they should share the same MIPI CSI bandwidth performance characteristics. This change enabled v4l2-ctl to capture correctly at that resolution.
Arducam kindly provided a custom driver with a 4032x3040 at 15fps mode. To rule out v4l2-ctl being the limitation, I tested with the v4l2cuda sample app ( modified to support raw bayer output) and it exhibits the same behavior as v4l2-ctl. V4l2-ctl -d /dev/video0 -set-fmt-video=width=4032,height=3040,pixelformat=RG10 -set-ctrl bypass_mode=0,sensor_mode=0 -stream-mmap tegra_channel_error_status:error 20022 frame 90.Gst-launch-1.0 -e nvarguscamerasrc sensor-id=0 sensor-mode=0 ! 'video/x-raw(memory:NVMM),width=4032,height=3040,framerate=30/1' ! nvvidconv ! nvv4l2h265enc ! h265parse ! mp4mux ! filesink location=out.mp4Īnd just to clarify, Argus is 100% able to actually capture 4032x3040 at 30fps and encode at 30fps via nvv4l2h265enc/nvv4l2h264enc.
Here’s a breakdown of the functionality between Argus and v4l2 when running the Arducam drivers (where mode 0 = 4032x3040 at 30fps):
The Nvidia driver only provides 3840x2160 at 30fps and 1920x1080 at 60fps.
With the one that does work with v4l2-ctl I’ve been testing both the stock Nvidia and Arducam drivers, the latter which provides support for the full resolution mode 4032x3040 at 30fps. I’m testing on two Jetson Nano 2GB Dev Kits running L4T 32.6.1 - For some reason, only one of them is able to run v4l2-ctl (see here for more info).