Camera stopped working nvarguscamerasrc0: CANCELLED

Autonomous Machines Jetson & Embedded Systems Jetson Nano
1

Hi,

After successfully using my Nvidia Jetson Nano Development kit (jetpack 4.6.2) with an IMX477 camera, suddenly the camera has stopped working.
Every gstreamer command I run is resulting in the following error:

GST_ARGUS: Starting repeat capture requests.
CONSUMER: Producer has connected; continuing.
nvbuf_utils: dmabuf_fd -1 mapped entry NOT found
nvbuf_utils: Can not get HW buffer from FD… Exiting…
CONSUMER: ERROR OCCURRED
ERROR: from element /GstPipeline:pipeline0/GstNvArgusCameraSrc:nvarguscamerasrc0: CANCELLED
Additional debug info:
Argus Error Status
EOS on shutdown enabled – waiting for EOS after Error
Waiting for EOS…

One of the commands which used to work but now doesn’t:

GST_DEBUG=4 gst-launch-1.0 nvarguscamerasrc ! 'video/x-raw(memory:NVMM), width=4032, height=3040, framerate=29/1, format=NV12' ! nvvidconv  !  nvv4l2h264enc bitrate=10000000 ! h264parse ! qtmux ! filesink location=test.mp4 -e

See full log in log.txt

log.txt (43.5 KB)

Also after running the command I could not interact with nvarguscamerasrc again, seems like:
VIDIOC_S_FMT: failed: Device or resource busy
VIDIOC_REQBUFS: failed: Device or resource busy

Does anyone have any idea what could have happend and how to fix it?

I have already tried reinstalling the camera drivers, without any result…

I also discovered that my boot logs show the following error:

apr 26 09:54:58 kernel: imx477 7-001a: imx477_board_setup: error during i2c read probe (-121)
apr 26 09:54:58 kernel: imx477 7-001a: board setup failed

Thanks in advance!

Quinten

3

hello quintene,

did you meant the camera functionality works normally in the beginning?
may I know what’s your test procedure, or, what’s the changes you’ve done.

according to above,
it looks the camera resources has occupied.
do you have other process that running the camera use-case?

4

Hi Jerry,

Fitst of all thanks for your help!
Yes the camera functionality did work normally at the beginning.

Nothing has changed, I run the gstreamer command every day to capture a video but now it did give me these errors.

About the Device or resource busy error this happens after the crash in my gstreamer command. Therefore I have to reboot every time I want to test te camera now. I thought maybe it could provide some insights in the cause of the problem.

I have no other process that running the camera use-case.
Thanks again!
Qiunten

5

hello quintene,

could you please try restart the Argus daemon service, and running gst pipeline again for testing.
for example,
$ sudo pkill nvargus-daemon
$ sudo systemctl start nvargus-daemon

6

After restarting the nvargus-daemo I could run gstreamer again but it still tells me the camera crashes:

GST_ARGUS: Setup Complete, Starting captures for 0 seconds
GST_ARGUS: Starting repeat capture requests.
CONSUMER: Producer has connected; continuing.
nvbuf_utils: dmabuf_fd -1 mapped entry NOT found
nvbuf_utils: Can not get HW buffer from FD… Exiting…
CONSUMER: ERROR OCCURRED
ERROR: from element /GstPipeline:pipeline0/GstNvArgusCameraSrc:nvarguscamerasrc0: CANCELLED

I also discovered that my boot logs show the following error:

apr 26 09:54:58 kernel: imx477 7-001a: imx477_board_setup: error during i2c read probe (-121)
apr 26 09:54:58 kernel: imx477 7-001a: board setup failed

7

I also logged the nvargus-daemon seems like it can’t find the camera but when I run ls /dev/video0
it shows “/dev/video0” so it seems like its connected but not correctly?

Since I did no changes to the working setup I have ordered a new camera ribbon cable maybe it got damaged hopefully it will work again with a new cable.

