CameraMaster: master init failed with status = 10

[stefan65]

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

Trying to bring up camera, model: Ox03C10-EXAL-BA0C. Running a simple script to initialize camera with the following parameters:

paramsClient.parameters = “camera-name=F008A120RM0AV2,interface=csi-ab,output-format=yuv,link=0”
paramsClient.protocol = “camera.gmsl”;

and getting the following output:

[28-07-2023 18:00:46] Platform: Detected Drive Orin P3710
[28-07-2023 18:00:46] TimeSource: monotonic epoch time offset is 1690564757198777
[28-07-2023 18:00:46] TimeSourceVibranteLinux: detect valid PTP interface mgbe2_0
[28-07-2023 18:00:46] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to mgbe2_0
[28-07-2023 18:00:46] PTP Time is available from Eth Driver
[28-07-2023 18:00:46] Adding variable DW_Base:DW_Version
[28-07-2023 18:00:46] Added variable DW_Base:DW_Version
[28-07-2023 18:00:46] Platform: number of GPU devices detected 1
[28-07-2023 18:00:46] Platform: currently selected GPU device 0, Resource Data Dir: trt_08_05_10_03, Arch: ga10b
[28-07-2023 18:00:46] Platform: currently selected GPU device integrated ID 0
[28-07-2023 18:00:46] CUDLAEngine:getDLACount: CUDLA version is = 1003000
[28-07-2023 18:00:46] CUDLAEngine:getDLACount: Number of DLA devices = 2
[28-07-2023 18:00:46] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘./resources’: VirtualFileSystem: Failed to mount ‘./resources/resources.pak’
[28-07-2023 18:00:46] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/home/admin/test_ws/samples/build_orin/install/usr/local/driveworks/samples/bin/data’: VirtualFileSystem: Failed to mount ‘/home/admin/test_ws/samples/build_orin/install/usr/local/driveworks/samples/bin/data/resources.pak’
[28-07-2023 18:00:46] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks/data
[28-07-2023 18:00:46] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks/data’: VirtualFileSystem: Failed to mount ‘/usr/local/driveworks/data/resources.pak’
[28-07-2023 18:00:46] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-5.10/data
[28-07-2023 18:00:46] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks-5.10/data’: VirtualFileSystem: Failed to mount ‘/usr/local/driveworks-5.10/data/resources.pak’
[28-07-2023 18:00:46] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks/lib/libdw_base.so.5.10
[28-07-2023 18:00:46] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.10/targets/aarch64-Linux/lib/libdw_base.so.5.10
[28-07-2023 18:00:46] SDK: No resources(.pak) mounted, some modules will not function properly
[28-07-2023 18:00:46] egl::Display: found 1 EGL devices
[28-07-2023 18:00:46] egl::Display: use drm device: drm-nvdc
[28-07-2023 18:00:46] TimeSource: monotonic epoch time offset is 1690564757198777
[28-07-2023 18:00:46] TimeSourceVibranteLinux: detect valid PTP interface mgbe2_0
[28-07-2023 18:00:46] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to mgbe2_0
[28-07-2023 18:00:46] PTP Time is available from Eth Driver
[28-07-2023 18:00:46] Initialize DriveWorks SDK v5.10.87
[28-07-2023 18:00:46] Release build with GNU 9.3.0 from buildbrain-branch-0-g9a5b4670e12 against Drive PDK v6.0.6.0
[28-07-2023 18:00:46] SensorFactory::createSensor() → time.nvpps, nvpps-device=/dev/nvpps0
[28-07-2023 18:00:46] Can not create time sensor: DW_HAL_CANNOT_OPEN_CHANNEL: EndpointNVPPS: cannot open NVPPS device with name: /dev/nvpps0
Error: Permission denied
[28-07-2023 18:00:46] SensorFactory::createSensor() → camera.gmsl, camera-name=F008A120RM0AV2,interface=csi-ab,output-format=yuv,link=0
[28-07-2023 18:00:46] CameraBase: pool size set to 8
[28-07-2023 18:00:46] SensorFactory::createSensor() → camera.gmsl.master,
[28-07-2023 18:00:47] CameraMaster::parseDevBlock Getting device info list.
[28-07-2023 18:00:47] devBlock: 0 Slave = 0 Interface = csi-ab Camera_name = F008A120RM0AV2 Link = 0 GroupInit = 0 RecCfg = 1
[28-07-2023 18:00:47] Camera Match Name: F008A120RM0AV2 Description: Entron F008A120RM0A module - 120-deg FOV, 24-bit capture, MIPI-AR0820, MAX9295 linkIndex: 4294967295 serInfo.Name: MAX9295
[28-07-2023 18:00:47] Client, Setting up information for camera ID 0
[28-07-2023 18:00:47] Client, successfully found info for camera ID 0 bound to id 0
[28-07-2023 18:00:47] ImageStreamer(NvMedia → CUDA)
[28-07-2023 18:00:47] ImageStreamer(NvMedia → CUDA)
[28-07-2023 18:00:47] ImageStreamer(NvMedia → CUDA)
[28-07-2023 18:00:47] ImageStreamer(NvMedia → CUDA)
[28-07-2023 18:00:47] ImageStreamer(NvMedia → CUDA)
[28-07-2023 18:00:47] ImageStreamer(NvMedia → CUDA)
[28-07-2023 18:00:47] ImageStreamer(NvMedia → CUDA)
[28-07-2023 18:00:47] ImageStreamer(NvMedia → CUDA)
[28-07-2023 18:00:47] CameraClient: using NITO found at /usr/share/camera/F008A120RM0AV2.nito
CAMERA CREATED SUCCESSFULLY
[28-07-2023 18:00:47] SIPLMaster::SIPLMaster: Setting up master camera
[28-07-2023 18:00:47] Platform:
[28-07-2023 18:00:47] Platform Config:
[28-07-2023 18:00:47] Description:
[28-07-2023 18:00:47] Number of device blocks: 1
[28-07-2023 18:00:47] Device Block : 0
[28-07-2023 18:00:47] csiPort: 2
[28-07-2023 18:00:47] i2cDevice: 0
[28-07-2023 18:00:47] Deserializer Name: MAX96712
[28-07-2023 18:00:47] Deserializer Description: Maxim 96712 Aggregator
[28-07-2023 18:00:47] Deserializer i2cAddress: 41
[28-07-2023 18:00:47] Simulator Mode: 0
[28-07-2023 18:00:47] Passive Mode: 0
[28-07-2023 18:00:47] Phy Mode: 0
[28-07-2023 18:00:47] Number of camera modules: 1
[28-07-2023 18:00:47] CameraModule index: 0
[28-07-2023 18:00:47] Name :F008A120RM0AV2
[28-07-2023 18:00:47] Description: Entron F008A120RM0A module - 120-deg FOV, 24-bit capture, MIPI-AR0820, MAX9295
[28-07-2023 18:00:47] Serializer name: MAX9295
[28-07-2023 18:00:47] Serializer description: Maxim 9295 Serializer
[28-07-2023 18:00:47] Serializer i2cAdress: 98
[28-07-2023 18:00:47] EEPROM name: N24C64
[28-07-2023 18:00:47] EEPROM i2cAddress: 84
[28-07-2023 18:00:47] EEPROM description: N24C64 EEPROM
[28-07-2023 18:00:47] Sensor ID: 0
[28-07-2023 18:00:47] Sensor name: AR0820
[28-07-2023 18:00:47] Sensor description: OnSemi AR0820 Sensor
[28-07-2023 18:00:47] Sensor i2cAddress: 16
[28-07-2023 18:00:47] Sensor isTPGEnabled: 0
[28-07-2023 18:00:47] Sensor isTriggerMode: 1
[28-07-2023 18:00:47] cfa: 35
[28-07-2023 18:00:47] embeddedTopLines: 2
[28-07-2023 18:00:47] embeddedBottomLines: 4
[28-07-2023 18:00:47] inputFormat: 8
[28-07-2023 18:00:47] height: 2168
[28-07-2023 18:00:47] width: 3848
[28-07-2023 18:00:47] fps: 30.000000
[28-07-2023 18:00:47] Embedded Data: 0
[28-07-2023 18:00:47] CameraMaster available outputs: 1
[28-07-2023 18:00:47] CameraClient: setting pipeline config for camera ID 0
[28-07-2023 18:00:47] CameraMaster: master initiation
MAX96712: Revision 5 detected
MAX96712 Link 0: PHY optimization was enabled
[28-07-2023 18:00:48] CameraMaster: master init failed with status = 10
[28-07-2023 18:00:48] Driveworks exception thrown: DW_UNEXPECTED_EVENT: CameraMaster::bootstrap failed with sipl status 10

