Imx219 board setup failed and no video in /dev/videox directory

Autonomous Machines Jetson & Embedded Systems Jetson Orin NX
,
1

When I run , sudo dmesg | grep imx219 in jetson orin nx developer kit (jetpack 5.1.2) L4T 35.4.1

[ 13.851482] imx219 9-0010: tegracam sensor driver:imx219_v2.0.6
[ 13.866853] imx219 9-0010: imx219_board_setup: error during i2c read probe (-121)
[ 13.882882] imx219 9-0010: board setup failed
[ 13.898506] imx219: probe of 9-0010 failed with error -121
[ 13.898792] imx219 10-0010: tegracam sensor driver:imx219_v2.0.6
[ 13.923009] imx219 10-0010: imx219_board_setup: error during i2c read probe (-121)
[ 13.938725] imx219 10-0010: board setup failed
[ 13.945293] imx219: probe of 10-0010 failed with error -121

Then, ls /dev/videoX*
Do not have any videoX in dev directory , even device have connected with CSI camera.

Is that any driver hot the camera has to be installed ?

Kindly aid me to get solve this issue.

2

Moving this topic to the Jetson forums for visibility.

1 Like
4

hello nexncommunication2023,

it’s reported failure for device registration.
are you using developer kits with Raspberry pi v2, imx219 camera module?
if yes, please try running Jetson-IO to Configure CSI Connector.

5

Hello JerryChang,
Thank you for your reply.
Am using imx219 camera module. I will try how to configure CSI connector and let you know.

6

Hi JerryChang,
Even after the configuration of CSI connector , There is no videox in /dev/videox directory.

could I know the reason for the below log board setup failed

[ 13.851482] imx219 9-0010: tegracam sensor driver:imx219_v2.0.6
[ 13.866853] imx219 9-0010: imx219_board_setup: error during i2c read probe (-121)
[ 13.882882] imx219 9-0010: board setup failed
[ 13.898506] imx219: probe of 9-0010 failed with error -121

7

hello nexncommunication2023,

it sometimes due to false hardware connection.
please check you’ve having correct pin direction of your flex ribbon cable.

8

Hello JerryChang ,

I had even checked the ribbon cable. Still this error persists.
kindly tell how could I solve this issue.
I also attached the output of contain the set of commands regarding camera module.

Error while connecting CSI camera to deepstream

deepstream-app -c source1_csi_dec_infer_resnet_int8.txt

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

nvstreammux: Successfully handled EOS for source_id=0

** INFO: <bus_callback:262>: Received EOS. Exiting …

v4l2-ctl --list-devices

NVIDIA Tegra Video Input Device (platform:tegra-camrtc-ca):

/dev/media0

Cannot open device /dev/video0, exiting.

nvgstcapture-1.0

  • Message: 13:12:28.617: main:4734 iterating capture loop …

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

NvMMLiteOpen : Block : BlockType = 4

===== NvVideo: NVENC =====

NvMMLiteBlockCreate : Block : BlockType = 4

ERROR on bus: by /GstPipeline:capture_native_pipeline: Output window was closed

debug info:

/dvs/git/dirty/git-master_linux/tests-multimedia/nvgstapps/nvgstcapture-1.0/nvgstcapture.c(4159): nvgst_handle_xevents (): /GstPipeline:capture_native_pipeline

** Message: 13:12:43.725: main:4744 Capture completed

** Message: 13:12:43.759: main:4795 Camera application will now exit

sudo dmesg | grep -i camera

[ 6.949321] gpio-397 (camera-control-output-low): hogged as output/low

[ 6.956092] gpio-486 (camera-control-output-low): hogged as output/low

[ 14.327037] input: UVC Camera (046d:0825) as /devices/platform/3610000.xhci/usb1/1-2/1-2.1/1-2.1:1.0/input/input9

[10099.040213] input: UVC Camera (046d:0825) as /devices/platform/3610000.xhci/usb1/1-2/1-2.1/1-2.1:1.0/input/input10

ls /dev/video*

v4l2-ctl -d2 -D

gst-launch-1.0 v4l2src device=/dev/video2 ! video/x-raw,width=1920,height=1080,framerate=65/1 ! fpsdisplaysink text-overlay=false video-sink=waylandsink sync=false -v

cat /proc/config.gz | gunzip | grep IMX

CONFIG_TOUCHSCREEN_IMX6UL_TSC is not set

CONFIG_VIDEO_IMX214 is not set

CONFIG_VIDEO_IMX219 is not set

CONFIG_VIDEO_IMX258 is not set

CONFIG_VIDEO_IMX274 is not set

CONFIG_VIDEO_IMX290 is not set

CONFIG_VIDEO_IMX319 is not set

CONFIG_VIDEO_IMX355 is not set

CONFIG_NV_VIDEO_IMX185=m

