When I run this command, I see the logs below but only get a black screen. My camera is the IMX678-MIPI-V2.0. I have two cameras, but I want to connect just one first to check the video output. However, I’m having trouble getting the screen to display.
Using winsys: x11
Pipeline is live and does not need PREROLL ...
Got context from element 'eglglessink0': gst.egl.EGLDisplay=context, display=(GstEGLDisplay)NULL;
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: 3840 x 2160 FR = 29.999999 fps Duration = 33333334 ; Analog Gain range min 1.000000, max 22.250000; Exposure Range min 13000, max 683709000;
GST_ARGUS: 1920 x 1080 FR = 59.999999 fps Duration = 16666667 ; Analog Gain range min 1.000000, max 22.250000; Exposure Range min 13000, max 683709000;
GST_ARGUS: Running with following settings:
Camera index = 0
Camera mode = 0
Output Stream W = 3840 H = 2160
seconds to Run = 0
Frame Rate = 29.999999
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:694 NvBufSurfaceFromFd Failed.
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, threadFunction:247 (propagating)
WARNING: from element /GstPipeline:pipeline0/GstEglGlesSink:eglglessink0: Pipeline construction is invalid, please add queues.
Additional debug info:
gstbasesink.c(1209): gst_base_sink_query_latency (): /GstPipeline:pipeline0/GstEglGlesSink:eglglessink0:
Not enough buffering available for the processing deadline of 0:00:00.015000000, add enough queues to buffer 0:00:00.015000000 additional data. Shortening processing latency to 0:00:00.000000000.
Got EOS from element "pipeline0".
Additionally,
cat /etc/nv_tegra_release
# R35 (release), REVISION: 3.1, GCID: 32827747, BOARD: t186ref, EABI: aarch64, DATE: Sun Mar 19 15:19:21 UTC 2023
*** Please note that this reply is generated by LLM automatically ***
Based on the provided context, it appears that you are trying to connect a single IMX678 MIPI camera to a Jetson Orin Nano module and display the video output on a screen. However, you are only getting a black screen.
Here are a few potential issues that might be causing the problem:
Camera configuration: Make sure that the camera is properly configured and recognized by the Jetson Orin Nano module. You can check the camera configuration using the v4l2-ctl command. For example, you can list all available cameras using v4l2-ctl --list-devices.
Device tree configuration: The device tree configuration might not be correct for your camera. The device tree configuration is used to describe the hardware components of your system, including the camera. You can check the device tree configuration using the dtc command. For example, you can dump the device tree configuration using dtc -I fs -O dts /proc/device-tree.
Camera driver: The camera driver might not be loaded or might not be compatible with your camera. You can check the loaded drivers using the lsmod command. For example, you can list all loaded drivers using lsmod | grep video.
Video output: The video output might not be configured correctly. You can check the video output configuration using the xrandr command. For example, you can list all available video outputs using xrandr --query.
To troubleshoot the issue, you can try the following steps:
Check the camera configuration using v4l2-ctl --list-devices.
Check the device tree configuration using dtc -I fs -O dts /proc/device-tree.
Check the loaded drivers using lsmod | grep video.
Check the video output configuration using xrandr --query.
Try to capture a video using the v4l2-ctl command. For example, you can capture a video using v4l2-ctl --stream-mmap --stream-count=1 --stream-to=/dev/video0.
If none of these steps help, you can try to provide more information about your system and camera configuration, such as the kernel version, device tree configuration, and camera driver version.
In comparison to other similar issues, such as the one mentioned in the context (Mem copy error - NVMM - DeepStream), the issue you are facing seems to be related to the camera configuration and video output, rather than a memory copy error. However, it’s always a good idea to check the system logs and kernel messages for any error messages that might be related to the issue you are facing.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Check the loaded drivers using lsmod | grep video.
nothing
Check the video output configuration using xrandr --query.
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 598mm x 337mm 1920x1080 60.00*+ 59.94 50.00 1680x1050 59.95 1600x900 60.00 1440x900 59.89 1280x1024 75.02 60.02 1280x800 59.81 1280x720 60.00 59.94 50.00 1152x864 75.00 1024x768 75.03 70.07 60.00 800x600 75.00 72.19 60.32 56.25 720x576 50.00 720x480 59.94 640x480 75.00 72.81 59.94
Try to capture a video using the v4l2-ctl command. For example, you can capture a video using v4l2-ctl --stream-mmap --stream-count=1 --stream-to=/dev/video0.
VIDIOC_REQBUFS returned -1 (Device or resource busy)