./sample_cameraserver_client running failed. Error is as follows: Driveworks exception thrown: DW_FAILURE: Camera getImage: failed for DW_CA

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
1

image
image1189×446 126 KB

2

image
image1010×159 17.3 KB

3

Dear @chenhui.song,
Please confirm if the platform is DRIVE AGX ORIN or DRIVE AGX Xavier? Also please share the command and camera module used.

4

platform is DRIVE AGX ORIN ,service :./camera_server --params=camera-name=YH_AR0233_HFOV195_SVS_FRONT,interface=csi-ab,fifo-size=4,output-format=processed

client:./sc_sample_cameraserver_client (Use the default parameters.)

5

camera_server runing Successfully,
nvidia@tegra-ubuntu:/usr/local/driveworks/tools/sensors$ ./camera_server --params=camera-name=YH_AR0233_HFOV195_SVS_FRONT,interface=csi-ab,fifo-size=4,output-format=processed
[10-09-2022 00:21:20] Platform: Detected Drive Orin P3710
[10-09-2022 00:21:20] TimeSource: monotonic epoch time offset is 1662685741156531
[10-09-2022 00:21:20] Platform: Detected Drive Orin P3710
[10-09-2022 00:21:20] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to mgbe2_0
[10-09-2022 00:21:20] PTP Time is available from Eth Driver
[10-09-2022 00:21:20] Adding variable DW_Base:DW_Version
[10-09-2022 00:21:20] Addded variable DW_Base:DW_Version
[10-09-2022 00:21:20] Platform: number of GPU devices detected 1
[10-09-2022 00:21:20] Platform: currently selected GPU device Name: Orin, Resource Data Dir: trt_08_04_10_04, Arch: ga10b
[10-09-2022 00:21:20] Platform: currently selected GPU device integrated ID 0
[10-09-2022 00:21:20] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘./resources’: VirtualFileSystem: Failed to mount ‘./resources/resources.pak’
[10-09-2022 00:21:20] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks-5.4/tools/sensors/data’: VirtualFileSystem: Failed to mount ‘/usr/local/driveworks-5.4/tools/sensors/data/resources.pak’
[10-09-2022 00:21:20] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-5.4/tools/sensors/…/…/data
[10-09-2022 00:21:20] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks-5.4/tools/sensors/…/…/data’: VirtualFileSystem: Failed to mount ‘/usr/local/driveworks-5.4/tools/sensors/…/…/data/resources.pak’
[10-09-2022 00:21:20] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-5.4/data
[10-09-2022 00:21:20] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks-5.4/data’: VirtualFileSystem: Failed to mount ‘/usr/local/driveworks-5.4/data/resources.pak’
[10-09-2022 00:21:20] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.4/tools/sensors/…/…/targets/aarch64-Linux/lib/libdw_base.so.5.4
[10-09-2022 00:21:20] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.4/targets/aarch64-Linux/lib/libdw_base.so.5.4
[10-09-2022 00:21:20] SDK: No resources(.pak) mounted, some modules will not function properly
[10-09-2022 00:21:20] SDK: Create NvMediaDevice
[10-09-2022 00:21:20] SDK: Create NvMedia2D
[10-09-2022 00:21:20] egl::Display: found 1 EGL devices
[10-09-2022 00:21:20] egl::Display: use drm device: drm-nvdc
[10-09-2022 00:21:20] TimeSource: monotonic epoch time offset is 1662685741156531
[10-09-2022 00:21:20] Platform: Detected Drive Orin P3710
[10-09-2022 00:21:20] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to mgbe2_0
[10-09-2022 00:21:20] PTP Time is available from Eth Driver
[10-09-2022 00:21:20] Initialize DriveWorks SDK v5.4.5418
[10-09-2022 00:21:20] Release build with GNU 9.3.0 from buildbrain-branch-0-gbd2ae934941 against Drive PDK v6.0.3.0
[10-09-2022 00:21:20] SensorFactory::createSensor() → camera.gmsl, camera-name=YH_AR0233_HFOV195_SVS_FRONT,interface=csi-ab,fifo-size=4,output-format=processed,link=0
[10-09-2022 00:21:20] CameraBase: pool size set to 8
[10-09-2022 00:21:20] SensorFactory::createSensor() → camera.gmsl.master,
[10-09-2022 00:21:21] CameraMaster::parseDevBlock Getting device info list.
[10-09-2022 00:21:21] devBlock: 0 Slave = 0 Interface = csi-ab Camera_name = YH_AR0233_HFOV195_SVS_FRONT Link = 0
[10-09-2022 00:21:21] Camera Match Name: YH_AR0233_HFOV195_SVS_FRONT Description: OnSemi AR0233 GRBG module - 195-deg FOV, MIPI-AR0233, MAX9295 linkIndex: 4294967295 serInfo.Name: MAX9295
[10-09-2022 00:21:21] Client, Setting up information for camera ID 0
[10-09-2022 00:21:21] Client, successfully found info for camera ID 0 bound to id 0
[10-09-2022 00:21:21] ImageStreamer(NvMedia → CUDA)
[10-09-2022 00:21:21] ImageStreamer(NvMedia → CUDA)
[10-09-2022 00:21:21] ImageStreamer(NvMedia → CUDA)
[10-09-2022 00:21:21] ImageStreamer(NvMedia → CUDA)
[10-09-2022 00:21:21] ImageStreamer(NvMedia → CUDA)
[10-09-2022 00:21:21] ImageStreamer(NvMedia → CUDA)
[10-09-2022 00:21:21] ImageStreamer(NvMedia → CUDA)
[10-09-2022 00:21:21] ImageStreamer(NvMedia → CUDA)
[10-09-2022 00:21:21] CameraClient: using NITO found at /opt/nvidia/nvmedia/nit/YH_AR0233_HFOV195_SVS_FRONT.nito
[10-09-2022 00:21:21] SIPLMaster::SIPLMaster: Setting up master camera
[10-09-2022 00:21:21] Platform:
[10-09-2022 00:21:21] Platform Config:
[10-09-2022 00:21:21] Description:
[10-09-2022 00:21:21] Number of device blocks: 1
[10-09-2022 00:21:21] Device Block : 0
[10-09-2022 00:21:21] csiPort: 2
[10-09-2022 00:21:21] i2cDevice: 0
[10-09-2022 00:21:21] Deserializer Name: MAX96712
[10-09-2022 00:21:21] Deserializer Description: Maxim 96712 Aggregator
[10-09-2022 00:21:21] Deserializer i2cAddress: 41
[10-09-2022 00:21:21] Simulator Mode: 0
[10-09-2022 00:21:21] Passive Mode: 0
[10-09-2022 00:21:21] Phy Mode: 0
[10-09-2022 00:21:21] Number of camera modules: 1
[10-09-2022 00:21:21] CameraModule index: 0
[10-09-2022 00:21:21] Name :YH_AR0233_HFOV195_SVS_FRONT
[10-09-2022 00:21:21] Description: OnSemi AR0233 GRBG module - 195-deg FOV, MIPI-AR0233, MAX9295
[10-09-2022 00:21:21] Serializer name: MAX9295
[10-09-2022 00:21:21] Serializer description: Maxim 9295 Serializer
[10-09-2022 00:21:21] Serializer i2cAdress: 64
[10-09-2022 00:21:21] EEPROM name: NV24C32
[10-09-2022 00:21:21] EEPROM i2cAddress: 80
[10-09-2022 00:21:21] EEPROM description: NV24C32 EEPROM
[10-09-2022 00:21:21] Sensor ID: 0
[10-09-2022 00:21:21] Sensor name: AR0233
[10-09-2022 00:21:21] Sensor description: OnSemi AR0233 Sensor
[10-09-2022 00:21:21] Sensor i2cAddress: 16
[10-09-2022 00:21:21] Sensor isTPGEnabled: 0
[10-09-2022 00:21:21] Sensor isTriggerMode: 1
[10-09-2022 00:21:21] cfa: 35
[10-09-2022 00:21:21] embeddedTopLines: 12
[10-09-2022 00:21:21] embeddedBottomLines: 0
[10-09-2022 00:21:21] inputFormat: 8
[10-09-2022 00:21:21] height: 1280
[10-09-2022 00:21:21] width: 1920
[10-09-2022 00:21:21] fps: 30.000000
[10-09-2022 00:21:21] Embedded Data: 1
[10-09-2022 00:21:21] CameraMaster available outputs: 1
[10-09-2022 00:21:21] CameraClient: setting pipeline config for camera ID 0
[10-09-2022 00:21:21] CameraMaster: master initiation

