AR0341 Sensor module with 96717 Serializer board not having any MCLK chip on board but Nvidia is giving 25MHz MCLK input to sensor module

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

Hi, We are having AR0341 with MAX96717 Serializer sensor module board, which is not having any master clock chip/register. But when we are running nvsipl_camera with our driver we figured out that Sensor module is getting 25MHz MCLK. We need to know who is generating this clock and our driver settings are for 27MHz.
We checked the Nvidia source code serializer file “cdi_max96717f.c” where “GenerateClock” function can generated 24 or 25MHz clock but that function is not getting called then who is generating 25MHz clock to sensor serializer?

Thanks
Mayur

Camera driver development is out of the forum support scope. Please reach out for support through NVOnline.

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