Enter recovery mode by following the instructions in one of the guides:
Quick Start Guide L4T 35.3.1 (NVIDIA Jetson Orin Nano, Orin NX, Xavier NX and AGX Xavier)
Quick Start Guide L4T 32.7.3 (NVIDIA Jetson Nano, TX2, Xavier NX and AGX Xavier)
Create a directory and clone the repository.
cd <working_dir>
git clone https://github.com/VC-MIPI-modules/vc_mipi_nvidia
Start the quickstart installation process and follow the instructions.
cd vc_mipi_nvidia/bin
./quickstart.sh
If you have changed your hardware setup simply execute this script again.
During the setup process of the quickstart.sh script, there will be executed the l4t_create_default_user.sh script from NVIDIA, which will create a default user with the credentials given by the user.
- After setting up the toolchain, the user is prompted to this credentials mask.
- This script has been available since L4T 32.6.1 and will be applied accordingly.
(Optional)
Set up the target by executing one of the following commands on the host computer when the target device is already running:
cd vc_mipi_nvidia/bin
./setup.sh --target
This function will configure a connection with the running target. It will backup the users known_hosts file and copy the users public rsa key, so that every time when a ssh connection to the device is opened, the user don't need to enter the password again. It will also copy the demo.sh and max_speed.sh script into the /home/username/test/ folder on the device.
For more information about the mentioned scripts, please run the appropriate script with the option "--help" in a shell on the running device.
vc@nvidia $./test/demo.sh --help
or
vc@nvidia $ ./test/max_speed.sh --help
When operating with the max_speed.sh script, it should be run as root.
E.g. speeding up the clocks:
vc@nvidia $ sudo ./test/max_speed.sh --max
If you want to use GStreamer with nvarguscamerasrc it is essential to adjust some properties in the device tree. To do that follow the instructions in this section. For each camera there is a mode0 node in the device tree. There is an additional comment in this node to mark the properties that you need to customize. In the tables below you will find the specific values for each camera.
The value of the property pixel_t lists the supported pixel formats. Here you have to choose one out of the following table.
pixel_t | value RAW08 | value RAW10 | value RAW12 |
---|---|---|---|
RGGB | bayer_rggb8 | bayer_rggb | bayer_rggb12 |
GBRG | bayer_gbrg8 | bayer_gbrg | bayer_gbrg12 |
The property max_framerate is given for the number of lanes and the pixel format. For example, 4L10 stands for 4 lanes and the pixel format RAW10. Always set the def_framerate to the same value as max_framerate
As an example the device tree for the IMX226 with 4 lanes and pixel format RAW10 is shown on the code snippet. Be aware of that the property values for gain are given in mdB [:)] and the frame rate in mHz. So, you have to multiply the values from the table with 1000.
...
// ----------------------------------------------------
// If you want to use GStreamer with nvarguscamerasrc
// you have to adjust this settings
physical_w = "7.222";
physical_h = "5.550";
// ----------------------------------------------------
// This node is needed by the Tegra framework.
// You don't have to change any settings if just want to use the V4L API.
mode0 {
...
// ----------------------------------------------------
// If you want to use GStreamer with nvarguscamerasrc
// you have to adjust this settings.
active_l = "0";
active_t = "0";
active_w = "3904";
active_h = "3000";
#if LINUX_VERSION < 500
pixel_t = "bayer_gbrg";
#else
mode_type = "bayer";
pixel_phase = "gbrg";
csi_pixel_bit_depth = "10";
#endif
min_gain_val = "0"; // 0.0 dB
max_gain_val = "27000"; // 27.0 dB
step_gain_val = "14"; // 0.014 dB
default_gain = "0"; // 0.0 dB
min_exp_time = "1"; // 1 us
max_exp_time = "1000000"; // 1000000 us
step_exp_time = "1"; // 1 us
default_exp_time = "10000"; // 10000 us
min_framerate = "1000"; // 1 Hz
max_framerate = "43600"; // 43.6 Hz
step_framerate = "100"; // 0.1 Hz
default_framerate = "43600"; // 43.6 Hz
// ----------------------------------------------------
...
If you want to change some settings of a camera in the device tree, please follow these steps.
Edit the device tree file for your hardware setup. | system on module | carrier board | device tree file |
---|---|---|---|
NVIDIA Jetson Nano | NVIDIA Jetson Nano Developer Kit | src/devicetree/NV_DevKit_Nano/tegra210-camera-vc-mipi-cam.dtsi | |
NVIDIA Jetson Nano | Auvidea JNX30 | src/devicetree/Auvidea_JNX30_Nano/tegra210-camera-vc-mipi-cam.dtsi | |
NVIDIA Jetson Nano | Auvidea JNX42 | src/devicetree/Auvidea_JNX42_Nano/tegra210-camera-vc-mipi-cam.dtsi | |
NVIDIA Jetson Xavier NX | NVIDIA Jetson Xavier NX Developer Kit | src/devicetree/NV_DevKit_XavierNX/tegra194-camera-vc-mipi-cam.dtsi | |
NVIDIA Jetson Xavier NX | Auvidea JNX30 | src/devicetree/Auvidea_JNX30_XavierNX/tegra194-camera-vc-mipi-cam.dtsi | |
NVIDIA Jetson Xavier NX | Auvidea JNX42 | src/devicetree/Auvidea_JNX42_XavierNX/tegra194-camera-vc-mipi-cam.dtsi | |
NVIDIA Jetson AGX Xavier | Auvidea J20 on DevKit | src/devicetree/Auvidea_J20_AGXXavier/tegra194-camera-vc-mipi-cam.dtsi | |
NVIDIA Jetson TX2 | Auvidea J20 on DevKit | src/devicetree/Auvidea_J20_TX2/tegra186-camera-vc-mipi-cam.dtsi | |
NVIDIA Jetson TX2 NX | Auvidea JNX30D | src/devicetree/Auvidea_JNX30D_TX2NX/tegra186-camera-vc-mipi-cam.dtsi | |
NVIDIA Jetson Orin Nano | NVIDIA Jetson Orin Nano Developer Kit | src/devicetree/NV_DevKit_OrinNano/tegra234-camera-vc-mipi-cam.dtsi Jetpack 5 (L4T 35.3.1, L4T 35.4.1) |
|
NVIDIA Jetson Orin Nano | NVIDIA Jetson Orin Nano Developer Kit | src/devicetree/NV_DevKit_OrinNano/tegra234-p3767-camera-p3768-vc_mipi-dual.dts Jetpack 6 (L4T 36.2.0 DP) |
|
NVIDIA Jetson Orin Nano | Auvidea JNX42 | src/devicetree/Auvidea_JNX42_OrinNano/tegra234-camera-vc-mipi-cam.dtsi | |
NVIDIA Jetson Orin NX | Auvidea JNX42 | src/devicetree/Auvidea_JNX42_OrinNX/tegra234-camera-vc-mipi-cam.dtsi |
To edit the correct device tree file you can simply use the setup script. It will open the correct device tree file in the nano editor.
./setup.sh --camera
Enter recovery mode by following the instructions in one of the guides:
Quick Start Guide L4T 35.3.1 (NVIDIA Jetson Orin Nano, Orin NX, Xavier NX and AGX Xavier)
Quick Start Guide L4T 32.7.3 (NVIDIA Jetson Nano, TX2, Xavier NX and AGX Xavier)
Build and flash the device tree files to the target.
./build.sh --dt
./flash.sh --dt
Regarding to Jetpack5 and higher, please have a look at the section Annotations.
Flashing the device
If you want to use your camera in an application with long exposure times or external trigger and the time between two consecutively triggers is potentially long (> 5 seconds) it is necessary to adjust the timeout of the csi receiver. In this case please change following line of code.
system on module | line | in file |
---|---|---|
NVIDIA Jetson Nano | 232 | /kernel/nvidia/drivers/media/platform/tegra/camera/vi/vi2_fops.c |
NVIDIA Jetson Xavier NX | 36 | /kernel/nvidia/drivers/media/platform/tegra/camera/vi/vi5_fops.c |
NVIDIA Jetson AGX Xavier | 36 | /kernel/nvidia/drivers/media/platform/tegra/camera/vi/vi5_fops.c |
NVIDIA Jetson TX2 | 1097 | /kernel/nvidia/drivers/media/platform/tegra/camera/vi/vi4_fops.c |
NVIDIA Jetson TX2 NX | 1097 | /kernel/nvidia/drivers/media/platform/tegra/camera/vi/vi4_fops.c |
You can find the revision of the camera module in the dmesg log.
dmesg | grep 'i2c'
[...] i2c 6-0010: +--- VC MIPI Camera -----------------------------------+
[...] i2c 6-0010: | MANUF. | Vision Components MID: 0x0427 |
[...] i2c 6-0010: | MODULE | ID: 0x0183 REV: 0012 |
[...] i2c 6-0010: | SENSOR | SONY IMX183 |
...
If you have your own BSP, you have to integrate the driver into it. Please follow these steps.
Apply all patches in the folder kernel_common_32.3.1+ and the patches listed in the following table that match your hardware setup
system on module | carrier board | BSP | all patches in folder patch/... |
---|---|---|---|
NVIDIA Jetson Nano | NVIDIA DevKit | 32.7.1 - 32.7.3 | kernel_Nano_32.6.1+ |
32.7.4 | kernel_Nano_32.6.1+ kernel_Nano_32.7.4 |
||
Auvidea JNX30 | 32.7.1 - 32.7.3 | kernel_Nano_32.6.1+ dt_Auvidea_JNX30_Nano_32.5.0+ |
|
32.7.4 | kernel_Nano_32.6.1+ kernel_Nano_32.7.4 dt_Auvidea_JNX30_Nano_32.5.0+ |
||
Auvidea JNX42 | 32.7.1 - 32.7.3 | kernel_Nano_32.6.1+ dt_Auvidea_JNX30_Nano_32.5.0+ |
|
32.7.4 | kernel_Nano_32.6.1+ kernel_Nano_32.7.4 dt_Auvidea_JNX30_Nano_32.5.0+ |
||
NVIDIA Jetson Xavier NX | NVIDIA DevKit | 32.7.1 - 32.7.2 | kernel_Xavier_32.6.1+ |
32.7.3 | kernel_Xavier_32.7.3+ | ||
35.1.0 | kernel_Xavier_35.1.0+ | ||
35.2.1 | kernel_Xavier_35.2.1+ | ||
35.3.1 | kernel_Xavier_35.3.1+ | ||
35.4.1 | kernel_Xavier_35.4.1+ | ||
Auvidea JNX30 | 32.7.1 - 32.7.2 | kernel_Xavier_32.6.1+ dt_Auvidea_JNX30_XavierNX_32.5.0+ |
|
32.7.3 | kernel_Xavier_32.7.3+ dt_Auvidea_JNX30_XavierNX_32.5.0+ |
||
35.1.0 | kernel_Xavier_35.1.0+ | ||
35.2.1 | kernel_Xavier_35.2.1+ | ||
35.3.1 | kernel_Xavier_35.3.1+ | ||
35.4.1 | kernel_Xavier_35.4.1+ | ||
Auvidea JNX42 | 32.7.1 - 32.7.2 | kernel_Xavier_32.6.1+ dt_Auvidea_JNX30_XavierNX_32.5.0+ |
|
32.7.3 | kernel_Xavier_32.7.3+ dt_Auvidea_JNX30_XavierNX_32.5.0+ |
||
35.1.0 | kernel_Xavier_35.1.0+ | ||
35.2.1 | kernel_Xavier_35.2.1+ | ||
35.3.1 | kernel_Xavier_35.3.1+ | ||
35.4.1 | kernel_Xavier_35.4.1+ | ||
NVIDIA Jetson AGX Xavier | DevKit + J20 | 32.7.1 - 32.7.2 | kernel_Xavier_32.6.1+ |
32.7.3 | kernel_Xavier_32.7.3+ | ||
35.1.0 | kernel_Xavier_35.1.0+ | ||
35.2.1 | kernel_Xavier_35.2.1+ | ||
35.3.1 | kernel_Xavier_35.3.1+ | ||
35.4.1 | kernel_Xavier_35.4.1+ | ||
NVIDIA Jetson TX2 | DevKit + J20 | 32.7.1 - 32.7.2 | kernel_Xavier_32.6.1+ |
32.7.3 | kernel_Xavier_32.7.3+ | ||
NVIDIA Jetson TX2 NX | Auvidea JNX30D | 32.7.1 - 32.7.2 | kernel_Xavier_32.6.1+ |
32.7.3 | kernel_Xavier_32.7.3+ | ||
NVIDIA Jetson Orin Nano | NVIDIA DevKit | 35.3.1 | kernel_Xavier_35.3.1+ |
35.4.1 | kernel_Xavier_35.4.1+ | ||
36.2.0 | kernel_Xavier_36.2.0+ * | ||
Auvidea JNX42 | 35.3.1 | kernel_Xavier_35.3.1+ | |
35.4.1 | kernel_Xavier_35.4.1+ | ||
NVIDIA Jetson Orin NX | Auvidea JNX42 | 35.2.1 | kernel_Xavier_35.2.1+ |
35.3.1 | kernel_Xavier_35.3.1+ | ||
35.4.1 | kernel_Xavier_35.4.1+ |
*) For L4T 36.2.0, the kernel_common_32.3.1+ must be left out.
Copy the camera device tree to the folder listed in the following table
system on module | carrier board | copy from src/devicetree/... to folder |
---|---|---|
NVIDIA Jetson Nano | NVIDIA DevKit | NV_DevKit_Nano/tegra210-camera-vc-mipi-cam.dtsi => /hardware/nvidia/platform/t210/porg/kernel-dts/porg-platforms |
Auvidea JNX30 | Auvidea_JNX30_Nano/tegra210-camera-vc-mipi-cam.dtsi => /hardware/nvidia/platform/t210/porg/kernel-dts/porg-platforms |
|
Auvidea JNX42 | Auvidea_JNX42_Nano/tegra210-camera-vc-mipi-cam.dtsi => /hardware/nvidia/platform/t210/porg/kernel-dts/porg-platforms |
|
NVIDIA Jetson Xavier NX | NVIDIA DevKit | NV_DevKit_XavierNX/tegra194-camera-vc-mipi-cam.dtsi => /hardware/nvidia/platform/t19x/jakku/kernel-dts/common |
Auvidea JNX30 | Auvidea_JNX30_XavierNX/tegra194-camera-vc-mipi-cam.dtsi => /hardware/nvidia/platform/t19x/jakku/kernel-dts/common |
|
Auvidea JNX42 | Auvidea_JNX42_XavierNX/tegra194-camera-vc-mipi-cam.dtsi => /hardware/nvidia/platform/t19x/jakku/kernel-dts/common |
|
NVIDIA Jetson AGX Xavier | DevKit + J20 | Auvidea_J20_AGXXavier/tegra194-camera-vc-mipi-cam.dtsi => /hardware/nvidia/platform/t19x/common/kernel-dts/t19x-common-modules |
NVIDIA Jetson TX2 | DevKit + J20 | Auvidea_J20_TX2/tegra186-camera-vc-mipi-cam.dtsi => /hardware/nvidia/platform/t18x/common/kernel-dts/t18x-common-modules |
NVIDIA Jetson TX2 NX | Auvidea JNX30D | Auvidea_JNX30D_TX2NX/tegra186-camera-vc-mipi-cam.dtsi => /hardware/nvidia/platform/t18x/lanai/kernel-dts/common |
NVIDIA Jetson Orin Nano | NVIDIA DevKit | NV_DevKit_OrinNano/tegra234-camera-vc-mipi-cam.dtsi => /hardware/nvidia/platform/t23x/p3768/kernel-dts/cvb (device tree include file used for Jetpack 5) |
NV_DevKit_OrinNano/tegra234-p3767-camera-p3768-vc_mipi-dual.dts => /hardware/nvidia/t23x/nv-public/overlay (device tree overlay file for Jetpack 6) |
||
Auvidea JNX42 | Auvidea_JNX42_OrinNano/tegra234-camera-vc-mipi-cam.dtsi => /hardware/nvidia/platform/t23x/p3768/kernel-dts/cvb |
|
NVIDIA Jetson Orin NX | Auvidea JNX42 | Auvidea_JNX42_OrinNX/tegra234-camera-vc-mipi-cam.dtsi => /hardware/nvidia/platform/t23x/p3768/kernel-dts/cvb |
Copy all driver files from folder src/driver to /kernel/nvidia/drivers/media/i2c
To test the camera you can use v4l2-test
When the system has booted successfully, it is necessary to run the script max_speed.sh from the /target folder as superuser. It will read out the maximum frequencies and set them as the current ones. This is a recommendation from nvidia.
sudo ./max_speed.sh --max
with this L4T 36.2 version, the tegra part is completely separated from the kernel
VC Mipi driver is now running as a couple of kernel modules
modifications to the camera device tree are realised with device tree overlays
nvarguscamerasrc+nvvidconv must be installed separately (gst-nvarguscamera_src.tbz2 and gst-nvvidconv_src.tbz2 are residing in the Linux_for_Tegra/source folder and will be copied automatically into the home directory of the target device)
a convenience script setup_nvidia.sh can be called on the running jetson to install some prerequisites (an internet connection must be present)
device tree handling
./setup.sh --camera
./build.sh --dt
| this step is automatically done by ./build.sh --all
sudo ./flash.sh --all
, the overlay file will be flashed into uefithe dtbo file must be copied into the specified location before the restart
LABEL secondary
MENU LABEL secondary kernel
LINUX /boot/Image
FDT /boot/dtb/kernel_tegra234-p3768-0000+p3767-0005-nv.dtb
INITRD /boot/initrd
APPEND ...
OVERLAYS /boot/tegra234-p3767-camera-p3768-vc_mipi-dual.dtbo
- this version has been tested with two identical IMX565, IMX567/8, IMX296, IMX226, IMX415 sensors
- there might be problems when using only a single sensor
Regarding to flashing issues, please have a look at Flashing the device