Sekonix SF3324: Driveworks sample camera failed

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

Hello,

We have a sekonix SF3324 with us and are trying to use the driveworks sample camera with the following command

./sample_camera --rig=/usr/local/driveworks-4.0/data/samples/sensors/camera/camera/rig_test.json

Unfortunately we obtain the following error, and are not able to view the output

nvidia@tegra-ubuntu:/usr/local/driveworks-4.0/bin$ ./sample_camera --rig=/usr/local/driveworks-4.0/data/samples/sensors/camera/camera/rig_test.json
[12-03-2024 19:04:47] Platform: Detected DDPX - Tegra A
[12-03-2024 19:04:47] TimeSource: monotonic epoch time offset is 1710266564972349
[12-03-2024 19:04:47] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to eth0
[12-03-2024 19:04:47] TimeSource Eth: Lost PTP time synchronizaton. Synchronized time will not be available from this timesource.
[12-03-2024 19:04:47] TimeSource: Could not detect valid PTP time source at 'eth0'. Fallback to CLOCK_MONOTONIC.
[12-03-2024 19:04:47] Platform: number of GPU devices detected 1
[12-03-2024 19:04:47] Platform: currently selected GPU device integrated ID 0
[12-03-2024 19:04:47] 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]'
[12-03-2024 19:04:47] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-4.0/data
[12-03-2024 19:04:47] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-4.0/data/': VirtualFileSystem: Failed to mount '/usr/local/driveworks-4.0/data/[.pak]'
[12-03-2024 19:04:47] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-4.0/data
[12-03-2024 19:04:47] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-4.0/data/': VirtualFileSystem: Failed to mount '/usr/local/driveworks-4.0/data/[.pak]'
[12-03-2024 19:04:47] SDK: No resources(.pak) mounted, some modules will not function properly
[12-03-2024 19:04:47] SDK: Create NvMediaDevice
[12-03-2024 19:04:47] SDK: Create NvMedia2D
[12-03-2024 19:04:47] SDK: use EGL display as provided
[12-03-2024 19:04:47] TimeSource: monotonic epoch time offset is 1710266564972350
[12-03-2024 19:04:47] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to eth0
[12-03-2024 19:04:47] TimeSource Eth: Lost PTP time synchronizaton. Synchronized time will not be available from this timesource.
[12-03-2024 19:04:47] TimeSource: Could not detect valid PTP time source at 'eth0'. Fallback to CLOCK_MONOTONIC.
[12-03-2024 19:04:47] Initialize DriveWorks SDK v4.0.0
[12-03-2024 19:04:47] Release build with GNU 7.3.1 from no-gitversion-build against Drive PDK v5.2.6.0
[12-03-2024 19:04:47] Rig::fromFile: Loading rig file: /usr/local/driveworks-4.0/data/samples/sensors/camera/camera/rig_test.json
[12-03-2024 19:04:47] rig::DatabaseOverlayer: Failed to open a file '/tmp/car_vin' - file likely does not exist - skipping overlay
[12-03-2024 19:04:47] No valid data file found for camera:sample0 in parameter string: camera-name=SF3324,interface=csi-a,link=0,output-format=processed (using configuration folder /usr/local/driveworks-4.0/data/samples/sensors/camera/camera/)
[12-03-2024 19:04:47] 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=SF3324,interface=csi-a,link=0,output-format=processed
[12-03-2024 19:04:47] SensorFactory::createSensor() -> camera.gmsl, camera-name=SF3324,interface=csi-a,link=0,output-format=processed
[12-03-2024 19:04:47] CameraBase: pool size set to 8
[12-03-2024 19:04:47] SensorFactory::createSensor() -> camera.gmsl.master, 
[12-03-2024 19:04:47] CameraMaster::parseDevBlock Getting device info list.
[12-03-2024 19:04:47] devBlock: 1 Slave = 0 Interface = csi-a Camera_name = SF3324 Link = 0
[12-03-2024 19:04:47] Camera Match Name: SF3324 Description: Sekonix SF3324 module - 120-deg FOV, DVP AR0231-RCCB, MAX96705 linkIndex: 4294967295 serInfo.Name: MAX96705
[12-03-2024 19:04:47] Client, Setting up information for camera ID 0
[12-03-2024 19:04:47] Client, successfully found info for camera ID 0 bound to id 0
[12-03-2024 19:04:47] CameraClient: no NITO found at /opt/nvidia/nvmedia/nit/SF3324.nito
[12-03-2024 19:04:47] CameraClient: using NITO found at /opt/nvidia/nvmedia/nit/sf3324.nito
[12-03-2024 19:04:47] Initialize DriveWorks VisualizationSDK v4.0.0
[12-03-2024 19:04:47] Initialize DriveWorksGL SDK v4.0.0
onInitialize: Total cameras 1
onInitialize: getting image props 0
onInitialize: initilizing stream: 0
[12-03-2024 19:04:47] StreamConsumerGL: successfully initialized
[12-03-2024 19:04:47] StreamProducerCUDA: successfully initialized
Main: Starting master.
[12-03-2024 19:04:48] CameraGSMLMaster: starting...
[12-03-2024 19:04:48] SIPLMaster::SIPLMaster: Setting up master camera
[12-03-2024 19:04:48] Platform: 
[12-03-2024 19:04:48] Platform Config: 
[12-03-2024 19:04:48] Description: 
[12-03-2024 19:04:48] Number of device blocks: 1
[12-03-2024 19:04:48] Device Block : 0
[12-03-2024 19:04:48] 	csiPort: 0
[12-03-2024 19:04:48] 	i2cDevice: 0
[12-03-2024 19:04:48] 	Deserializer Name: MAX96712
[12-03-2024 19:04:48] 	Deserializer Description: Maxim 96712 Aggregator
[12-03-2024 19:04:48] 	Deserializer i2cAddress: 41
[12-03-2024 19:04:48] 	Simulator Mode: 0
[12-03-2024 19:04:48] 	Slave Mode: 0
[12-03-2024 19:04:48] 	Phy Mode: 0
[12-03-2024 19:04:48] 	Number of camera modules: 1
[12-03-2024 19:04:48] 	CameraModule index: 0
[12-03-2024 19:04:48] 		Name :SF3324
[12-03-2024 19:04:48] 		Description: Sekonix SF3324 module - 120-deg FOV, DVP AR0231-RCCB, MAX96705
[12-03-2024 19:04:48] 		Serializer name: MAX96705
[12-03-2024 19:04:48] 		Serializer description: Maxim 96705 Serializer
[12-03-2024 19:04:48] 		Serializer i2cAdress: 64
[12-03-2024 19:04:48] 			Sensor ID: 0
[12-03-2024 19:04:48] 			Sensor name: AR0231
[12-03-2024 19:04:48] 			Sensor description: OnSemi AR0231 Sensor
[12-03-2024 19:04:48] 			Sensor i2cAddress: 16
[12-03-2024 19:04:48] 			Sensor isTPGEnabled: 0
[12-03-2024 19:04:48] 			Sensor isTriggerMode: 1
[12-03-2024 19:04:48] 				 cfa: 39
[12-03-2024 19:04:48] 				 embeddedTopLines: 24
[12-03-2024 19:04:48] 				 embeddedBottomLines: 4
[12-03-2024 19:04:48] 				 inputFormat: 8
[12-03-2024 19:04:48] 				 height: 1208
[12-03-2024 19:04:48] 				 width: 1920
[12-03-2024 19:04:48] 				 fps: 30.0000000
[12-03-2024 19:04:48] 				 Embedded Data: 0
[12-03-2024 19:04:48] CameraMaster available outputs: 1
[12-03-2024 19:04:48] CameraClient: setting pipeline config for camera ID 0
[12-03-2024 19:04:48] CameraMaster: master initiation
MAX96712: Revision 2 detected
MAX96712: Enable periodic AEQ on Link 0
MAX96705: Pre-emphasis set to 0xaa
MAX96705: Revision 1 detected!
Sensor AR0231 RCCB Rev7 detected!
[12-03-2024 19:04:49] SIPLClient: ImageQueue timeout
[12-03-2024 19:04:49] SIPLNotifier: Event notification queue timeout
Module_id 22 Severity 6 : NvMediaICPCreateEx 76
Module_id 22 Severity 6 : T19x VI version  0x000019
[12-03-2024 19:04:49] CameraClient: allocating RAW surfaces, nvmedia surface 210
[12-03-2024 19:04:49] Registering imagegroups for pipeline 0 NO COOKIES
[12-03-2024 19:04:49] CameraClient: allocating ISP surfaces 36
[12-03-2024 19:04:49] CameraClient: format not specified. Using h264 in Codec Header.
[12-03-2024 19:04:49] CameraMaster: bootstrap complete
Module_id 30 Severity 2 : src/control/common/camrangecheck.cpp 71
Module_id 30 Severity 2 : parameter is out of range
Module_id 30 Severity 2 : src/control/common/camrangecheck.cpp 358
Module_id 30 Severity 2 : Bad input parameter : Channel Gain
Module_id 30 Severity 2 : src/control/auto/SiplControlAuto.cpp 468
Module_id 30 Severity 2 : Bad input parameter currFrameEmbedInfo
SIPL_ICP_ISP_0: /dvs/git/dirty/git-master_linux/camera/fusa/sipl/src/core/pipelineMgr/spmgr/pipeline/blocks/CNvMISPBlock.cpp: 673: ProgramISP: GetNoiseProfile failed. status:1
SIPL_ICP_ISP_0: /dvs/git/dirty/git-master_linux/camera/fusa/sipl/src/core/pipelineMgr/spmgr/pipeline/blocks/CNvMISPBlock.cpp: 613: ProcessISP: ProgramISP failed
SIPL_ICP_ISP_0: /dvs/git/dirty/git-master_linux/camera/fusa/sipl/src/core/pipelineMgr/spmgr/pipeline/CNvMSensorPipeline.cpp: 1088: DoISPProcessing: ISP block process isp failed
[12-03-2024 19:04:49] CameraClient: Notification received from pipeline index:0 of type: NOTIF_ERROR_ISP_PROCESSING_FAILURE
[12-03-2024 19:04:50] SIPLClient: ImageQueue timeout
[12-03-2024 19:04:50] SIPLNotifier: Event notification queue timeout

