Having trouble using gstreamer with imx185 camera on spacely carrier board

Hello,

I am having issues using an imx185 camera on a spacely carrier board.

I’m using a tx2 that is flashed with the latest Jetpack and the BSP used is spacely-imx185-3cam.

The camera is connected through a FAW cable to csi0,1 and its DIP switch is set to master mode. The spacely’s S3 DIP switches are off.

The problem occurs when I use the example gstreamer pipeline from Connect Tech’s site:

gst-launch-1.0 nvarguscamerasrc sensor-id=0 ! "video/x-raw(memory:NVMM),height=1080, width=1920, format=NV12, framerate=60/1" ! nvvidconv ! xvimagesink -ev &

This gives me the following error:

GST_ARGUS: Creating output stream
(Argus) Error BadParameter: (propagating from src/eglstream/FrameConsumerImpl.cpp. function initialize(), line 89)
(Argus) Error BadParameter: (propagating from src/eglstream/FrameConsumerImpl.cpp. function create(), line 44)
Error generated. /dvs/git/dirte/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, threadInitialize:220 Failed to create FrameConsumer

I also took a look at dmesg and noticed the following lines:

imx185 35-001a: probing v4l2 sensor
imx185 35-001a: reset-gpios not found 0
tegra-vi4 15700000.vi: subdev imx185 30-001a bound
imx185 35-001a: tegra camera driver registration failed

Could anyone give guidance as to the next step?

Hi,

If the imx185 is from our partners, please contact the vendor to get support.
Or you may follow [Sensor Software Driver Programming Guide] to program device tree.
https://docs.nvidia.com/jetson/l4t/index.html

Hi AJMathews,
I would suggest you to initially test one camera module by removing all other device entries in the device-tree(tegra-camera-platform) provided by the vendor’s kernel source.
This could help corner down the issue.