The AR0234 binocular camera was adapted with AGX ORIN in version R35.3.1, and the argus preview was not available

After loading the relevant drivers, you can use the v4l2 command to print out the correct frame rate, as follows:

nvidia@nvidia-desktop:~$ v4l2-ctl -V -d /dev/video0 --stream-mmap
Format Video Capture:
	Width/Height      : 1920/1200
	Pixel Format      : 'RG12' (12-bit Bayer RGRG/GBGB)
	Field             : None
	Bytes per Line    : 3840
	Size Image        : 4608000
	Colorspace        : sRGB
	Transfer Function : Default (maps to sRGB)
	YCbCr/HSV Encoding: Default (maps to ITU-R 601)
	Quantization      : Default (maps to Full Range)
	Flags             : 
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 60.03 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 60.03 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 60.03 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 60.03 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 60.03 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 60.03 fps
<<<<<<<<<<^C

An error occurs while previewing the argus_camera screen. Use journalctl -f -u nvargus-daemon to view the log as follows:

nvidia@nvidia-desktop:~$ journalctl -f -u nvargus-daemon
-- Logs begin at Thu 2022-09-08 17:58:15 CST. --
2月 19 15:40:02 nvidia-desktop nvargus-daemon[1042]: (NvOdmDevice) Error ModuleNotPresent:  (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorViCsi.cpp, function initialize(), line 107)
2月 19 15:40:02 nvidia-desktop nvargus-daemon[1042]: NvPclDriverInitializeData: Unable to initialize driver v4l2_sensor
2月 19 15:40:02 nvidia-desktop nvargus-daemon[1042]: NvPclInitializeDrivers: error: Failed to init camera sub module v4l2_sensor
2月 19 15:40:02 nvidia-desktop nvargus-daemon[1042]: NvPclStartPlatformDrivers: Failed to start module drivers
2月 19 15:40:02 nvidia-desktop nvargus-daemon[1042]: NvPclStateControllerOpen: Failed ImagerGUID 7. (error 0xA000E)
2月 19 15:40:02 nvidia-desktop nvargus-daemon[1042]: NvPclOpen: PCL Open Failed. Error: 0xf
2月 19 15:40:02 nvidia-desktop nvargus-daemon[1042]: SCF: Error BadParameter: Sensor could not be opened. (in src/services/capture/CaptureServiceDeviceSensor.cpp, function getSourceFromGuid(), line 689)
2月 19 15:40:02 nvidia-desktop nvargus-daemon[1042]: SCF: Error BadParameter:  (propagating from src/services/capture/CaptureService.cpp, function addSourceByGuid(), line 453)
2月 19 15:40:02 nvidia-desktop nvargus-daemon[1042]: SCF: Error BadParameter:  (propagating from src/api/CameraDriver.cpp, function addSourceByIndex(), line 333)
2月 19 15:40:02 nvidia-desktop nvargus-daemon[1042]: SCF: Error BadParameter:  (propagating from src/api/CameraDriver.cpp, function getSource(), line 505)

What, I wonder, is the cause of this phenomenon? How can we fix it? Thank you.

it may be the root cause, may I know how many cameras in the system, could you please share the device tree settings for reference, especially the property settings within tegra-camera-platform{}

At present, only two nodes cam0 and cam1 are used, and the configuration is as follows:

