Jetson Xavier nx cannot open csi-camera

I am trying connect imx219-77 camera to jetson xavier nx. I type nvgstcapture-1.0 but there are some errors below:

Using winsys: x11
** Message: 21:27:03.659: <main:4651> iterating capture loop ....
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, execute:751 No cameras available
NvMMLiteOpen : Block : BlockType = 4
===== NVMEDIA: NVENC =====
NvMMLiteBlockCreate : Block : BlockType = 4

And v4l2-ctl --list-devices shows the following result:

NVIDIA Tegra Video Input Device (platform:tegra-camrtc-ca):

vi-output, imx219 9-0010 (platform:tegra-capture-vi:0):

vi-output, imx219 10-0010 (platform:tegra-capture-vi:2):


Just to discard other issues, are you able to capture with v4l2-ctl?, for example, something like

v4l2-ctl -d /dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat=RG10 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=100


  • Can you please share you the .dsti where you are currently defining the entries for your IMX219 camera?
  • Also make sure that the modules path in /lib/modules matches the kernel image name, i.e, the output of the command uname -a

Jafet Chaves,
Embedded SW Engineer at RidgeRun
Contact us:
Developers wiki:

I try to capture with v4l2-ctl as your example, and it shows the following message:

$ v4l2-ctl -d /dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat=RG10 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=100
VIDIOC_STREAMON returned -1 (Input/output error)

And the module looks the same as the kernal image:

$ ls /lib/modules/
$ uname -a
Linux xavier 5.10.104-tegra #1 SMP PREEMPT Wed Aug 10 20:17:07 PDT 2022 aarch64 aarch64 aarch64 GNU/Linux

But I cannot find the .dtsi file you say by this command:

$ sudo find / -type f -name *.dtsi
find: ‘/run/user/1000/doc’: Permission denied
find: ‘/run/user/1000/gvfs’: Permission denied
find: ‘/proc/6358’: No such file or directory

Thanks for your response.

When you run the v4l2-ctl command what is the output of dmesg also the output of the V4L2 trace log

  1. To enable the V4L2 trace log
echo 1 > /sys/kernel/debug/tracing/tracing_on
echo 30720 > /sys/kernel/debug/tracing/buffer_size_kb
echo 1 > /sys/kernel/debug/tracing/events/tegra_rtcpu/enable
echo 1 > /sys/kernel/debug/tracing/events/freertos/enable
echo 2 > /sys/kernel/debug/camrtc/log-level
echo > /sys/kernel/debug/tracing/trace
  1. In a separate terminal run your v4l2-ctl command
  2. Check the output log with:
sudo cat /sys/kernel/debug/tracing/trace

One neat trick to decompile the complete running device is to do to the command below, then you could attach the text file here.

dtc -I fs -O dts /proc/device-tree > device_tree.txt

Also are you using a standard sdkamanager installation image or some other custom build?


Is this problem sloved?

I also have same problem.

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