DRIVE OS Version: 6.0.10
I am currently testing the cameras Smartlead BS2S107A-100-03 (IMX623) and Smartlead BF8S103G-100-00 (IMX728) using the sample_camera application located at /usr/local/driveworks/samples/src/sensors/camera/camera.
There are cases where the sample_camera application fails to launch depending on the combination of camera connections. Specifically, the dwSensor_start function returns an error.
Below are the test results:
- Three IMX728 cameras connected to port A, and four IMX623 cameras connected to port B.
Result: ERROR
- Three IMX728 cameras connected to port A, and one IMX623 camera connected to port B.
Result: SUCCESS
- Three IMX728 cameras connected to port A, and two IMX623 cameras connected to port B.
Result: ERROR
- One IMX728 camera connected to port A, and four IMX623 cameras connected to port B.
Result: SUCCESS
- Two IMX728 cameras connected to port A, and four IMX623 cameras connected to port B.
Result: ERROR
I believe the causes for the failure to launch the sample_camera application may be the following:
- Limitations on the number of connected cameras.
- Total pixel count.
Could you please advise what might be causing the failure to launch the sample_camera application?
Dear @Natsuha_Shishido ,
Firstly for each test case, make sure nvsipl_camera is working as DW camera sample uses NVSIPL APIs.
For each failure test case, set env DW_SIPL_NVMEDIA_VERBOSITY=4 and share its corresponding output in /var/log/syslog and application log. Please clear the syslog after each test to avoid confusion.
Dear @SivaRamaKrishnaNV
I set env DW_SIPL_NVMEDIA_VERBOSITY=4 to obtain the application logs and /var/log/syslog.
The collected logs also include the rig file used at startup.
Test case 4 was previously reported as SUCCESS; however, the logs obtained this time show an ERROR.
4. One IMX728 camera connected to port A, and four IMX623 cameras connected to port B.
Result: ERROR
Additionally, we have added test case 6, and I am sharing the logs related to this case as well.
6. Four IMX728 cameras connected to port A, and three IMX623 cameras connected to port B.
Result: SUCCESS
Log
20260126_dw_sample__test.zip (378.0 KB)
Dear @SivaRamaKrishnaNV
I have an additional report.
Although Test Case 1 was previously reported as an error, it succeeded after changing the order of the rig file.
The order of the “sensor” entries in the rig was changed as follows:
[0] IMX728 → IMX623
[1] IMX728 → IMX623
[2] IMX728 → IMX623
[3] IMX623 → IMX623
[4] IMX623 → IMX728
[5] IMX623 → IMX728
[6] IMX623 → IMX728
With the above combination, Test Case 6 resulted in an error.
I will share the application logs, /var/log/syslog, and rig files for Test Case 1 and Test Case 6.
20260202_dw_sample__test.zip (152.3 KB)
Dear @SivaRamaKrishnaNV
I have provided the logs; may I kindly ask if there are any updates regarding the progress on this matter?
Dear @Natsuha_Shishido ,
Could you remove format=h264, isp-mode=xx from config to see if it helps? Could you refer to /usr/local/driveworks/data/samples/sensors/camera/camera/rig_imx728_imx623_ar0820.json as reference and use relevant parameters based on the link and camera-name. Let me know if you have issue? I am assuming, nvsipl_camera is working for the camera combination configuration you are testing.
Also, May I know what is the use case as you are looking to use cameras in parallel?
Dear @SivaRamaKrishnaNV
I tried deleting the format=h264, isp-mode=xx entries from the rig file, but the result was the same and I still got an error.
The rig file, syslog and terminal log are below.
syslog.txt (68.1 KB)
orin_log.log (1.4 MB)
rig_Orin3.json.txt (8.0 KB)
nvsipl_camera does not allow the combination of multiple camera models.
I want to create software that captures frames from multiple cameras and multiple models and sends them to other machines.
First, I’m considering whether it’s possible to capture frames from multiple cameras and multiple models using the original sample_camera.
Dear @SivaRamaKrishnaNV
While checking the release notes for DRIVE OS 7.0.3 Linux for DRIVE Thor, I found a statement in the fixed issues that said, “SAL did not work with 4x SmartLead IMX623B2 cameras.”
Could this be related?
Is it a known issue with DRIVE OS 6.0.10.0?
I would recommend to focus on Test 1 first.
Yes. different camera models should be connected to different quad port.
Can you check running separate nvsipl_camerainstance for each Quad port. Does that work for you?
Could you check using GMSL params like camera-name=R0SIM728S3RU2120NB2,format=mp4,interface=csi-ab,CPHY-mode=1,link=0,output-format=raw+processed,async-record=1,file-buffer-size=16777216 in rig file for IMX728 camera.
Our QA has tested 4 IMX728 cameras, 2x IMX 728 + 2x IMX623 with with sample_camera and notice no issue.
Could you share the rig file, sample_camera log, syslog with export DW_SIPL_NVMEDIA_VERBOSITY=4 set on terminal. Please clear syslog before running the sample.
Dear @SivaRamaKrishnaNV
Thank you for the information.
I would like to ask questions focusing on the configuration of Group A: 3× IMX728 and Group B: 4× IMX623.
Specifically, I would like to understand the root cause of the error that occurs with the above combination.
Please refer to the zip file “log1_GroupA_IMX728x3_GroupB_IMX623x4__Fail” for the rig file, sample_camera logs, and syslog collected with export DW_SIPL_NVMEDIA_VERBOSITY=4.
https://forums.developer.nvidia.com/t/the-sample-camera-application-fails-to-launch-depending-on-th…
Can you check running separate nvsipl_camerainstance for each Quad port. Does that work for you?
It can be executed successfully. This issue has already been resolved in a different topic
Could you check using GMSL params like~
In the response dated February 2, we indicated that the operation can succeed depending on the order in which the sensors are listed in the rig file. Therefore, we do not think this is caused by parameter settings.
Dear @SivaRamaKrishnaNV
We encountered an error under the following conditions in our environment. Could you please check if the same error occurs in your environment?
camera connections
Three IMX728(Smartlead BF8S103G-100-00) cameras connected to port A, and four IMX623(Smartlead BS2S107A-100-03) cameras connected to port B.
rig index
[0] IMX728
[1] IMX728
[2] IMX728
[3] IMX623
[4] IMX623
[5] IMX623
[6] IMX623
Unfortunately I don’t have these cameras to reproduce. I am not sure how ordering of camera entries can make difference and succeded. 20260126_dw_sample__test folder does not seems to have this case.
Our QA testing is limited to 2x IMX728 + 2x IMX623. He don’t see any issue.
Please try changing the parameters to as earlier suggested to see if helps. Generally initialization failures caused by memory limits with the fifo-size used or frames-pool parameters. Note that, DOS 6.0.10 is the last devzone release for orin and issues on this release are not actively pursued by engineering team.
Dear @SivaRamaKrishnaNV
Thank you for your response. I will try several combinations of the two parameters.
Since the application works correctly depending on the order in which the cameras are listed in the rig file, I will close this thread.