/ {

	tegra-camera-platform {
		compatible = "nvidia, tegra-camera-platform";

		num_csi_lanes = <16>;
		max_lane_speed = <4000000>;
		min_bits_per_pixel = <10>;
		vi_peak_byte_per_pixel = <2>;
		vi_bw_margin_pct = <25>;
		isp_peak_byte_per_pixel = <5>;
		isp_bw_margin_pct = <25>;

		/**
		 * The general guideline for naming badge_info contains 3 parts, and is as follows,
		 * The first part is the camera_board_id for the module; if the module is in a FFD
		 * platform, then use the platform name for this part.
		 * The second part contains the position of the module, ex. "rear" or "front".
		 * The third part contains the last 6 characters of a part number which is found
		 * in the module's specsheet from the vender.
		 */
		modules {
			module0 {
				badge = "cam0_position0";
				position = "position0";
				orientation = "1";
				drivernode0 {
					/* Declare PCL support driver (classically known as guid)  */
					pcl_id = "v4l2_sensor";
					/* Driver v4l2 device name */
					devname = "sg2-ar0234c-gmsl2 30-0010";
					/* Declare the device-tree hierarchy to driver instance */
					proc-device-tree = "/proc/device-tree/i2c@3180000/tca9546@70/i2c@0/cam_0@1b";
				};
			};
			module1 {
				badge = "cam1_position1";
				position = "position1";
				orientation = "1";
				drivernode0 {
					/* Declare PCL support driver (classically known as guid)  */
					pcl_id = "v4l2_sensor";
					/* Driver v4l2 device name */
					devname = "sg2-ar0234c-gmsl2 30-0018";
					/* Declare the device-tree hierarchy to driver instance */
					proc-device-tree = "/proc/device-tree/i2c@3180000/tca9546@70/i2c@0/cam_1@1c";
				};
			};
			module2 {
				badge = "cam2_position2";
				position = "position2";
				orientation = "1";
				drivernode0 {
					/* Declare PCL support driver (classically known as guid)  */
					pcl_id = "v4l2_sensor";
					/* Driver v4l2 device name */
					devname = "sg2-ar0234c-gmsl2 31-001b";
					/* Declare the device-tree hierarchy to driver instance */
					proc-device-tree = "/proc/device-tree/i2c@3180000/tca9546@70/i2c@1/cam_2@1b";
				};
			};
			module3 {
				badge = "cam3_position3";
				position = "position3";
				orientation = "1";
				drivernode0 {
					/* Declare PCL support driver (classically known as guid)  */
					pcl_id = "v4l2_sensor";
					/* Driver v4l2 device name */
					devname = "sg2-ar0234c-gmsl2 31-001c";
					/* Declare the device-tree hierarchy to driver instance */
					proc-device-tree = "/proc/device-tree/i2c@3180000/tca9546@70/i2c@1/cam_3@1c";
				};
			};
			module4 {
				badge = "cam4_position4";
				position = "position4";
				orientation = "1";
				drivernode0 {
					/* Declare PCL support driver (classically known as guid)  */
					pcl_id = "v4l2_sensor";
					/* Driver v4l2 device name */
					devname = "sg2-ar0234c-gmsl2 32-001b";
					/* Declare the device-tree hierarchy to driver instance */
					proc-device-tree = "/proc/device-tree/i2c@3180000/tca9546@70/i2c@2/cam_4@1b";
				};
			};
			module5 {
				badge = "cam5_position5";
				position = "position5";
				orientation = "1";
				drivernode0 {
					/* Declare PCL support driver (classically known as guid)  */
					pcl_id = "v4l2_sensor";
					/* Driver v4l2 device name */
					devname = "sg2-ar0234c-gmsl2 32-001c";
					/* Declare the device-tree hierarchy to driver instance */
					proc-device-tree = "/proc/device-tree/i2c@3180000/tca9546@70/i2c@2/cam_5@1c";
				};
			};
			module6 {
				badge = "cam6_position6";
				position = "position6";
				orientation = "1";
				drivernode0 {
					/* Declare PCL support driver (classically known as guid)  */
					pcl_id = "v4l2_sensor";
					/* Driver v4l2 device name */
					devname = "sg2-ar0234c-gmsl2 33-001b";
					/* Declare the device-tree hierarchy to driver instance */
					proc-device-tree = "/proc/device-tree/i2c@3180000/tca9546@70/i2c@3/cam_6@1b";
				};
			};
			module7 {
				badge = "cam7_position7";
				position = "position7";
				orientation = "1";
				drivernode0 {
					/* Declare PCL support driver (classically known as guid)  */
					pcl_id = "v4l2_sensor";
					/* Driver v4l2 device name */
					devname = "sg2-ar0234c-gmsl2 33-001c";
					/* Declare the device-tree hierarchy to driver instance */
					proc-device-tree = "/proc/device-tree/i2c@3180000/tca9546@70/i2c@3/cam_7@1c";
				};
			};
		};
	};
};

hello FANYX,

please also refer to below for updating your position property,
it is now support 12-cam in the system now.
they are…

enum {
    bottomleft,    //video0
    centerleft,    //video1
    centerright,   //video2
    topleft,       //video3
    bottomright,   //video4
    topright,      //video5
    bottomcenter,  //video6
    topcenter,     //video7
    frontcenter,   //video8
    rearcenter,    //video9
    leftcenter,    //video10
    rightcenter,   //video11

BTW,
since you’ve only two camera nodes available, (or, you’ve only two camera device connected)
please also revise tegra-camera-platform{} to have two nodes. it’s must to have identical property settings with your physical camera setup.

I tried to change it to the following configuration, but it still couldn’t open.

tegra-camera-platform {
		compatible = "nvidia, tegra-camera-platform";

		num_csi_lanes = <16>;
		max_lane_speed = <4000000>;
		min_bits_per_pixel = <10>;
		vi_peak_byte_per_pixel = <2>;
		vi_bw_margin_pct = <25>;
		isp_peak_byte_per_pixel = <5>;
		isp_bw_margin_pct = <25>;

		/**
		 * The general guideline for naming badge_info contains 3 parts, and is as follows,
		 * The first part is the camera_board_id for the module; if the module is in a FFD
		 * platform, then use the platform name for this part.
		 * The second part contains the position of the module, ex. "rear" or "front".
		 * The third part contains the last 6 characters of a part number which is found
		 * in the module's specsheet from the vender.
		 */
		modules {
			module0 {
				badge = "cam0_bottomleft";
				position = "bottomleft";
				orientation = "1";
				drivernode0 {
					/* Declare PCL support driver (classically known as guid)  */
					pcl_id = "v4l2_sensor";
					/* Driver v4l2 device name */
					devname = "sg2-ar0234c-gmsl2 30-001b";
					/* Declare the device-tree hierarchy to driver instance */
					proc-device-tree = "/proc/device-tree/i2c@3180000/tca9546@70/i2c@0/cam_0@1b";
				};
			};
			module1 {
				badge = "cam1_centerleft";
				position = "centerleft";
				orientation = "1";
				drivernode0 {
					/* Declare PCL support driver (classically known as guid)  */
					pcl_id = "v4l2_sensor";
					/* Driver v4l2 device name */
					devname = "sg2-ar0234c-gmsl2 30-001c";
					/* Declare the device-tree hierarchy to driver instance */
					proc-device-tree = "/proc/device-tree/i2c@3180000/tca9546@70/i2c@0/cam_1@1c";
				};
			};

The log you see with dmesg is as follows:

hello FANYX,

is it complete failures? that’s error reported by encoder instead of camera software stack.
could you please have an alternative ways to follow below steps to enable VI tracing logs.

echo 1 > /sys/kernel/debug/tracing/tracing_on
echo 30720 > /sys/kernel/debug/tracing/buffer_size_kb
echo 1 > /sys/kernel/debug/tracing/events/tegra_rtcpu/enable
echo 1 > /sys/kernel/debug/tracing/events/freertos/enable
echo 2 > /sys/kernel/debug/camrtc/log-level
echo > /sys/kernel/debug/tracing/trace
cat /sys/kernel/debug/tracing/trace

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