# gst-launch-1.0 nvarguscamerasrc sensor-id=0 num-buffers=1 ! "video/x-raw(memory:NVMM), format=(string)NV12, width=(int)1728, height=(int)1728" ! nvvidconv ! jpegenc ! filesink location=test0.jpg^C
root@iking:/home/iking# gst-launch-1.0 nvarguscamerasrc sensor-id=1 num-buffers=4000 ! "video/x-raw(memory:NVMM), format=(string)NV12, width=(int)960, height=(int)960" ! nvvidconv ! jpegenc ! filesink location=test1.mp4
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
GST_ARGUS: Creating output stream
CONSUMER: Waiting until producer is connected...
GST_ARGUS: Available Sensor modes :
GST_ARGUS: 960 x 960 FR = 120.000005 fps Duration = 8333333 ; Analog Gain range min 1.000000, max 87.471001; Exposure Range min 16000, max 8333000;
GST_ARGUS: 800 x 800 FR = 29.999999 fps Duration = 33333334 ; Analog Gain range min 1.000000, max 87.471001; Exposure Range min 26000, max 33324000;
GST_ARGUS: 1728 x 1728 FR = 36.000000 fps Duration = 27777778 ; Analog Gain range min 1.000000, max 87.471001; Exposure Range min 26000, max 27779000;
GST_ARGUS: Running with following settings:
Camera index = 1
Camera mode = 0
Output Stream W = 960 H = 960
seconds to Run = 0
Frame Rate = 120.000005
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
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, threadExecute:723 NvBufSurfaceFromFd Failed.
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, threadFunction:242 (propagating)
Got EOS from element "pipeline0".
Execution ended after 0:00:04.005884143
Sometimes this error occurs when obtaining images in gst-launch-1.0, especially after pressing Ctrl+C, and it is easy to reproduce when restarting again
SCF: Error InvalidState: Timeout!! Skipping requests on sensor GUID 4, capture sequence ID = 281470681743360 draining session frameStart events 281470681743363
(in src/services/capture/FusaCaptureViCsiHw.cpp, function waitCsiFrameStart(), line 531)
So the sensor does not generate correct frame data, triggering the error. Would suggest check the sensor driver. For further debugging please check developer guide:
We looked at it from the oscilloscope and it seems that there is data on the CSI bus, but/ Argus_yuvjpeg-d 1 cannot be read. This tegra Driver and other tools are provided by Nvidia
The phenomenon is that the image obtained by CSI0 has red stripes. CSI1 cannot obtain images， Can you help confirm what’s wrong with the device tree or others！
rbpcv3_sc432ai_a@36 and rbpcv3_sc432ai_b@36 all set：
lane_polarity = “6”;
Hi,
Would suggest inspect the hardware signal and see if the signal quality is good and stable. Our CSI port is to receive signals from the camera source. From the log, it looks like the signal quality is not good occasionally.
It was normal for a period of time after the system started, but after this error occurred, it continued to be abnormal. I wonder if after clearing this error, it can still run normally