Could you please help us in this scenario?

Best regards,
Roshan

Is this regarding a physical Sekonix SF3324 camera module? We haven’t received reports of similar issues from other developers using this camera. Additionally, based on your previous posts, it appears that the camera worked on your side.

Hello @VickNV ,

It is a digital twin, previously it was working, now we have an error saying

Bad input parameter : Channel Gain

Could you please let us know, which register address and value we have to change in order to tackle this error?

Best regards,
Roshan

Please refer to the sensorWBInfo document section for the supported values.

Hello @VickNV

I have some trouble recognizing the Register address and the value from the image sensor datasheet,

Could you please share the register address and the corresponding value we have to set for the awb gain?

Would really appreciate it,

Best regards,
Roshan

Could you try the four registers?

 181     {.name = "GREEN1_GAIN", .addr = 0X3056, .data = 0},
 182     {.name = "BLUE_GAIN", .addr = 0X3058, .data = 0},
 183     {.name = "RED_GAIN", .addr = 0X305A, .data = 0},
 184     {.name = "GREEN2_GAIN", .addr = 0X305C, .data = 0},

However, I must remind you that this request falls outside the scope of forum support. Please understand that there may be limitations to how much I can help with specific technical details.

Hello @VickNV

Thanks a lot for your response, really appreciate the help,
We tried to replace the mentioned register addresses and values
But unfortunately, still have the same error

Best regards,
Roshan

Is this still unresolved? I hope you were able to find a solution or retrieve the previously working version.