Erroneous pipeline: no element "nvarguscamerasrc"

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
,
1

I have tried absolutely everything. When I first flashed the OS, it worked fine, then a few days later I get this error. I tried everything to fix it and followed a few threads here but I had no luck.

I just want to see the feed from my camera so i run these commands:

sensor_id=0 # 0 for CAM0 and 1 for CAM1 ports 
Framerate=30 
gst-launch-1.0 nvarguscamerasrc sensor_id=$sensor_id ! "video/x-raw(memory:NVMM),width=1920,height=1080,framerate=$Framerate/1,format=NV12" ! nvvidconv flip-method=0 ! "video/x-raw,width=960,height=720" ! nvvidconv ! nvegltransform ! nveglglessink -e

I get this error: WARNING: erroneous pipeline: no element “nvarguscamerasrc”

2

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, it appears that you are experiencing issues with the nvarguscamerasrc element on your Jetson Orin Nano device. The error message “WARNING: erroneous pipeline: no element nvarguscamerasrc” suggests that the nvarguscamerasrc element is not available or not properly configured.

To troubleshoot this issue, let’s compare your situation with similar issues reported by other users.

  1. Similar issues:
    • “Nvarguscamerasrc not working (URGENT)” ( Jetson Orin Nano camera ) - This thread discusses a similar issue with nvarguscamerasrc not working on Jetson Orin Nano. The solution involves checking the device tree and ensuring that the camera sensor is properly configured.
    • “Gst-nvarguscamera fails on Jetpack 6.0” ( Jetson Orin NX camera ) - This thread reports a similar issue with gst-nvarguscamera failing on Jetpack 6.0. The solution involves updating the device tree and ensuring that the camera sensor is properly configured.
  2. Device tree configuration:
    • The device tree configuration is crucial for camera functionality on Jetson devices. Ensure that your device tree is properly configured for your camera sensor. You can refer to the “DeviceTree.txt” file provided in the “Capturing Image from custom sensor fails with 4-csi lanes” thread for an example of a properly configured device tree.
  3. Camera sensor configuration:
    • Ensure that your camera sensor is properly configured and connected to the Jetson Orin Nano device. You can refer to the “IMX219 not detected on JetPack 6 (Error -121)” thread for troubleshooting steps specific to the IMX219 camera sensor.
  4. Jetpack version:
    • Ensure that you are running the latest Jetpack version (6.2) on your Jetson Orin Nano device. You can refer to the “Jetpack 6.2” release notes for information on camera-related fixes and improvements.

To resolve the issue, you can try the following steps:

  1. Verify that your device tree is properly configured for your camera sensor.
  2. Ensure that your camera sensor is properly connected and configured.
  3. Update to the latest Jetpack version (6.2) if you haven’t already.
  4. Refer to the “Nvarguscamerasrc not working (URGENT)” and “Gst-nvarguscamera fails on Jetpack 6.0” threads for additional troubleshooting steps.

If none of these steps resolve the issue, please provide more details about your setup, including the camera sensor model, device tree configuration, and any error messages you encounter.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

4

Why is the device tree related here? I am a beginner so I am a bit confused. It used to work fine and I could see a feed. But now I get this error everywhere

6

What’s the sensor? BSP version?

If imx219/imx477 you need to have jetson-io to enable it.

7

Hello, I have an IMX519. I followed the wiki here for the drivers and it worked perfectly on a new image but now I keep getting this nvarguscamerasrc error and I cannot do anything.

What would be the process of getting both cam0 and cam1 also working, thats also another thing i am struggling with

8

Confirm if the sensor driver probe successful or not.

v4l2-ctl --list-devices
9

It is, it shows up. I reflashed the OS and its working fine I am just scared that this error happens again and my only option is to reflash as it has happened twice already.

10

Confirm which device device tree in /boot/extlinux/extlinux.conf to backup it to restore if happened again.

  1. save the extlinux.conf and the dtb file show in the .conf
11

Hey! thanks for the speedy replies. I am a beginner so I am a bit confused. The device tree is stored under /boot/extlinux/extlinux.conf? and I should make a copy of that incase the error happens again?

Or any resources I could look at to learn?

12

Check the FDT in file /boot/extlinux/extlinux.conf that point the dtb current the system usage.

Example

LABEL JetsonIO
        MENU LABEL Custom Header Config: <CSI Jetson Camera E3333 module>
        LINUX /boot/Image
        FDT /boot/kernel_tegra194-p2888-0008-p2822-0000-user-custom.dtb
        INITRD /boot/initrd
        APPEND ${cbootargs} root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 rootfstype=ext4 video=efifb:off nospectre_bhb
~
13

So if anything were to ever happen, I can recompile the backup .dtb file and it should be good?

14

Suppose yes, if it cause by incorrect device tree config.

16

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