Drivework sample with Camera can't run on Xavier B

dong.liang · November 11, 2019, 3:18am

Hello,

The sample_drivenetNcameras runs properly on Xavier A(the application window shows up the detected object), but when I try to run it on Xavier B, nothing shows up in the application window(blackout) and “Cannot read frame: DW_NOT_READY” message keeps bumping up on the Terminal. Then I push Escape key to quit the application and “(NvCapture) Error Timeout” message shows on the terminal as below.

I wonder if I miss some configuration to run the sample with the camera on Xavier B? Thank you.

nvidia@tegra-ubuntu:/usr/local/driveworks-2.0/bin$ ./sample_drivenetNcameras --input-type=camera
[04-07-2017 07:40:13] Platform: Detected DDPX - Tegra B
[04-07-2017 07:40:13] Initialize DriveWorks SDK v2.0.2081
[04-07-2017 07:40:13] Release build with GNU 4.9.4 from heads/buildbrain-branch-0-g36b127f against Drive PDK v5.1.0.2
[04-07-2017 07:40:13] TimeSource: monotonic epoch time offset is 1499153892206067
[04-07-2017 07:40:13] PTP Time is available from NVPPS Driver
[04-07-2017 07:40:13] Platform: number of GPU devices detected 1
[04-07-2017 07:40:13] Platform: currently selected GPU device integrated ID 0
[04-07-2017 07:40:13] SDK: Resources mounted from .././data/
[04-07-2017 07:40:13] SDK: Create NvMediaDevice
[04-07-2017 07:40:13] SDK: use EGL display as provided
[04-07-2017 07:40:13] SensorFactory::createSensor() -> camera.gmsl, camera-group=a,camera-type=ar0231-rccb-bae-sf3324,serialize=false,output-format=raw,camera-count=4,camera-mask=0001,slave=0,fifo-size=5
[04-07-2017 07:40:13] CameraGMSL: Create NvMediaIPPManager
[04-07-2017 07:40:13] CameraGMSL: required FPS = 30, resolution = 1920x1208
nvmedia isc: IscPwrCtrlInit: 939: Camera power control library: NVCCP
Max96712 Rev 2 detected!
MAX96712: Enable periodic AEQ on Link 0
MAX96705: Pre-emphasis set to 0xaa
Sensor AR0231 RCCB Rev7 detected!
[04-07-2017 07:40:14] CameraGMSL: default IPP event callback function set
Camera image with 1920x1208 at 30 FPS
[04-07-2017 07:40:14] Setting up SoftISP
[04-07-2017 07:40:14] DriveNet: Running in FP32 mode.
[04-07-2017 07:40:14] DriveNet: Running in FP32 mode.
[04-07-2017 07:40:15] FileHeader: file header created with development build (patch = -1), assumingcompatibility
[04-07-2017 07:40:15] FileHeader: file header created with development build (patch = -1), assumingcompatibility
[04-07-2017 07:40:15] Using an engine plan file across different models of devices is not recommended and is likely to affect performance or even cause errors.
[04-07-2017 07:40:15] Glob Size is 28376488 bytes.
[04-07-2017 07:40:15] Added linear block of size 22118400
[04-07-2017 07:40:15] Added linear block of size 7372800
[04-07-2017 07:40:15] Added linear block of size 1036800
[04-07-2017 07:40:15] Added linear block of size 218624
[04-07-2017 07:40:20] Deserialize required 4907073 microseconds.
[04-07-2017 07:40:20] DataConditioner: Scale transformation has been configured with 0.003922.
[04-07-2017 07:40:20] DataConditioner: Split transformation has been enabled.
[04-07-2017 07:40:20] DataConditioner: Value subtract transformation has been configured with {0.00000, 0.00000, 0.00000}.
[04-07-2017 07:40:20] Initialize DriveWorks VisualizationSDK v2.0.2081
[04-07-2017 07:40:20] Initialize DriveWorksGL SDK v2.0.2081
[04-07-2017 07:40:21] StreamConsumerGL: successfully initialized
[04-07-2017 07:40:21] StreamProducerCUDA: successfully initialized
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Cannot read frame: DW_NOT_READY
Timing results:
Thread main:
-onProcess                CPU: 2021305us, std= 806       | GPU: 2021075us, std= 464       | samples=21
-onRender                 CPU:   895us, std=1808       | GPU:   904us, std=1824       | samples=21

