Driveworks sample_camera_usb failed

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-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

Hi,
I tried to run the sample_camera_usb, but I got errors.
Attach is the log.

dial@tegra-ubuntu: /us/local/driveworks/bin$ . /sample_camera_usb
programArguments: Missing argument ‘dwTracePath’ requested
[26-05-2023 18:38:56] Platform: Detected Drive Orin P3710
[26-05-2023 18:38:56] TimeSource: monotonic epoch time offset is 1685126129272543
[26-05-2023 18:38:56] TimeSourceVibranteLinux: detect valid PTP interface mgbe2_0
[26-05-2023 18:38:56] TimeSource: Could not detect valid PT time source at nvpps. Fallback to mgbe2 o
26-05-2023 18:38:56] PTP Time is available from Eth Driver
26-05-2023 18:38:56] Adding variable DW_Base: DW_Version
26-05-2023 18:38:56] Added variable DW_Base:DW_Version
26-05-2023 18:38:56] Platform: number of GPU devices detected 1
26-05-2023 18:38:56] Platform: currently selected GPU device 0, Resource Data Dir: trt_08_05_10_03, Arch: ga10b
26-05-2023 18:38:56] Platform: currently selected GPU device integrated ID O
26-05-2023 18:38:56] CUDLAEngine:getDLACount: CUDLA version is = 1003000
[26-05 -2023 18:38:56] CUDLAEngine:getDLACount: Number of DLA devices = 2
[26-05-2023 18:38:56] Context: :mountResourceCandidateDataPath resource FAILED to mount from ‘./resources’: VirtualFilesystem: Failed to mount ’ ./ resources/resources. pak’
[26-05-2023 18:38:56] Context:: mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks-5.10/bin/data’: VirtualfileSystem: Failed to mount ‘/usr/local/driveworks-5.10/bin/data/resources.pak’
26-05-2023 18:38:56] Context::findDataRootInPathwalk data/DATA_ROOT found at: /us/local/driveworks/data
[26-05-2023 18:38:56] Context: : mountResourceCandidateDataPath resource FAILED to mount from "/ust/local/driveworks/data: VirtualFilesystem: Failed to mount ‘/usr/local/driveworks-5.10/bin/data/resources.pak’
[26-05-2023 18:38:56] Context: :findDataRootInPathWalk data/DATA ROOT found at: /us/local/driveworks-5.10/data
[26-05-2023 18:38:56] Context: :mountResourceCandidateDataPath resource FAILED to mount from "/usr/local/driveworks-5.10/data’: VirtualfileSystem: Failed to mount ‘/usr/local/driveworks-5.10/bin/data/resources.pak’
05-2023 18:38:56] Context: :findResourcesPackageInPathwalk: Could not find ./resources/resources. pak in upto 7 parent directories from /us/local/driveworks-5.10/targets/aarch64-Linux/lib/libdw_base.so.5.10