DriverVersion:603_Dev20220818_nitogroup

MAX96712: Revision 5 detected
MAX9295: Revision 8 detected!
Sensor AR0233 Rev 202E detected!
[10-09-2022 00:21:21] CameraMaster: Bootstrap NvSIPL and ClientPipelines complete
[10-09-2022 00:21:21] CameraMaster: bootstrap complete
[10-09-2022 00:21:21] CameraMaster: starting…
[10-09-2022 00:21:21] CameraClient: allocating image pool for ICP
[10-09-2022 00:21:21] Allocating NvSci group
[10-09-2022 00:21:21] Registering imagegroups for pipeline 0 NO COOKIES
[10-09-2022 00:21:21] CameraClient: allocating image pool
[10-09-2022 00:21:21] Allocating NvSci isp images
[10-09-2022 00:21:21] CameraClient: format not specified. Using h264 in Codec Header.

EnableReplication: handle 30000cf0 enable 1

EnableReplication: passiveEnabled 0 port 1 mipiOutMode 2
[10-09-2022 00:21:21] SIPLClient: Acquisition started
CameraSever: Successfully initialized camera with resolution of 1920x1280 at framerate of 30.000000 FPS
CameraServer: ready for incoming connection
[10-09-2022 00:21:21] SocketServer: listening on 49252
[10-09-2022 00:21:22] SIPLDeviceBlockNotificationHandler: Queue timeout
[10-09-2022 00:21:23] SIPLDeviceBlockNotificationHandler: Queue timeout
[10-09-2022 00:21:24] SIPLDeviceBlockNotificationHandler: Queue timeout
[10-09-2022 00:21:24] Socket accept returned error DW_TIME_OUT(20) for server 281471151508320
[10-09-2022 00:21:25] SIPLDeviceBlockNotificationHandler: Queue timeout
[10-09-2022 00:21:26] SIPLDeviceBlockNotificationHandler: Queue timeout
[10-09-2022 00:21:27] SIPLDeviceBlockNotificationHandler: Queue timeout
[10-09-2022 00:21:27] Socket accept returned error DW_TIME_OUT(20) for server 281471151508320
[10-09-2022 00:21:28] SIPLDeviceBlockNotificationHandler: Queue timeout
[10-09-2022 00:21:29] SIPLDeviceBlockNotificationHandler: Queue timeout
[10-09-2022 00:21:30] SIPLDeviceBlockNotificationHandler: Queue timeout
[10-09-2022 00:21:30] Socket accept returned error DW_TIME_OUT(20) for server 281471151508320
[10-09-2022 00:21:31] SIPLDeviceBlockNotificationHandler: Queue timeout
[10-09-2022 00:21:32] SIPLDeviceBlockNotificationHandler: Queue timeout
[10-09-2022 00:21:33] SIPLDeviceBlockNotificationHandler: Queue timeout
[10-09-2022 00:21:33] Socket accept returned error DW_TIME_OUT(20) for server 281471151508320

6

camera_server running Successfully.

image
image1736×819 170 KB

7

image
image1115×887 205 KB

8

./sample_cameraserver_client running failed,

image
image1554×766 146 KB

9

image
image1578×857 113 KB

10

Hi @chenhui.song
DriveWorks 5.4 is not a developer site release (listed in the page) and is out of the forum support scope. Please go through another support channel for it. If you don’t know, please contact your nvidia representative. Thanks.

11

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