Unable to set 2 fps in nvsipl

Please provide the following info (tick the boxes after creating this topic):
Software Version
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
1.9.3.10904
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

Hello

I am facing a very strange issue where in I am unable to set the fps for camera at 2 fps. I am able to set to 3 4 5 10 15 etc but when I set to 2 fps I get 1 fps only. I am using nvsipl. I am setting the fps in drive-foundation/platform-config/hardware/nvidia/platform/t23x/automotive/kernel-dts/p3710/common/tegra234-p3710-0010.dts. These are Quanta cameras and as per my latest understanding, generator 0 is the one connected to the camera, if that info makes any sense or of help.

Thanks!!
Jishnu

How do you set the FPS in the DTSI file?

Because you noticed the issue with a Quanta camera module and according to the camera ecosystem information, it should be supported by Quanta. Please report this to them. They will work with nvidia if needed.

@VickNV I usually change the value of freq_hz in the below snippet

/* EDGE_OUT #0 */
gen0: generator@380 {
reg = <0x380 0x80>;
freq_hz = <30>;
duty_cycle = <25>;
offset_ms = <0>;
status = “okay”;
};

so here above 30 I changed to 2. From Quanta what I remember is its generator 0 connected. Do you see any troubles? It works when I change to other numbers here.

Thank you for providing the details. Considering your observation, it would be beneficial to review the implementation of cam_fsync_program_group_generator_edges() in cam_fsync.c, which you have access to. This may help identify any potential issues or findings related to the observed behavior.

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