first of all everything works just fine with Jetpack 4.6.
I tried to use Jetpack 5.0.1 DP however was not able to get the CSI Camera running (IMX219).
nvarguscamerasrc sensor_id=0 returns: nvarguscamerasrc: command not found
Other scripts failed with:
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, execute:751 No cameras available
v4l2-ctl --all returns no camera while the output on JP 4.6 is as expected.
Do you have any idea how get CSI Cameras running under Jetpack 5?
To be precise I tested that camera: IMX219-160 Camera - Waveshare Wiki
However it shouldn’t matter because the imager is the same and only the lens is different.
And as said, every release before Jetpack 5 was working just fine. I even back tested.
Works for me on NX DevKit with Jetpack 5.0.1 DP. Default kernel, no UEFI bootloader, default device tree.
root@nx:/boot/extlinux# v4l2-ctl --all
Driver Info:
Driver name : tegra-video
Card type : vi-output, imx219 10-0010
Bus info : platform:tegra-capture-vi:2
Driver version : 5.10.65
Capabilities : 0x84200001
Video Capture
Streaming
Extended Pix Format
Device Capabilities
Device Caps : 0x04200001
Video Capture
Streaming
Extended Pix Format
Media Driver Info:
Driver name : tegra-camrtc-ca
Model : NVIDIA Tegra Video Input Device
Serial :
Bus info :
Media version : 5.10.65
Hardware revision: 0x00000003 (3)
Driver version : 5.10.65
Interface Info:
ID : 0x0300000b
Type : V4L Video
Entity Info:
ID : 0x00000009 (9)
Name : vi-output, imx219 10-0010
Function : V4L2 I/O
Pad 0x0100000a : 0: Sink
Link 0x0200000f: from remote pad 0x1000006 of entity ‘13e10000.host1x:nvcsi@15a00000-’: Data, Enabled
Priority: 2
Video input : 0 (Camera 2: ok)
Format Video Capture:
Width/Height : 3280/2464
Pixel Format : ‘RG10’ (10-bit Bayer RGRG/GBGB)
Field : None
Bytes per Line : 6560
Size Image : 16163840
Colorspace : sRGB
Transfer Function : Default (maps to sRGB)
YCbCr/HSV Encoding: Default (maps to ITU-R 601)
Quantization : Default (maps to Full Range)
Flags :
please have a try as mentioned by shane24 to modify the pipeline,
furthermore, please also share the complete logs for (i.e. $ dmesg > klogs.txt ) reference, thanks
according to those failures, it means camera device did not register to kernel driver, and there’s error about i2c communication.
such i2c communication issue often related to power issue, could you please review the driver for the regulator settings, you may also narrow down the issue by examine the power-on/off sequence, thanks