Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, execute:740 No cameras available

I have li-imx219-mipi-ff-nano-h136 v1.3 camera and it’s not working. Can someone help me step by step?

hello kara5225,

Jetson Nano support Raspberry Pi Camera Module 2, IMX219 by default.
I assume this is camera module from one of Jetson Camera Partners, please contact with vendor for further supports.


I have another one. Will this work?

hello kara5225,

yes, it looks like the camera module supported with Jetson Nano.
please double check you’re having correct pin connections to the camera connector.
please have camera device connected before power-on, besides, you may dig into kernel init messages, such as $ dmesg | grep imx219 for the details of camera device registration.

Hi again Jerry,

[ 1.316363] imx219 7-0010: tegracam sensor driver:imx219_v2.0.6
[ 1.339731] imx219 7-0010: imx219_board_setup: error during i2c read probe (-121)
[ 1.339805] imx219 7-0010: board setup failed
[ 1.339858] imx219: probe of 7-0010 failed with error -121
[ 1.340293] imx219 8-0010: tegracam sensor driver:imx219_v2.0.6
[ 1.363645] imx219 8-0010: imx219_board_setup: error during i2c read probe (-121)
[ 1.363704] imx219 8-0010: board setup failed
[ 1.363753] imx219: probe of 8-0010 failed with error -121

I don’t understand correctly this one. Is it connected or nah?

hello kara5225,

FYI,
during kernel initialization stage, it’s step for camera device registration to setup a video device node to linux kernel. sensor probing only run once during kernel initialization stage of system boot-up.
for a typical camera application running cycle, the driver will Power On the sensor, Start Sensor Streaming, sending relevant v4l2 controls, and finally power off the sensor.
so… if there’s a error returns, it’ll not register a video node, (/dev/video0).

please double check your hardware connections, especially the direction of the golden finger.

Hey Jerry,

I worked downside and capture screenshot not my photo. What’s the reason of this?

jetson@jetson:~$ nvgstcapture-1.0 --orientation=3
Encoder null, cannot set bitrate!
Encoder Profile = High
Supported resolutions in case of ARGUS Camera
(2) : 640x480
(3) : 1280x720
(4) : 1920x1080
(5) : 2104x1560
(6) : 2592x1944
(7) : 2616x1472
(8) : 3840x2160
(9) : 3896x2192
(10): 4208x3120
(11): 5632x3168
(12): 5632x4224

Runtime ARGUS Camera Commands:

Help : ‘h’
Quit : ‘q’
Set Capture Mode:
mo:
(1): image
(2): video
Get Capture Mode:
gmo
Set sensor orientation:
so:
(0): none
(1): Rotate counter-clockwise 90 degrees
(2): Rotate 180 degrees
(3): Rotate clockwise 90 degrees
Get sensor orientation:
gso
Set sensor mode:
smo: e.g., smo:1
Get sensor mode:
gsmo
Set Whitebalance Mode:
wb:
(0): off
(1): auto
(2): incandescent
(3): fluorescent
(4): warm-fluorescent
(5): daylight
(6): cloudy-daylight
(7): twilight
(8): shade
(9): manual
Get Whitebalance Mode:
gwb
Set Saturation (0 to 2):
st: e.g., st:1.25
Get Saturation:
gst
Set Exposure Compensation (-2 to 2):
ec: e.g., ec:-2
Get Exposure Compensation:
gec
Set Auto Whitebalance Lock:
awbl: e.g., awbl:0
Get Auto Whitebalance Lock:
awbl
Set Auto Exposure Lock:
ael: e.g., ael:0
Get Auto Exposure Lock:
gael
Set TNR Mode:
tnrm: e.g., tnrm:1
(0): OFF
(1): FAST
(2): HIGH QUALITY
Get TNR Mode:
gtnrm
Set TNR Strength (-1 to 1):
tnrs: e.g., tnrs:0.5
Get TNR Strength:
gtnrs
Set EE Mode:
eem: e.g., eem:1
(0): OFF
(1): FAST
(2): HIGH QUALITY
Get EE Mode:
geem
Set EE Strength (-1 to 1):
ees: e.g., ees:0.5
Get EE Strength:
gees
Set Auto Exposure Anti-Banding (0 to 3):
aeab: e.g., aeab:2
(0): OFF
(1): MODE AUTO
(2): MODE 50HZ
(3): MODE 60HZ
Get Auto Exposure Anti-Banding:
gaeab
Set Gain Range:
gr: e.g., gr:1 16
Get Gain Range:
ggr
Set Exposure Time Range:
etr: e.g., etr:34000 35000
Get Exposure Time Range:
getr
Set ISP Digital Gain Range:
dgr: e.g., dgr:2 152
Get ISP Digital Gain Range:
gdgr
Capture: enter ‘j’ OR
followed by a timer (e.g., jx5000, capture after 5 seconds) OR
followed by multishot count (e.g., j:6, capture 6 images)
timer/multihot values are optional, capture defaults to single shot with timer=0s
Start Recording : enter ‘1’
Stop Recording : enter ‘0’
Video snapshot : enter ‘2’ (While recording video)
Get Preview Resolution:
gpcr
Get Image Capture Resolution:
gicr
Get Video Capture Resolution:
gvcr