CANNOT START CAMERA
[28-07-2023 18:00:48] Deinit master camera
[28-07-2023 18:00:48] SIPLClient: ImageQueue shutdown
[28-07-2023 18:00:48] SIPLNotifier: Event notification queue shutdown
[28-07-2023 18:00:50] CameraClient: Stopping client
[28-07-2023 18:00:50] Releasing camera master

Emphasis mine. What is causing this error, and how to resolve?

[VickNV]

As mentioned on the NVIDIA ecosystem page (DRIVE AGX Orin Sensors & Accessories | NVIDIA Developer), contacting OmniVision is the best course of action for the ‘OmniVision OX03C10-EXAL-BA0C’ camera module issues. Also, it’s important to note that camera bring-up support is outside the scope of forum support.

[stefan65]

A more specific follow up then: what does the following (excerpt from previous post) error mean:

[28-07-2023 21:06:18] CameraMaster: master init failed with status = 10
[28-07-2023 21:06:18] Driveworks exception thrown: DW_UNEXPECTED_EVENT: CameraMaster::bootstrap failed with sipl status 10

Specifically what does the status value of 10 mean, because I believe this is generated by driveworks and not the camera internal code. Could you please confirm?

[VickNV]

The error you are encountering appears to be an unspecified error, as mentioned in the SIPL document. Since you are using an ecosystem module, you need to get OmniVision’s support accordingly.

[stefan65]

Looking further into this issue, I tried using the sipl query to find our gmsl camera in the sipl database using ./sipl_query
per this page: DriveWorks SDK Reference: Cameras Supported. with the following result:

sipl_output.txt (11.7 KB)

The camera we purchased per NVIDIA’s recommendation is Omnivison model OX03C10-EXAL-BA0C, and is listed and advertised on your website, DRIVE AGX Orin Sensors & Accessories | NVIDIA Developer as a supported camera. Similarly the Omnivision website, NVIDIA | OMNIVISION advertises it to be compatible with driveworks and the Orin platform.

However, we cannot find this camera in the list of supported cameras returned by ./sipl.

Could you please urgently clarify what is the right name in the sipl list that corresponds to the camera you are advertising to be compatible with our system.

Our DriveWorks version is 5.10 and the DriveOS version 6.0.6.

[VickNV]

I understand your concern regarding the compatibility of the Omnivision OX03C10-EXAL-BA0C camera module with our system. As mentioned on the ecosystem page, it is essential to carefully review the information provided as follows:

According to the ecosystem page, you are required to contact OmniVision, to obtain the camera modules, software, and associated support. The SDK Compatibility information on the page is ‘Contact Sensor Vendor’ for software compatibility, which means you need to check the information with OmniVision.