Camera IMX219-IR-CUT Waveshark not working with Nvidia Jetson Nano

When trying to connect the waveshark imx219-IR-CUT camera, errors are generated and the camera image does not appear on the monitor. According to the manufacturer’s recommendations, the camera is compatible with the jetsonen nano.

Here are the errors that appear:

etson@jetson-desktop:~$ ls /dev/video
/dev/video0
jetson@jetson-desktop:~$ DISPLAY=:0.0 gst-launch-1.0 nvarguscamerasrc ! ‘video/xraw(memory:NVMM), width=3280, height=2464, format=(string)NV12, framerate=(fraction)20/1’ !
nvoverlaysink -e
Invalid MIT-MAGIC-COOKIE-1 keynvbuf_utils: Could not get EGL display connection
Setting pipeline to PAUSED …
Pipeline is live and does not need PREROLL …
Setting pipeline to PLAYING …
New clock: GstSystemClock
GST_ARGUS: Creating output stream
Invalid MIT-MAGIC-COOKIE-1 keyCONSUMER: Waiting until producer is connected…
GST_ARGUS: Available Sensor modes :
GST_ARGUS: 3264 x 2464 FR = 21,000000 fps Duration = 47619048 ; Analog Gain range min
1,000000, max 10,625000; Exposure Range min 13000, max 683709000;
GST_ARGUS: 3264 x 1848 FR = 28,000001 fps Duration = 35714284 ; Analog Gain range min
1,000000, max 10,625000; Exposure Range min 13000, max 683709000;
GST_ARGUS: 1920 x 1080 FR = 29,999999 fps Duration = 33333334 ; Analog Gain range min
1,000000, max 10,625000; Exposure Range min 13000, max 683709000;
GST_ARGUS: 1640 x 1232 FR = 29,999999 fps Duration = 33333334 ; Analog Gain range min
1,000000, max 10,625000; Exposure Range min 13000, max 683709000;
GST_ARGUS: 1280 x 720 FR = 59,999999 fps Duration = 16666667 ; Analog Gain range min
1,000000, max 10,625000; Exposure Range min 13000, max 683709000;
GST_ARGUS: 1280 x 720 FR = 120,000005 fps Duration = 8333333 ; Analog Gain range min
1,000000, max 10,625000; Exposure Range min 13000, max 683709000;
GST_ARGUS: Running with following settings:

  • Camera index = 0*
  • Camera mode = 0*
  • Output Stream W = 3264 H = 2464*
  • seconds to Run = 0*
  • Frame Rate = 21,000000*
    GST_ARGUS: Setup Complete, Starting captures for 0 seconds
    GST_ARGUS: Starting repeat capture requests.
    CONSUMER: Producer has connected; continuing.
    ERROR: from element /GstPipeline:pipeline0/GstNvArgusCameraSrc:nvarguscamerasrc0:
    CANCELLED
    Additional debug info:
    Argus Error Status
    EOS on shutdown enabled – waiting for EOS after Error
    Waiting for EOS…
    nvbuf_utils: dmabuf_fd -1 mapped entry NOT found
    nvbuf_utils: Can not get HW buffer from FD… Exiting…
    CONSUMER: ERROR OCCURRED
    (Argus) Error EndOfFile: Unexpected error in reading socket (in
    src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadCore(), line 266)
    (Argus) Error EndOfFile: Receiving thread terminated with error (in
    src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadWrapper(), line 368)

and

~$ DISPLAY=:0.0 gst-launch-1.0 nvarguscamerasrc ! 'video/x-raw(memory:NVMM), width=3280,
height=2464, format=(string)NV12, framerate=(fraction)20/1’ ! nvoverlaysink -e
Invalid MIT-MAGIC-COOKIE-1 keynvbuf_utils: Could not get EGL display connection
Setting pipeline to PAUSED …
Pipeline is live and does not need PREROLL …
Setting pipeline to PLAYING …
New clock: GstSystemClock
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gstnvarguscamera/gstnvarguscamerasrc.cpp, execute:725 No cameras available
Got EOS from element “pipeline0”.
Execution ended after 0:00:00.027239175
Setting pipeline to PAUSED …
Setting pipeline to READY …
Setting pipeline to NULL …
Freeing pipeline …

Should I install any drivers, please help ?

Sorry for the late response, is this still an issue to support? Thanks

Did you integrate the driver from the vendor?
The error could be the context in tegra-camera-platform{} of device tree cause the issue.

Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gstnvarguscamera/gstnvarguscamerasrc.cpp, execute:725 No cameras available

Integrate the driver from the vendor ? Could I please have more information on how to do this ? I am a beginner in jetson nano.

I also noticed that after the command:
ls/dev/video* - I get the response -
ls: cannot access ‘dev/video*’: No such file or directory.

I gather that as if jetson does not see the camera at all

That tell your sensor driver didn’t load correct. If could be the driver or device tree configure problem.
Have a check below document for the driver implement.

https://docs.nvidia.com/jetson/l4t/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/camera_dev.html#

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