05-2023 18:38:56] Context: :findResourcesPackageInPathwalk: Could not find ./resources/resources. pak in upto 7 parent directories from /us/local/driveworks-5.10/targets/aarch64-Linux/lib/libdw_base.so.5.10
05-2023 18:38:56] SDK: No resources (.pak) mounted, some modules will not function properly
05-2023 18:38:56] SDK: Use EGL display as provided
05-2023 18:38:56] TimeSource: monotonic epoch time offset is 1685126129272543
05-2023 18:38:56] TimeSourceVibranteLinux: detect valid PT interface mgbe2 o
6-05-2023 18:38:56] TimeSource: Could not detect valid PT time source at nvpps.
Fallback to mgbe2
26-05-2023 18:38:56] PTP Time is available from Eth Driver
26-05-2023 18:38:56] Initialize DriveWorks SDK V5.10.87
26-05-2023 18:38:56] Release build with GNU 9.3.0 from buildbrain-branch-0-g9a5b4670e12 against Drive PDK V6.0.6.0
26-05-2023 18:38:56] SensorFactory:: createSensor () → time.nvpps, nvpps-device=/dev/nvpps0
26-05-2023 18:38:56] Can not create time sensor: DW_HAL_CANNOT_OPEN_CHANNEL: EndpointNVPPS: cannot open NVPPS device with name: /dev/nvvpps0
Error: Permission denied
[26-05-2023 18:38:56] Initialize Driveworks VisualizationSDK v5.10.87
[26-05-2023 18:38:56] Initialize DriveWorksGLSDK V5.10.87
[26-05-2023 18:38:56] SensorFactory: : createSensor() → camera. usb, device=1, mode=0
[26-05-2023 18:38:56] CameraBase: pool size set to 8
[26-05-2023 18:38:56] Driveworks exception thrown: DW FILE NOT FOUND: CameraV4L: Could not open device /dev/video
terminate called after throwing an instance of ‘std: :runtime error’ what (): [2023-05-26 18:38:56] DW Error DW_FILE_NOT_FOUND executing DW function: dwSAL createSensor (&m camera, params, m sal)
at /us/local/driveworks/samples/src/sensors/camera/camera_usb/main.cpp:127
Aborted

Please double-check if any camera device is available as ‘/dev/video*’.

How can I reboot the nvidida device? If I reboot the GUI doesn’t work.

the folder video are not existing. I just wanted to try DriveWorks SDK Reference: USB Camera Capture Sample. Did I missed steps?

It seems that your USB camera is not being detected. Please try reconnecting it or consider using a different camera.

I tried it with two cameras and I got for both the same issue. They are both working on our old Xavier A. I tried the camera there too.
This error message is new.
[30-05-2023 18:36:43] Driveworks exception thrown: DW_FILE_NOT_FOUND: Rig::fromFile: cannot open file: /usr/local/driveworks-5.10/data/samples/sensors/camera/camera/rig.json

In addition I tried with SSH and git this error message.
nvidia1@tegra-ubuntu:/usr/local/driveworks/bin$ ./sample_camera
ProgramArguments: Missing argument ‘dwTracePath’ requested
GLFW error: 65544, X11: The DISPLAY environment variable is missing
WindowGLFW: Failed to initialize GLFW
terminate called after throwing an instance of ‘std::exception’
what(): std::exception
Aborted
I also found out that for the error
[30-05-2023 18:36:43] Driveworks exception thrown: DW_FILE_NOT_FOUND: Rig::fromFile: cannot open file: /usr/local/driveworks-5.10/data/samples/sensors/camera/camera/rig.json
The path /samples/sensors/camera/camera/rig.json doesn’t exist in my folder. I found this path in the Xavier A too.


How can I get the missing files?
I got all the files from Docker

I wanted to kindly request that you create separate topics for different issues you come across. This helps us organize and address each matter more efficiently. Thank you for your understanding and cooperation.

yeah of course.