Runtime encoder configuration options:

Set Encoding Bit-rate(in bytes):
br: e.g., br:4000000
Get Encoding Bit-rate(in bytes):
gbr
Set Encoding Profile(only for H.264):
ep: e.g., ep:1
(0): Baseline
(1): Main
(2): High
Get Encoding Profile(only for H.264):
gep
Force IDR Frame on video Encoder(only for H.264):
Enter ‘f’

bitrate = 4000000
Encoder Profile = High
Encoder control-rate = 1
Encoder EnableTwopassCBR = 0

Using winsys: x11
Opening in BLOCKING MODE
** Message: 11:51:37.565: main:4648 iterating capture loop …
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, execute:740 No cameras available
NvMMLiteOpen : Block : BlockType = 4
===== NVMEDIA: NVENC =====
NvMMLiteBlockCreate : Block : BlockType = 4
^C** Message: 11:52:02.605: <_intr_handler:4239> User Interrupted…

Terminating the camera pipeline …
** Message: 11:52:02.994: main:4658 Capture completed
** Message: 11:52:02.994: main:4707 Camera application will now exit

jetson@jetson:~/CSI-Camera$ gst-launch-1.0 nvarguscamerasrc sensor_id=0 ! ‘video/x-raw(memory:NVMM),width=3280, height=2464, framerate=21/1, format=NV12’ ! nvvidconv flip-method=2 ! ‘video/x-raw, width=816, height=616’ ! nvvidconv ! nvegltransform ! nveglglessink -e
Setting pipeline to PAUSED …

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
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, execute:740 No cameras available
Got EOS from element “pipeline0”.
Execution ended after 0:00:00.098910169
Setting pipeline to PAUSED …
Setting pipeline to READY …
Setting pipeline to NULL …
Freeing pipeline …

hello kara5225,

let’s dig into kernel logs to ensure you’ve camera device detected, and there’s /dev/video0.

It’s working.

/dev/video0

I saw this.

hello kara5225,

did you meant you cannot access to camera stream via nvarguscamerasrc plugin although there’s video node?

Hi again Jerry,

Yes, that’s what I meant. i see the /dev/video0 text, but the camera is still not working. What do you think the problem is?

hello kara5225,

please review your sensor device tree settings,
it’s check those sensor settings within Property-Value Pairs to initial the stream.

besides, is it a Jetson Nano developer kit?
may I also confirm which Jetpack release version you’re working with.

Hey Jerry, sorry for late

Actually, i don’t understand device tree settings clearly. Can you explain step by step? Also i’m using Jetpack 4.6.1.

Thanks for answer.

hello kara5225,

(1) please double check your camera hardware, Jetson Nano support Raspberry Pi Camera Module 2, IMX219 by default. please have cross validation to confirm it’s not due to hardware damage.

(2) you may having some device tree changes if that’s not default IMX219, please contact with sensor vendor for further supports.

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