NVIDIA Drive - Unable to access the third camera

Please provide the following info (check/uncheck the boxes after creating this topic):
Software Version
DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.6 and DriveWorks 4.0
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other

Target Operating System
Linux
QNX
other

Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other

SDK Manager Version
1.9.1.10844
other

Host Machine Version
native Ubuntu 18.04
other

I am trying to access three camera through json file and it is throwing an error…

./sample_camera --rig=/usr/local/driveworks/data/samples/sensors/camera/camera/rig2.json
[29-09-2023 09:21:22] Platform: Detected DDPX - Tegra A
[29-09-2023 09:21:22] TimeSource: monotonic epoch time offset is 1695967337769573
[29-09-2023 09:21:22] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to eth0
[29-09-2023 09:21:22] TimeSource Eth: Lost PTP time synchronizaton. Synchronized time will not be available from this timesource.
[29-09-2023 09:21:22] TimeSource: Could not detect valid PTP time source at ‘eth0’. Fallback to CLOCK_MONOTONIC.
[29-09-2023 09:21:22] Platform: number of GPU devices detected 1
[29-09-2023 09:21:22] Platform: currently selected GPU device integrated ID 0
[29-09-2023 09:21:22] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks-4.0/bin/data/’: VirtualFileSystem: Failed to mount ‘/usr/local/driveworks-4.0/bin/data/[.pak]’
[29-09-2023 09:21:22] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-4.0/bin/…/data
[29-09-2023 09:21:22] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks-4.0/bin/…/data/’: VirtualFileSystem: Failed to mount ‘/usr/local/driveworks-4.0/bin/…/data/[.pak]’
[29-09-2023 09:21:22] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-4.0/data
[29-09-2023 09:21:22] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks-4.0/data/’: VirtualFileSystem: Failed to mount ‘/usr/local/driveworks-4.0/data/[.pak]’
[29-09-2023 09:21:22] SDK: No resources(.pak) mounted, some modules will not function properly
[29-09-2023 09:21:22] SDK: Create NvMediaDevice
[29-09-2023 09:21:22] SDK: Create NvMedia2D
[29-09-2023 09:21:22] SDK: use EGL display as provided
[29-09-2023 09:21:22] TimeSource: monotonic epoch time offset is 1695967337769572
[29-09-2023 09:21:22] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to eth0
[29-09-2023 09:21:22] TimeSource Eth: Lost PTP time synchronizaton. Synchronized time will not be available from this timesource.
[29-09-2023 09:21:22] TimeSource: Could not detect valid PTP time source at ‘eth0’. Fallback to CLOCK_MONOTONIC.
[29-09-2023 09:21:22] Initialize DriveWorks SDK v4.0.0
[29-09-2023 09:21:22] Release build with GNU 7.3.1 from no-gitversion-build against Drive PDK v5.2.6.0
[29-09-2023 09:21:22] Rig::fromFile: Loading rig file: /usr/local/driveworks/data/samples/sensors/camera/camera/rig2.json
[29-09-2023 09:21:22] rig::DatabaseOverlayer: Failed to open a file ‘/tmp/car_vin’ - file likely does not exist - skipping overlay
[29-09-2023 09:21:22] Driveworks exception thrown: DW_FILE_INVALID: JsonInputArchive: fail to parse json

terminate called after throwing an instance of ‘std::runtime_error’
what(): [2023-09-29 09:21:22] DW Error DW_FILE_INVALID executing DW function:
dwRig_initializeFromFile(&rigConfig, m_context, getArgument(“rig”).c_str())
at samples/sensors/camera/camera/main.cpp:212
Aborted (core dumped)
rig2.txt (3.2 KB)

Dear @siva.ariram,
Could you check connecting SF3324 camera at link1 as well.

In the process of testing nvsipl, I lost my display by ‘Sudo pkill X’, Now I am trying to get back the display

Xavier B is working fine, but the problem is with Xavier A, I can able to access it through SSH but not sure whether it is Xavier A or B.

Could you please provide a solution for this? Do I need to reflash the board ? is that the only solution?

Dear @siva.ariram,
Please reboot the target using aurix or hard reboot. eth0:200 interface IP can tell Xavier A/B. 10.42.0.28/29 denotes Xavier A/B.
Could you please file a seperate topic for display issue with details. This helps to provide better support for each topic

Back to the camera access error…I have tried with link 0 and 1, still the same error

I solved the display issue by reflashing the board.

rig_log.txt (14.0 KB)
@SivaRamaKrishnaNV I have uploaded the error file in here, I tried with link 1 and 0, but the third camera is not showing up. The file is working with Two cameras (SF3324 and SF3325)

Note: It is visualizing SF3324 and SF3325, even if I give both the camera name as SF3324.

Dear @siva.ariram,
Could you keep same camera type in one camera group. You can connect 2 SF3324 cameras to one port and connect other SF3325 to another camera group.

We have only one camera group cable with us!

Dear @siva.ariram,
using different camera module with a single camera group is not supported.

Thank you! Please let me know where can I find these camera group connectors. It is difficult to find them from nvidia shop!

Please reach out to your NVIDIA representative. He/she can assist you in sourcing these connectors effectively.

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