=== NVIDIA Libargus Camera Service (0.98.3)=== Listening for connections…=== gst-launch-1.0[9664]: Connection established (7FA37591D0)OFParserListModules: module list: /proc/device-tree/tegra-camera-platform/modules/module0
OFParserListModules: module list: /proc/device-tree/tegra-camera-platform/modules/module1
OFParserGetVirtualDevice: NVIDIA Camera virtual enumerator not found in proc device-tree
---- imager: No override file found. ----
(NvCamV4l2) Error ModuleNotPresent: V4L2Device not available (in /dvs/git/dirty/git-master_linux/camera/utils/nvcamv4l2/v4l2_device.cpp, function findDevice(), line 256)
(NvCamV4l2) Error ModuleNotPresent: (propagating from /dvs/git/dirty/git-master_linux/camera/utils/nvcamv4l2/v4l2_device.cpp, function initialize(), line 60)
(NvOdmDevice) Error ModuleNotPresent: (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorViCsi.cpp, function initialize(), line 107)
NvPclDriverInitializeData: Unable to initialize driver v4l2_sensor
NvPclInitializeDrivers: error: Failed to init camera sub module v4l2_sensor
NvPclStartPlatformDrivers: Failed to start module drivers
NvPclStateControllerOpen: Failed ImagerGUID 1. (error 0xA000E)
NvPclOpen: PCL Open Failed. Error: 0xf
SCF: Error BadParameter: Sensor could not be opened. (in src/services/capture/CaptureServiceDeviceSensor.cpp, function getSourceFromGuid(), line 593)
SCF: Error BadParameter: (propagating from src/services/capture/CaptureService.cpp, function addSourceByGuid(), line 437)
SCF: Error BadParameter: (propagating from src/api/CameraDriver.cpp, function addSourceByIndex(), line 305)
SCF: Error BadParameter: (propagating from src/api/CameraDriver.cpp, function getSource(), line 471)
Acquiring SCF Camera device source via index 0 has failed. ---- imager: No override file found. ----
=== gst-launch-1.0[9664]: CameraProvider initialized (0x7f9c91f1e0)SCF: Error Timeout: ISP Stats timed out! (in src/services/capture/NvIspHw.cpp, function waitIspStatsFinished(), line 608)
Error: waitIspStatsFinished Something went wrong with waiting on stats
Error: waitIspStatsFinished Something went wrong with waiting on stats
SCF: Error Timeout: ISP port 0 timed out! (in src/services/capture/NvIspHw.cpp, function waitIspFrameEnd(), line 492)
SCF: Error InvalidState: Something went wrong with waiting on Isp frame end (in src/services/capture/NvIspHw.cpp, function waitIspFrameEnd(), line 550)
SCF: Error InvalidState: (propagating from src/common/Utils.cpp, function workerThread(), line 116)
SCF: Error InvalidState: Worker thread IspHw frameComplete failed (in src/common/Utils.cpp, function workerThread(), line 133)
Error: waitCsiFrameStart timeout guid 0
**VI/CSI Debug Registers
VI_CFG_INTERRUPT_MASK_0 = 0x00000000
VI_CFG_INTERRUPT_STATUS_0 = 0x00000000
VI_CSI_0_ERROR_STATUS_0 = 0x00000000
VI_CSI_0_ERROR_INT_MASK_0 = 0x00000000
VI_CSI_1_ERROR_STATUS_0 = 0x00000000
VI_CSI_1_ERROR_INT_MASK_0 = 0x00000000
CSI_CSI_PIXEL_PARSER_A_INTERRUPT_MASK_0 = 0x00000000
CSI_CSI_PIXEL_PARSER_A_STATUS_0 = 0x00000000
CSI_CSI_PIXEL_PARSER_B_INTERRUPT_MASK_0 = 0x00000000
CSI_CSI_PIXEL_PARSER_B_STATUS_0 = 0x00000000
CSI_CSI_CIL_A_INTERRUPT_MASK_0 = 0x00000000
CSI_CSI_CIL_A_STATUS_0 = 0x00000000
CSI_CSI_CILA_STATUS_0 = 0x00000000
CSI_CSI_CIL_B_INTERRUPT_MASK_0 = 0x00000000
CSI_CSI_CIL_B_STATUS_0 = 0x00000000
CSI_CSI_CILB_STATUS_0 = 0x00000000
CSI_CSI_READONLY_STATUS_0 = 0x00000000
CSI_DEBUG_CONTROL_0 = 0x63060700
CSI_DEBUG_COUNTER_0_0 = 0x00000000
CSI_DEBUG_COUNTER_1_0 = 0x00000000
CSI_DEBUG_COUNTER_2_0 = 0x00000000

SCF: Error Timeout: (propagating from src/common/Utils.cpp, function workerThread(), line 116)
SCF: Error Timeout: Worker thread ViCsiHw frameStart failed (in src/common/Utils.cpp, function workerThread(), line 133)
SCF: Error Timeout: (propagating from src/services/capture/CaptureServiceDeviceIsp.cpp, function waitCompletion(), line 423)
SCF: Error Timeout: (propagating from src/services/capture/CaptureServiceDevice.cpp, function pause(), line 951)
SCF: Error Timeout: During capture abort, syncpoint wait timeout waiting for current frame to finish (in src/services/capture/CaptureServiceDevice.cpp, function handleCancelSourceRequests(), line 1034)
PowerServiceCore:handleRequests: timePassed = 2972
SCF: Error Timeout: (propagating from src/services/capture/CaptureServiceEvent.cpp, function wait(), line 59)
Error: Camera HwEvents wait, this may indicate a hardware timeout occured,abort current/incoming cc

8

hello quintene,

may I know the details of camera module, is this a rbpcv3-imx477?

9

Hi @JerryChang,

The camera module is an arducam UC-698 Rev.B
Does this help?

10

hello quintenvaneys,

this is not the camera module we default supported. it’s more like a hardware issue for intermittent failure.

11

Hi @JerryChang,

It seemed that a new ribbon did fix the issue.
Thanks for the assistance on the matter!

13

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