Please provide the following info (tick the boxes after creating this topic): Software Version
DRIVE OS 184.108.40.206
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
Target Operating System
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)
SDK Manager Version
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
I am trying to trigger the camera from external PPS. Currently I am able to ensure that PPS signal is fed and NVPPS_GETEVENT is detecting it.
From the driver code I am setting it into NVPPS_MODE_TIMER NVPPS_TSC_NSEC mode. I am not running PTP4L at the moment.
I will also add the logs of running nvsipl as well as driveworks camera sample here. Could you please help me understand why I don’t see the trigger to camera? I get 0 fps in nvsipl_camera application and timeout in dw camera application.
Since you’re using the Quanta IMX728 camera module (HZKJ_IMX728_ES2_V2_120FOV) and it’s supported by Quanta, have you confirmed with them if they’ve verified fsync with the camera module?
This could provide efficient clarification.
I spoke to Quanta. So they say if we could verify that the external trigger is reaching the deserialiser or the MFP2 pin then they could help us if the camera isn’t responding. As long as the trigger signal reaches the deserialiser they are confident camera should function since internally generated fysnc is working.
So can you help us understand if there is a way to verify this trigger is reaching the pin. Can we print or read some pin value? This will help us debug ahead and coordinate with Quanta if needed.
I’ll check your questions with our team and get back to you as soon as possible.
In the meantime, could you please provide details regarding any modifications you’ve made based on 220.127.116.11? Additionally, sharing the command and output of “nvsipl_camera” would be helpful for further investigation.
My target was to use driveworks and not nvsipl app. Nevertheless I understand the point you are referring to. I will try to run as per the document example and share the results. Let me re try and I will share newer logs. Meanwhile if there are more debug points that would be helpful especially since I am using driveworks sensor camera app.
Were you able to get some info on how I can tap on “if we could verify that the external trigger is reaching the deserialiser or the MFP2 pin then they could help us if the camera isn’t responding.” ? Any possible way to tap or print the values. We would like to know if the external trigger did create any Frame sync signal.
Sorry but I am a bit confused. Is heterogeneous Frame sync and NvPPS related? Quanta agreed about the missing implementation for Heterogeneous Frame sync. But they said NvPPS should work irrespective. Its something you may be able to help me resolve. I think Configuration for running NVPPS GPIO mode this question is the relevant question to ask for NvPPS case. As I understand from @SivaRamaKrishnaNV NvPPS may not exactly trigger the camera. it may only help align.
Now open question is
what is the device tree configuration for this ie is frame-sync group enabled? Or will it work with internal clock and no frame-sync is required?
Some info on how NvPPS helps us align and do correction of the timestamp