Difference in Available Sensor modes when using RPi Camera V.2 with Orin Nano and Nano 2/4 GB

[roboteer]

I am using the same RPi Camera V.2 on the following Jetson Dev. Kits:

1. Nano 2GB and Nano 4GB Dev Kits.
2. Orin Nano Dev Kit.

From a bash terminal, when I invoked the command gst-launch-1.0 nvarguscamerasrc sensor-id=0, I got the following results:

1. For the Nano 2/4 GB Dev Kits I got 6 available Sensor Modes as shown below

GST_ARGUS: 3280 x 2464 FR = 21.000000 fps Duration = 47619048 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;

GST_ARGUS: 3264 x 1848 FR = 28.000001 fps Duration = 35714284 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;

GST_ARGUS: 1920 x 1080 FR = 29.999999 fps Duration = 33333334 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;

GST_ARGUS: 1640 x 1232 FR = 29.999999 fps Duration = 33333334 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;

GST_ARGUS: 1280 x 720 FR = 59.999999 fps Duration = 16666667 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;

GST_ARGUS: 1280 x 720 FR = 120.000005 fps Duration = 8333333 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;

2. For the Orin Nano Dev Kit I got only 5 available Sensor Modes as shown below

GST_ARGUS: 3280 x 2464 FR = 21.000000 fps Duration = 47619048 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;

GST_ARGUS: 3280 x 1848 FR = 28.000001 fps Duration = 35714284 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;

GST_ARGUS: 1920 x 1080 FR = 29.999999 fps Duration = 33333334 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;

GST_ARGUS: 1640 x 1232 FR = 29.999999 fps Duration = 33333334 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;

GST_ARGUS: 1280 x 720 FR = 59.999999 fps Duration = 16666667 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;

This sensor mode 1280 x 720 FR = 120 fps is “missing” on the Orin Nano, and I happen to need this mode to extend my work from the older Nano Dev Kit to the Orin Nano. Would NVIDIA be able or willing to “re-enable” the 120 fps sensor mode for the Orin Nano? I would very much appreciate that!!!

[ShaneCCC]

Please reference to below topic to add high frame sensor mode of imx219.

V4L2 driver returning empty and corrupted frame buffers from VIDIOC_DQBUF IOCTL

I read some more driver code and figured it out. I found this suspicious line in imx219.c: frame_length = (u32)(mode->signal_properties.pixel_clock.val * (u64)mode->control_properties.framerate_factor / mode->image_properties.line_length / val); At higher frame rates, frame_length was becoming smaller. When it got below about 500, the video glitching started happening. I haven’t read the entire IMX219 datasheet but I assume this is because it’s getting below some minimum active row (480) p…

[roboteer]

Hello @ShaneCCC

I very much appreciate your reference to this topic for JETSON NANO, but my issue is with the ORIN NANO, are you saying that the same solution will apply? I am just checking with you before digging into this approach further.

Thank you!

[ShaneCCC]

The sensor driver is the same. Suppose you can apply the high sensor frame rate mode manually.

Thanks