I got the missing files now. I still get errors, but different now. I called ./sample_camera --write-file=/home/nvidia1/output_camera
nvidia1@tegra-ubuntu:/usr/local/driveworks/bin$ ./sample_camera --write-file=/home/nvidia1/output_camera
ProgramArguments: Missing argument ‘dwTracePath’ requested
[31-05-2023 22:38:54] Platform: Detected Drive Orin P3710
[31-05-2023 22:38:54] TimeSource: monotonic epoch time offset is 1685572595922502
[31-05-2023 22:38:54] TimeSourceVibranteLinux: detect valid PTP interface mgbe2_0
[31-05-2023 22:38:54] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to mgbe2_0
[31-05-2023 22:38:54] PTP Time is available from Eth Driver
[31-05-2023 22:38:54] Adding variable DW_Base:DW_Version
[31-05-2023 22:38:54] Added variable DW_Base:DW_Version
[31-05-2023 22:38:54] Platform: number of GPU devices detected 1
[31-05-2023 22:38:54] Platform: currently selected GPU device 0, Resource Data Dir: trt_08_05_10_03, Arch: ga10b
[31-05-2023 22:38:54] Platform: currently selected GPU device integrated ID 0
[31-05-2023 22:38:54] CUDLAEngine:getDLACount: CUDLA version is = 1003000
[31-05-2023 22:38:54] CUDLAEngine:getDLACount: Number of DLA devices = 2
[31-05-2023 22:38:54] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘./resources’: VirtualFileSystem: Failed to mount ‘./resources/resources.pak’
[31-05-2023 22:38:54] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks-5.10/bin/data’: VirtualFileSystem: Failed to mount ‘/usr/local/driveworks-5.10/bin/data/resources.pak’
[31-05-2023 22:38:54] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-5.10/bin/…/data
[31-05-2023 22:38:54] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks-5.10/bin/…/data’: VirtualFileSystem: Failed to mount ‘/usr/local/driveworks-5.10/bin/…/data/resources.pak’
[31-05-2023 22:38:54] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-5.10/data
[31-05-2023 22:38:54] 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’
[31-05-2023 22:38:54] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.10/bin/…/lib/libdw_base.so.5.10
[31-05-2023 22:38:54] 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
[31-05-2023 22:38:54] SDK: No resources(.pak) mounted, some modules will not function properly
[31-05-2023 22:38:54] SDK: use EGL display as provided
[31-05-2023 22:38:54] TimeSource: monotonic epoch time offset is 1685572595922502
[31-05-2023 22:38:54] TimeSourceVibranteLinux: detect valid PTP interface mgbe2_0
[31-05-2023 22:38:54] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to mgbe2_0
[31-05-2023 22:38:54] PTP Time is available from Eth Driver
[31-05-2023 22:38:54] Initialize DriveWorks SDK v5.10.87
[31-05-2023 22:38:54] Release build with GNU 9.3.0 from buildbrain-branch-0-g9a5b4670e12 against Drive PDK v6.0.6.0
[31-05-2023 22:38:54] SensorFactory::createSensor() → time.nvpps, nvpps-device=/dev/nvpps0
[31-05-2023 22:38:54] Can not create time sensor: DW_HAL_CANNOT_OPEN_CHANNEL: EndpointNVPPS: cannot open NVPPS device with name: /dev/nvpps0
Error: Permission denied
[31-05-2023 22:38:54] fromFile: Loading rig file: /usr/local/driveworks-5.10/data/samples/sensors/camera/camera/rig.json
[31-05-2023 22:38:54] rig::DatabaseOverlayer: Failed to open a file ‘/tmp/car_vin’ - file likely does not exist - skipping overlay
[31-05-2023 22:38:54] No valid data file found for camera:sample0 in parameter string: camera-name=F008A120RM0AV2,interface=csi-ab,CPHY-mode=1,link=0,output-format=processed,async-record=1,file-buffer-size=16777216 (using configuration folder /usr/local/driveworks-5.10/data/samples/sensors/camera/camera/)
[31-05-2023 22:38:54] rig::DatabaseOverlayer: Failed to open a file ‘/tmp/car_vin’ - file likely does not exist - skipping overlay
onInitialize: creating camera.gmsl with params: camera-name=F008A120RM0AV2,interface=csi-ab,CPHY-mode=1,link=0,output-format=processed,async-record=1,file-buffer-size=16777216
[31-05-2023 22:38:54] SensorFactory::createSensor() → camera.gmsl, camera-name=F008A120RM0AV2,interface=csi-ab,CPHY-mode=1,link=0,output-format=processed,async-record=1,file-buffer-size=16777216
[31-05-2023 22:38:54] CameraBase: pool size set to 8
[31-05-2023 22:38:54] SensorFactory::createSensor() → camera.gmsl.master,
[31-05-2023 22:38:55] CameraMaster::parseDevBlock Getting device info list.
[31-05-2023 22:38:55] devBlock: 0 Slave = 0 Interface = csi-ab Camera_name = F008A120RM0AV2 Link = 0 GroupInit = 0 RecCfg = 1
[31-05-2023 22:38:55] Camera Match Name: F008A120RM0AV2 Description: Entron F008A120RM0A module - 120-deg FOV, 24-bit capture, MIPI-AR0820, MAX9295 linkIndex: 4294967295 serInfo.Name: MAX9295
[31-05-2023 22:38:55] Client, Setting up information for camera ID 0
[31-05-2023 22:38:55] Client, successfully found info for camera ID 0 bound to id 0
[31-05-2023 22:38:55] ImageStreamer(NvMedia → CUDA)
[31-05-2023 22:38:55] ImageStreamer(NvMedia → CUDA)
[31-05-2023 22:38:55] ImageStreamer(NvMedia → CUDA)
[31-05-2023 22:38:55] ImageStreamer(NvMedia → CUDA)
[31-05-2023 22:38:55] ImageStreamer(NvMedia → CUDA)
[31-05-2023 22:38:55] ImageStreamer(NvMedia → CUDA)
[31-05-2023 22:38:55] ImageStreamer(NvMedia → CUDA)
[31-05-2023 22:38:55] ImageStreamer(NvMedia → CUDA)
[31-05-2023 22:38:55] CameraClient: using NITO found at /usr/share/camera/F008A120RM0AV2.nito
[31-05-2023 22:38:55] SIPLMaster::SIPLMaster: Setting up master camera
[31-05-2023 22:38:55] Platform:
[31-05-2023 22:38:55] Platform Config:
[31-05-2023 22:38:55] Description:
[31-05-2023 22:38:55] Number of device blocks: 1
[31-05-2023 22:38:55] Device Block : 0
[31-05-2023 22:38:55] csiPort: 2
[31-05-2023 22:38:55] i2cDevice: 0
[31-05-2023 22:38:55] Deserializer Name: MAX96712
[31-05-2023 22:38:55] Deserializer Description: Maxim 96712 Aggregator
[31-05-2023 22:38:55] Deserializer i2cAddress: 41
[31-05-2023 22:38:55] Simulator Mode: 0
[31-05-2023 22:38:55] Passive Mode: 0
[31-05-2023 22:38:55] Phy Mode: 1
[31-05-2023 22:38:55] Number of camera modules: 1
[31-05-2023 22:38:55] CameraModule index: 0
[31-05-2023 22:38:55] Name :F008A120RM0AV2
[31-05-2023 22:38:55] Description: Entron F008A120RM0A module - 120-deg FOV, 24-bit capture, MIPI-AR0820, MAX9295
[31-05-2023 22:38:55] Serializer name: MAX9295
[31-05-2023 22:38:55] Serializer description: Maxim 9295 Serializer
[31-05-2023 22:38:55] Serializer i2cAdress: 98
[31-05-2023 22:38:55] EEPROM name: N24C64
[31-05-2023 22:38:55] EEPROM i2cAddress: 84
[31-05-2023 22:38:55] EEPROM description: N24C64 EEPROM
[31-05-2023 22:38:55] Sensor ID: 0
[31-05-2023 22:38:55] Sensor name: AR0820
[31-05-2023 22:38:55] Sensor description: OnSemi AR0820 Sensor
[31-05-2023 22:38:55] Sensor i2cAddress: 16
[31-05-2023 22:38:55] Sensor isTPGEnabled: 0
[31-05-2023 22:38:55] Sensor isTriggerMode: 1
[31-05-2023 22:38:55] cfa: 35
[31-05-2023 22:38:55] embeddedTopLines: 2
[31-05-2023 22:38:55] embeddedBottomLines: 4
[31-05-2023 22:38:55] inputFormat: 8
[31-05-2023 22:38:55] height: 2168
[31-05-2023 22:38:55] width: 3848
[31-05-2023 22:38:55] fps: 30.000000
[31-05-2023 22:38:55] Embedded Data: 0
[31-05-2023 22:38:55] CameraMaster available outputs: 1
[31-05-2023 22:38:55] CameraClient: setting pipeline config for camera ID 0
[31-05-2023 22:38:55] CameraMaster: master initiation
MAX96712: Revision 5 detected
MAX96712 Link 0: PHY optimization was enabled
[31-05-2023 22:38:55] CameraMaster: master init failed with status = 10
[31-05-2023 22:38:55] Driveworks exception thrown: DW_UNEXPECTED_EVENT: CameraMaster::bootstrap failed with sipl status 10