(NvCapture) Error Timeout: capture waiting for status timeout (in /dvs/git/dirty/git-master_linux/camera/capture/nvcapture/capture_hw_linux.c, function NvCaptureLinuxGetCaptureStatus(), line 362)
(NvCapture) Error Timeout:  (propagating from /dvs/git/dirty/git-master_linux/camera/capture/nvcapture/capture.c, function NvCaptureDequeue(), line 1050)
(NvCapture) Error Timeout: capture waiting for status timeout (in /dvs/git/dirty/git-master_linux/camera/capture/nvcapture/capture_hw_linux.c, function NvCaptureLinuxGetCaptureStatus(), line 362)
(NvCapture) Error Timeout:  (propagating from /dvs/git/dirty/git-master_linux/camera/capture/nvcapture/capture.c, function NvCaptureDequeue(), line 1050)
(NvCapture) Error Timeout: capture waiting for status timeout (in /dvs/git/dirty/git-master_linux/camera/capture/nvcapture/capture_hw_linux.c, function NvCaptureLinuxGetCaptureStatus(), line 362)
(NvCapture) Error Timeout:  (propagating from /dvs/git/dirty/git-master_linux/camera/capture/nvcapture/capture.c, function NvCaptureDequeue(), line 1050)
(NvCapture) Error Timeout: capture waiting for status timeout (in /dvs/git/dirty/git-master_linux/camera/capture/nvcapture/capture_hw_linux.c, function NvCaptureLinuxGetCaptureStatus(), line 362)
(NvCapture) Error Timeout:  (propagating from /dvs/git/dirty/git-master_linux/camera/capture/nvcapture/capture.c, function NvCaptureDequeue(), line 1050)
(NvCapture) Error Timeout: capture waiting for status timeout (in /dvs/git/dirty/git-master_linux/camera/capture/nvcapture/capture_hw_linux.c, function NvCaptureLinuxGetCaptureStatus(), line 362)
(NvCapture) Error Timeout:  (propagating from /dvs/git/dirty/git-master_linux/camera/capture/nvcapture/capture.c, function NvCaptureDequeue(), line 1050)
^[(NvCapture) Error Timeout: capture waiting for status timeout (in /dvs/git/dirty/git-master_linux/camera/capture/nvcapture/capture_hw_linux.c, function NvCaptureLinuxGetCaptureStatus(), line 362)
(NvCapture) Error Timeout:  (propagating from /dvs/git/dirty/git-master_linux/camera/capture/nvcapture/capture.c, function NvCaptureDequeue(), line 1050)
(NvCapture) Error Timeout: capture waiting for status timeout (in /dvs/git/dirty/git-master_linux/camera/capture/nvcapture/capture_hw_linux.c, function NvCaptureLinuxGetCaptureStatus(), line 362)
(NvCapture) Error Timeout:  (propagating from /dvs/git/dirty/git-master_linux/camera/capture/nvcapture/capture.c, function NvCaptureDequeue(), line 1050)
[04-07-2017 07:41:05] Driveworks VisualizationSDK released
[04-07-2017 07:41:05] SDK: Release NvMediaDevice
[04-07-2017 07:41:05] DriveworksGL SDK released
[04-07-2017 07:41:05] Driveworks SDK released
[04-07-2017 07:41:05] SDK: Release NvMedia2D

SivaRamaKrishnaNV · November 11, 2019, 10:14am

Dear dong.liang,
Are you trying to run on Xavier B at the same time?

dong.liang · November 11, 2019, 3:35pm

Thank you.

No, I just want to run it on Xavier B only.

SivaRamaKrishnaNV · November 11, 2019, 6:29pm

Dear dong.liang,
Can you add --slave=1 parameter to the arguments and check running?

SteveNV · November 12, 2019, 4:51am

Dear dong.liang,

If you have two camera and run the sample on XavierB, please refer to the following command. Thanks.
./sample_drivenetNcamera --input-type=camera --camera-type=ar0231-rccb-bae-sf3324 --selector-mask=0011

SivaRamaKrishnaNV · November 18, 2019, 8:51am

Dear dong.ling,
Did you check the suggested solutions. Could you share any update?

dong.liang · November 19, 2019, 11:32am

Thank you and sorry for my late reply.

It turns out to be the problem of Xavier A.
Sometimes when powering on the Drive AGX, Xavier B boots up while Xavier A fails to boot.
In that situation, Xavier B can’t run the camera demo properly, no matter with/without the --slave=1.

But if Xavier A&B boots up normally, camera demo can run properly on Xavier B using ./sample_drivenetNcameras --input-type=camera.

SivaRamaKrishnaNV · November 26, 2019, 6:15am

Dear dong.liang,
Could you upgrade to latest SDK and check the issue. DRIVE Software 10.0 is now available to download at https://developer.nvidia.com/drive/downloads

Topic		Replies	Views
About camera sample playback errors DRIVE AGX Xavier General	9	854	October 12, 2021
NVIDIA Driveworks Sample Error DRIVE AGX Xavier General driveworks	1	710	March 14, 2022
Getting error while executing Driveworks samples DRIVE AGX Xavier General driveworks-dnn-framework	6	858	May 1, 2023
Camera initiation returns error: nvccp_set_cam_unit_pwr_on failed status 1001 DRIVE AGX Xavier General driveworks-cameras	18	1210	January 6, 2023
Sample_camera, pipeline issue DRIVE AGX Xavier General driveos-nvmedia	3	759	January 13, 2022
Camera issues DRIVE AGX Xavier General driveos-nvmedia , driveworks-cameras	24	1658	October 12, 2021
Drive_works sample_camera giving error DriveWorks camera	1	662	October 4, 2023
Driveworks-4.0: Object Detector tracker sample not working DRIVE AGX Xavier General camera , driveworks , driveworks-cameras	20	876	September 12, 2023
Failed to set pipeline configuration DRIVE AGX Xavier General driveworks-cameras	7	1310	January 11, 2023
./sample_cameraserver_client running failed. Error is as follows: Driveworks exception thrown: DW_FAILURE: Camera getImage: failed for DW_CA DRIVE AGX Orin General driveworks-cameras	10	960	September 12, 2022

Drivework sample with Camera can't run on Xavier B

Related topics