CONFIG_NV_VIDEO_IMX477=m

CONFIG_NV_VIDEO_IMX219=m

CONFIG_NV_VIDEO_IMX268=m

CONFIG_NV_VIDEO_IMX274=m

CONFIG_NV_VIDEO_IMX318=m

CONFIG_NV_VIDEO_IMX390=y

CONFIG_VIDEO_IMX204 is not set

CONFIG_SND_SOC_IMX_AUDMUX is not set

CONFIG_USB_CHIPIDEA_IMX=m

CONFIG_PHY_FSL_IMX8MQ_USB=y

sudo dmesg | grep imx219

[ 13.851482] imx219 9-0010: tegracam sensor driver:imx219_v2.0.6

[ 13.866853] imx219 9-0010: imx219_board_setup: error during i2c read probe (-121)

[ 13.882882] imx219 9-0010: board setup failed

[ 13.898506] imx219: probe of 9-0010 failed with error -121

[ 13.898792] imx219 10-0010: tegracam sensor driver:imx219_v2.0.6

[ 13.923009] imx219 10-0010: imx219_board_setup: error during i2c read probe (-121)

[ 13.938725] imx219 10-0010: board setup failed

[ 13.945293] imx219: probe of 10-0010 failed with error -121

cat /proc/device-tree/compatible

nvidia,p3768-0000+p3767-0000nvidia,p3767-0000nvidia,tegra234nvidia,tegra23x

cat /proc/device-tree/nvidia,dtbbuildtime

Aug 1 202312:44:16

9

let’s confirm you’re using Orin developer kits with Raspberry pi v2, imx219 camera module.
could you please share a picture of your device, thanks

10

Hello @JerryChang
I have attached the picture of the Nvidia Device with camera
Device Name : Nvidia Orin NX Developer Kit
Camera : UC-439 Model

Camera
Camera1920×2880 357 KB

IMG_20231005_122549
IMG_20231005_1225491920×3413 443 KB

Nvidia_Device_Topview
Nvidia_Device_Topview1920×3090 360 KB

How can I fix this problem? Is it HW prblm or CSI interface (Driver prblm)?

11

this is not Raspberry pi v2, imx219 camera module…

12

Okay ,If i change the camera module ,is it works ? because error occur as Board setup fails

And Can you mention any related IMX219 camera module ??

13

please see-also… https://jetsonhacks.com/2019/04/02/jetson-nano-raspberry-pi-camera/

14

I have attached another camera module named as p5vq4a sunny Raspberry Pi v2 ,can i use that camera module ?

15

hello nexncommunication2023,

it’s not plug-n-play, please apply kernel and device tree update to adapt the camera driver.
you may also contact with Jetson Partner Supported Cameras.

16

Hello JerryChang,

Could you please share any links to update kernel and device tree update to adapt the camera driver

17

hello nexncommunication2023,

you may read developer guide, Building the Kernel and Flashing a Specific Partition.

besides, you may consider using USB camera.
please see-also Camera Architecture Stack, you could bypass libargus, running with v4l2 interface to fetch the stream directly.

18

Hi JerryChang,

Thank you, I will definitely have gaze on the kink you have shared.

Even I do not have /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp .

Here my USB camera is working fine with my nvidia device. Connection of CSI camera with my nvidia is the actual problem.

sudo media-ctl -p -d /dev/media0

Media controller API version 5.10.120

Media device information

driver tegra-camrtc-ca
model NVIDIA Tegra Video Input Device
serial
bus info
hw revision 0x3
driver version 5.10.120

Device topology

  • entity 1: 13e40000.host1x:nvcsi@15a00000- (2 pads, 0 link)
    type V4L2 subdev subtype Unknown flags 0
    pad0: Sink
    pad1: Source

  • entity 4: 13e40000.host1x:nvcsi@15a00000- (2 pads, 0 link)
    type V4L2 subdev subtype Unknown flags 0
    pad0: Sink
    pad1: Source

How do I know my camera name because I do not have any details related to the name of the camera

19

Hello JerryChang,

sudo dmesg | grep -i csi

[ 1.590670] SCSI subsystem initialized
[ 2.241210] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 239)
[ 6.982541] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: context isolation disabled due to no IOMMU
[ 6.992169] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: initialized
[ 6.998646] tegra-camrtc-capture-vi tegra-capture-vi: subdev 13e40000.host1x:nvcsi@15a00000- bound
[ 7.007866] tegra-camrtc-capture-vi tegra-capture-vi: subdev 13e40000.host1x:nvcsi@15a00000- bound

20

hello nexncommunication2023,

CSI is passive. it’s simply send controls and waiting for sensor output streams to CSI channel.
please check your sensor is actually enabled and outputting MIPI signaling.

1 Like
21

Hello JerryChang,
I will try.