The usage of cam_fsync_program_abs_start_value API to control camera fsync

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
1

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.10.0
DRIVE OS 6.0.8.1
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other

Target Operating System
Linux
QNX
other

Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
2.1.0
other

Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other

Issue Description
I called the API cam_fsync_program_abs_start_value to control camera fsync between multi Orin-X EVB. I inserted group ID 0 with absolute TSC clock value which I want to start fsync. But this API returned CAM_FSYNC_GROUP_NOT_FOUND (value -2).

What should I do to clear this issue? Does this have a condition to apply fsync start time?

Error String
The CAM_FSYNC_GROUP_NOT_FOUND (-2) is returned

3

Dear @chobr84 ,
I notice nvsipl_camera uses this API. Did you the sample? May I know the camera module?

4

Dear @SivaRamaKrishnaNV

My SW is refered from nvsipl_camera application SW of nvidia. It’s not be refered nvsipl_sample.

The camera model which is show from nvsipl_camera SW are following models.

for valeo IMX728 cameras,

  • V1SIM728S1RU3120NB20_CPHY_x4
  • V1SIM728MPRU4120HD1_CPHY_x4
  • V1SIM728MPRU3030ND1_CPHY_x4

for valeo IMX623 cameras,

  • V1SIM623S5RU5195NC0_CPHY_x4

Or should I configure the dtsi file before flash to EVB?

path : /drive/drive-linux/kernel/source/hardware/nvidia/platform/t23x/automotive/kernel-dts/p3710/common/tegra234-p3710-0010.dtsi

            fsync-groups {
                    status = "disabled";
                    fsync-group@0 {
                            id = <0>;
                            status = "okay";
                            generators = <&gen0>, <&gen2>, <&gen3>;
                    };
                    fsync-group@1 {
                            id = <1>;
                            status = "okay";
                            generators = <&gen1>;
                    };
            };

The status of fsync-groups is “disabled”. Should I change this to “okay”?

How I can find the valid range of group ID in parameter?

Best Regards
Bongrae Cho

5

I solve this issue.

The dtsi configuration was modified for Drive AGX Orin-X EVB. So the status of fsync-groups should be “okay” from “disabled”.

Then API return is OK.