I have a Jetson Orin NX 16 GB with the AVerMedia D131 carrier board that has two 22-pin CSI inputs and supposedly works with the Raspberry Pi camera. I cannot get it to work though. If I run
gst-launch-1.0 nvarguscamerasrc ! "video/x-raw(memory:NVMM), width=1920, height=1080, format=(string)NV12, framerate=(fraction)30/1" ! nvoverlaysink -e
I get the following output:
(Argus) Error Timeout: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function openSocketConnection(), line 219)
(Argus) Error Timeout: Cannot create camera provider (in src/rpc/socket/client/SocketClientDispatch.cpp, function createCameraProvider(), line 106)
(gst-plugin-scanner:4712): GStreamer-WARNING **: 14:25:17.084: Failed to load plugin '/usr/lib/aarch64-linux-gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block
(gst-plugin-scanner:4712): GStreamer-WARNING **: 14:25:17.120: Failed to load plugin '/usr/lib/aarch64-linux-gnu/gstreamer-1.0/libgstchromaprint.so': /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block
I already figured out that the bottom two errors can be fixed by running
export LD_PRELOAD=/usr/lib/aarch64-linux-gnu/libgomp.so.1
If I do that, the above command is still stuck though, and nothing happens, other than the Error Timeout errors after a couple of minutes.
v4l2-ctl --list-devices is just stuck and nothing happens (I can’t even ctrl-c or ctrl-z it, have to force kill it). Trying to sudo systemctl restart nvargus-daemon.service does not work either, the command is just stuck. Weirdly, running v4l2-ctl -d0 --list-ctrls gives me some indication that the camera is detected, since it immediately outputs
VIDIOC_QUERYCAP: ok
Camera Controls
group_hold 0x009a2003 (bool) : default=0 value=0 flags=execute-on-write
sensor_mode 0x009a2008 (int64) : min=0 max=7 step=1 default=0 value=0 flags=slider
gain 0x009a2009 (int64) : min=16 max=128 step=1 default=16 value=16 flags=slider
exposure 0x009a200a (int64) : min=26 max=500000 step=1 default=33333 value=26 flags=slider
frame_rate 0x009a200b (int64) : min=2000000 max=15000000 step=1 default=15000000 value=2000000 flags=slider
sensor_configuration 0x009a2032 (u32) : min=0 max=4294967295 step=1 default=0 [22] flags=read-only, volatile, has-payload
sensor_mode_i2c_packet 0x009a2033 (u32) : min=0 max=4294967295 step=1 default=0 [1026] flags=read-only, volatile, has-payload
sensor_control_i2c_packet 0x009a2034 (u32) : min=0 max=4294967295 step=1 default=0 [1026] flags=read-only, volatile, has-payload
bypass_mode 0x009a2064 (intmenu): min=0 max=1 default=0 value=0
override_enable 0x009a2065 (intmenu): min=0 max=1 default=0 value=0
height_align 0x009a2066 (int) : min=1 max=16 step=1 default=1 value=1
size_align 0x009a2067 (intmenu): min=0 max=2 default=0 value=0
write_isp_format 0x009a2068 (int) : min=1 max=1 step=1 default=1 value=1
sensor_signal_properties 0x009a2069 (u32) : min=0 max=4294967295 step=1 default=0 [30][18] flags=read-only, has-payload
sensor_image_properties 0x009a206a (u32) : min=0 max=4294967295 step=1 default=0 [30][16] flags=read-only, has-payload
sensor_control_properties 0x009a206b (u32) : min=0 max=4294967295 step=1 default=0 [30][36] flags=read-only, has-payload
sensor_dv_timings 0x009a206c (u32) : min=0 max=4294967295 step=1 default=0 [30][16] flags=read-only, has-payload
low_latency_mode 0x009a206d (bool) : default=0 value=0
preferred_stride 0x009a206e (int) : min=0 max=65535 step=1 default=0 value=0
sensor_modes 0x009a2082 (int) : min=0 max=30 step=1 default=30 value=7 flags=read-only
I have no idea what’s wrong, but it seems like an nvidia argus issue. Does anyone have any ideas?