Critical issue with the Argus driver

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
1

We’re encountering a critical issue with the Argus driver on our platform, which is based on Orin AGXI and Orin NX.

While V4L operates without any errors, attempting to use the Argus service results in failed camera access.

Setup Details:

  • Platform: Orin AGXI / Orin NX

  • Interface: FPD-Link III

  • JetPack Version: 6.2 (latest)

Issue:
Running the following command:

gst-launch-1.0 nvarguscamerasrc ! fakesink

Produces these errors:

nvbuf_utils: dmabuf_fd -1 mapped entry NOT found
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, threadExecute:734 NvBufSurfaceFromFd Failed.
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, threadFunction:245 (propagating)

We found a post describing the same issue, but it doesn’t include a resolution:

3
  1. Dump the device tree to confirm the port-index and tegra_sinterface
  2. Make the CID function to dummy to verify the v4l2-ctl then argus.
4

We take logs of vi/cs
while v4l2 operation, i.e. v4l2-ctl --stream-mmap
and while argus operation, i.e. gst-launch nvarguscamerasrc ! fakesink

on both operations, the correct sensor is opened and frames are received.
But, on the argus path, CHANSEL_NOMATCH error is marked.
What could be the reason for this?
is CHANSEL_NOMATCH related to the vc-id fields on both sensor and capture_vi_base ports?
but these field are common to both paths (v4l2/argus).

Thanks
v4l2_op_ok.txt (408.4 KB)
argus_op_nok.txt (110.6 KB)

6

Both v4l2-ctl and argus show the CHANSEL_NOMATCH
It could be the incorrect virtual channel ID cause that.

Thanks

8

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