terminate called after throwing an instance of ‘std::runtime_error’
what(): [2023-05-31 22:38:55] DW Error DW_UNEXPECTED_EVENT executing DW function:
dwSAL_start(m_sal)
at samples/sensors/camera/camera/main.cpp:363
Aborted

Can you try running the command with ‘sudo’ privileges? Additionally, could you please provide more information about the camera module you are using?

I get still errors.
nvidia1@tegra-ubuntu:/usr/local/driveworks/bin$ sudo ./sample_camera --write-file=/home/nvidia1/output_camera
[sudo] password for nvidia1:
ProgramArguments: Missing argument ‘dwTracePath’ requested
[31-05-2023 22:55:40] Platform: Detected Drive Orin P3710
[31-05-2023 22:55:40] TimeSource: monotonic epoch time offset is 1685572595922502
[31-05-2023 22:55:40] TimeSourceVibranteLinux: detect valid PTP interface mgbe2_0
[31-05-2023 22:55:40] TimeSource Nvpss : PTP ioctl returned error. Synchronized time will not be available from this timesource.
[31-05-2023 22:55:40] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to mgbe2_0
[31-05-2023 22:55:40] PTP Time is available from Eth Driver
[31-05-2023 22:55:40] Adding variable DW_Base:DW_Version
[31-05-2023 22:55:40] Added variable DW_Base:DW_Version
[31-05-2023 22:55:40] Platform: number of GPU devices detected 1
[31-05-2023 22:55:40] Platform: currently selected GPU device 0, Resource Data Dir: trt_08_05_10_03, Arch: ga10b
[31-05-2023 22:55:40] Platform: currently selected GPU device integrated ID 0
[31-05-2023 22:55:40] CUDLAEngine:getDLACount: CUDLA version is = 1003000
[31-05-2023 22:55:40] CUDLAEngine:getDLACount: Number of DLA devices = 2
[31-05-2023 22:55:40] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘./resources’: VirtualFileSystem: Failed to mount ‘./resources/resources.pak’
[31-05-2023 22:55:40] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks-5.10/bin/data’: VirtualFileSystem: Failed to mount ‘/usr/local/driveworks-5.10/bin/data/resources.pak’
[31-05-2023 22:55:40] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-5.10/bin/…/data
[31-05-2023 22:55:40] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks-5.10/bin/…/data’: VirtualFileSystem: Failed to mount ‘/usr/local/driveworks-5.10/bin/…/data/resources.pak’
[31-05-2023 22:55:40] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-5.10/data
[31-05-2023 22:55:40] 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’
[31-05-2023 22:55:40] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.10/bin/…/lib/libdw_base.so.5.10
[31-05-2023 22:55:40] 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
[31-05-2023 22:55:40] SDK: No resources(.pak) mounted, some modules will not function properly
[31-05-2023 22:55:40] SDK: use EGL display as provided
[31-05-2023 22:55:40] TimeSource: monotonic epoch time offset is 1685572595922502
[31-05-2023 22:55:40] TimeSourceVibranteLinux: detect valid PTP interface mgbe2_0
[31-05-2023 22:55:40] TimeSource Nvpss : PTP ioctl returned error. Synchronized time will not be available from this timesource.
[31-05-2023 22:55:40] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to mgbe2_0
[31-05-2023 22:55:40] PTP Time is available from Eth Driver
[31-05-2023 22:55:40] Initialize DriveWorks SDK v5.10.87
[31-05-2023 22:55:40] Release build with GNU 9.3.0 from buildbrain-branch-0-g9a5b4670e12 against Drive PDK v6.0.6.0
[31-05-2023 22:55:40] SensorFactory::createSensor() → time.nvpps, nvpps-device=/dev/nvpps0
[31-05-2023 22:55:40] TimeSensor: failed to set NVPPS parameters. Error: Invalid argument
[31-05-2023 22:55:40] This platform does not support NVPPS GPIO mode. Fallback to timer mode
[31-05-2023 22:55:40] TimeSensor: initialized with no UTC time reference.
[31-05-2023 22:55:40] EndpointNVPPS: started on /dev/nvpps0
[31-05-2023 22:55:40] fromFile: Loading rig file: /usr/local/driveworks-5.10/data/samples/sensors/camera/camera/rig.json
[31-05-2023 22:55:40] rig::DatabaseOverlayer: Failed to open a file ‘/tmp/car_vin’ - file likely does not exist - skipping overlay
[31-05-2023 22:55:40] No valid data file found for camera:sample0 in parameter string: camera-name=F008A120RM0AV2,interface=csi-ab,CPHY-mode=1,link=0,output-format=processed,async-record=1,file-buffer-size=16777216 (using configuration folder /usr/local/driveworks-5.10/data/samples/sensors/camera/camera/)
[31-05-2023 22:55:40] rig::DatabaseOverlayer: Failed to open a file ‘/tmp/car_vin’ - file likely does not exist - skipping overlay
onInitialize: creating camera.gmsl with params: camera-name=F008A120RM0AV2,interface=csi-ab,CPHY-mode=1,link=0,output-format=processed,async-record=1,file-buffer-size=16777216
[31-05-2023 22:55:40] SensorFactory::createSensor() → camera.gmsl, camera-name=F008A120RM0AV2,interface=csi-ab,CPHY-mode=1,link=0,output-format=processed,async-record=1,file-buffer-size=16777216
[31-05-2023 22:55:40] CameraBase: pool size set to 8
[31-05-2023 22:55:40] SensorFactory::createSensor() → camera.gmsl.master,
[31-05-2023 22:55:40] CameraMaster::parseDevBlock Getting device info list.
[31-05-2023 22:55:40] devBlock: 0 Slave = 0 Interface = csi-ab Camera_name = F008A120RM0AV2 Link = 0 GroupInit = 0 RecCfg = 1
[31-05-2023 22:55:40] Camera Match Name: F008A120RM0AV2 Description: Entron F008A120RM0A module - 120-deg FOV, 24-bit capture, MIPI-AR0820, MAX9295 linkIndex: 4294967295 serInfo.Name: MAX9295
[31-05-2023 22:55:40] Client, Setting up information for camera ID 0
[31-05-2023 22:55:40] Client, successfully found info for camera ID 0 bound to id 0
[31-05-2023 22:55:40] ImageStreamer(NvMedia → CUDA)
[31-05-2023 22:55:40] ImageStreamer(NvMedia → CUDA)
[31-05-2023 22:55:40] ImageStreamer(NvMedia → CUDA)
[31-05-2023 22:55:40] ImageStreamer(NvMedia → CUDA)
[31-05-2023 22:55:40] ImageStreamer(NvMedia → CUDA)
[31-05-2023 22:55:40] ImageStreamer(NvMedia → CUDA)
[31-05-2023 22:55:40] ImageStreamer(NvMedia → CUDA)
[31-05-2023 22:55:40] ImageStreamer(NvMedia → CUDA)
[31-05-2023 22:55:40] CameraClient: using NITO found at /usr/share/camera/F008A120RM0AV2.nito
[31-05-2023 22:55:40] SIPLMaster::SIPLMaster: Setting up master camera
[31-05-2023 22:55:40] Platform:
[31-05-2023 22:55:40] Platform Config:
[31-05-2023 22:55:40] Description:
[31-05-2023 22:55:40] Number of device blocks: 1
[31-05-2023 22:55:40] Device Block : 0
[31-05-2023 22:55:40] csiPort: 2
[31-05-2023 22:55:40] i2cDevice: 0
[31-05-2023 22:55:40] Deserializer Name: MAX96712
[31-05-2023 22:55:40] Deserializer Description: Maxim 96712 Aggregator
[31-05-2023 22:55:40] Deserializer i2cAddress: 41
[31-05-2023 22:55:40] Simulator Mode: 0
[31-05-2023 22:55:40] Passive Mode: 0
[31-05-2023 22:55:40] Phy Mode: 1
[31-05-2023 22:55:40] Number of camera modules: 1
[31-05-2023 22:55:40] CameraModule index: 0
[31-05-2023 22:55:40] Name :F008A120RM0AV2
[31-05-2023 22:55:40] Description: Entron F008A120RM0A module - 120-deg FOV, 24-bit capture, MIPI-AR0820, MAX9295
[31-05-2023 22:55:40] Serializer name: MAX9295
[31-05-2023 22:55:40] Serializer description: Maxim 9295 Serializer
[31-05-2023 22:55:40] Serializer i2cAdress: 98
[31-05-2023 22:55:40] EEPROM name: N24C64
[31-05-2023 22:55:40] EEPROM i2cAddress: 84
[31-05-2023 22:55:40] EEPROM description: N24C64 EEPROM
[31-05-2023 22:55:40] Sensor ID: 0
[31-05-2023 22:55:40] Sensor name: AR0820
[31-05-2023 22:55:40] Sensor description: OnSemi AR0820 Sensor
[31-05-2023 22:55:40] Sensor i2cAddress: 16
[31-05-2023 22:55:40] Sensor isTPGEnabled: 0
[31-05-2023 22:55:40] Sensor isTriggerMode: 1
[31-05-2023 22:55:40] cfa: 35
[31-05-2023 22:55:40] embeddedTopLines: 2
[31-05-2023 22:55:40] embeddedBottomLines: 4
[31-05-2023 22:55:40] inputFormat: 8
[31-05-2023 22:55:40] height: 2168
[31-05-2023 22:55:40] width: 3848
[31-05-2023 22:55:40] fps: 30.000000
[31-05-2023 22:55:40] Embedded Data: 0
[31-05-2023 22:55:40] CameraMaster available outputs: 1
[31-05-2023 22:55:40] CameraClient: setting pipeline config for camera ID 0
[31-05-2023 22:55:40] CameraMaster: master initiation
MAX96712: Revision 5 detected
MAX96712 Link 0: PHY optimization was enabled
[31-05-2023 22:55:41] CameraMaster: master init failed with status = 10
[31-05-2023 22:55:41] Driveworks exception thrown: DW_UNEXPECTED_EVENT: CameraMaster::bootstrap failed with sipl status 10

terminate called after throwing an instance of ‘std::runtime_error’
what(): [2023-05-31 22:55:41] DW Error DW_UNEXPECTED_EVENT executing DW function:
dwSAL_start(m_sal)
at samples/sensors/camera/camera/main.cpp:363
Aborted
My cameras are sekonix n2.0 camera

I don’t know this camera module.

Only the following Sekonix camera modules (from https://developer.nvidia.com/drive/ecosystem-orin#camera) are supported for this
devkit but please note that for software support related to both modules, it is necessary to contact Onsemi.

I found out that our camera module is sekonix SF3325. I don’t think the error is connected with the camera. We could ran it on our Nvidia Drive Xavier.I just ran it again. This has to be something with Nvidia.

Please note that Sekonix SF3325 on Xavier is supported by us but it on Orin is supported by Onsemi. Let me know if you need their contact information. Thanks.

Yes please.
Is it the Technical Support Center https://onsemineworg.my.site.com/onsemisupportcenter/s/datacategory or is there a specific internet address?

I sent you a private message with the contact information. Please check. Thanks.

1 Like

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