VEYE CS Camera for Jetson TX2

From wiki_veye
Jump to navigation Jump to search


How to use VEYE and CS series camera module on NVIDIA Jetson Nano,TX2,Xavier and Orin

1 Overview

This guide shows how to use VEYE and CS series camera modules on Jetson Nano,Jetson Nano 2GB,TX2,TX2 NX,AGX Xavier and Xavier NX. Jetson SDK Version is:

  • Jetpack4.2.2,L4T r32.2.1
  • Jetpack4.3,L4T r32.3.1
  • Jetpack4.4,L4T r32.4.3
  • Jetpack4.4.1,L4T r32.4.4
  • Jetpack4.5,L4T r32.5
  • Jetpack4.5.1,L4T r32.5.1
  • Jetpack4.6,L4T r32.6.1
  • Jetpack4.6.1, L4T r32.7.1
  • Jetpack4.6.2,L4T r32.7.2
  • Jetpack4.6.3,L4T r32.7.3
  • Jetpack5.0.1DP, L4T r34.1.1
  • Jetpack5.0.2, L4T r35.1
  • Jetpack5.1,L4T r35.2.1
  • Jetpack5.1.1,L4T r35.3.1
  • Jetpack5.1.2,L4T r35.4.1

We provide two ways to do so: Prebuilt Binaries or Source Code. Yes, It's Open Source!

VEYE and CS series camera modules are camera module with ISP functions build in. It output UYVY data using MIPI-CSI2. We provide V4L2 interface for video streaming apps , and Video Control Toolkits (which is Shell Script) to control the camera module directly, which is called DRA(Directly Register Access).

1.1 Camera module list

Camera module dirver status list
Series Model Status
VEYE series VEYE-MIPI-IMX327S Done
VEYE series VEYE-MIPI-IMX385 Done
VEYE series VEYE-MIPI-IMX462 Done
VEYE series VEYE-MIPI-IMX335 Done
CS series CS-MIPI-IMX307 Done
CS series CS-MIPI-SC132 Done

1.2 How to check the current L4T version

1.2.1 Method 1

On Jetson board

cat /etc/nv_tegra_release

If it shows:

# R32 (release), REVISION: 4.3......

It means L4t Version is 32.4.3

1.2.2 Method 2

Refer to this link to install jetson-stats:


2 Hardware Setup

We have designed a 6cam interposer board for TX2 devkit,Xavier and Orin, It support up to 6 cameras at the same time.

6cam interposer board connected with 6 cameras
6cam interposer board connected with 6 cameras

In particular, the VEYE-MIPI-IMX335 must use a 12V DC terminal to provide auxiliary power due to its high power consumption. Refer to J11 of ADP-N1.

2.1 NVIDIA TX2 Developer Kit

It is connected as shown in figure:

TX2 Devkit 6 cameras connection
TX2 Devkit 6 cameras connection

Be sure to screw the ADP adapter board to the bottom board.

2.2 NVIDIA AGX Xavier(the same with Orin)

Connect VEYE cameras to AGX Xavier
Connect VEYE cameras to AGX Xavier

Be sure to screw the ADP adapter board to the bottom board to ensure that the adapter plate is installed flat.

2.3 NVIDIA Nano ,TX2 NX and Xavier NX Devkit

The Xavier NX interface is compatible with raspberry pi and Jetson Nano. The connection mode is shown in figure:

Xavier NX connection with VEYE-MIPI-327
Xavier NX connection with VEYE-MIPI-327

Xavier NX connection with CS-MIPI-IMX307
Xavier NX connection with CS-MIPI-IMX307
Jetson Nano A02 与VEYE模组连接
VEYE327 connection with Jetson Nano A02
VEYE camera  connection with Orin Nano and Orin NX

3 Upgrade Jetson Nano, TX2,Xavier and Orin system

3.1 Overview

This section describes how to upgrade the Jetson system to support our camera module.

  • Jetpack4.x versions

To support our camera module, we need to update the two parts of the L4T (Linux for Tegra) of the Jetson system, Image and DTB.

In the Image, we added the camera driver, while the DTB indicates the camera model used. In general, you only need to use the Image and DTB, that we have prebuilt, and you don't need to build from source when it is not necessary.

  • Jetpack5.x versions

The driver is no longer compiled into the Image, but loaded into the system as a separate module. The dtb file is still compiled together as a whole to facilitate replacement.

The dtb can also be loaded dynamically as an overlay. Refer to the official nVidia Developer's Guide for NVIDIA® Jetson™ Linux for details.

  • For MV series camera

For MV series modules, we have added features to Image in order to support extended data types and external trigger modes. So regardless of Jetpack version, you need to update Image.

Whether you need to update modules depends on Jetpack version.

3.2 BSP package introduction

3.2.1 Path

3.2.2 bsp package includes:
  • prebuilt dtb for different boards
  • driver source code
  • dts source code
  • i2c toolkits

In release packages

  • prebuilt linux kernel:Image
  • prebuilt camera drivers

3.3 DTB file corresponds to Jetson boards

3.3.1 Nano A02


3.3.2 Nano B01 Devkit


3.3.3 Nano B01 4G emmc


3.3.4 Nano 2GB


3.3.5 TX2 Devkit


3.3.6 TX2 NX(p3509-0000 carrier board)

use the same carrier board with XAVIER NX Devkit




3.3.8 XAVIER NX Devkit


Specially, For Jetpack5.x, must use this dtb:

  • Jetson Xavier NX (P3668-0000) For developer kit only:


  • Jetson Xavier NX (P3668-0001) Commercial module:


3.3.9 AGX Orin


3.3.10 Orin NX
  • Jetson Orin NX 16G(P3767-0000):


  • Jetson Orin NX 8G (P3767-0001):


3.3.11 Orin Nano
  • Jetson Orin Nano 8G(P3767-0003) and Jetson Orin Nano Devkit(P3767-0005):


  • Jetson Orin Nano 4G (P3767-0004):


3.4 DTB file name and camera module correspondence

Under the dtb directory of each motherboard, the directory corresponding to the camera model is stored, and you can usually know the corresponding camera model directly by the directory name.


1, VEYE-MIPI-CAM2M is the new version of VEYE series dtb, which supports all VEYE 2M series products, including VEYE-MIPI-327E, VEYE-MIPI-IMX327S, VEYE-MIPI-IMX462, VEYE-MIPI-IMX385.

2, The ones with fpdlink as suffix correspond to fpdlink coaxial model module.

3,MV-MIPI-MVCAM is the common dtb for all MV series and RAW series cameras, excluding RAW-MIPI-AR0234M and RAW-MIPI-IMX462M..

3.5 Upgrade directly on the jetson board

Applicable models: Jetson Nano, Xavier and Orin.

Note: AGX Xavie Jetpack version >= 4.4 , support this upgrade mode. Earlier versions have not been verified and are not recommended.

3.5.1 Check the current L4T version

First check the current L4T version and try to replace it with the same version.

cat /etc/nv_tegra_release

If it shows:

# R32 (release), REVISION: 4.3......

It means L4t Verion is 32.4.3

3.5.2 Note about L4T 32.7. 2

The Image and dts of L4T 32.7.2 are identical to those of L4T 32.7.1, so you can directly use the contents of the L4T 32.7.1 related directory.

In addition, the upgrade requires updating cboot, please refer to the FAQ section.

3.5.3 Download the bsp package to the Jetson board

On Jetson Board:


Or type in the address bar of your browser:

tar -xzvf nvidia_jetson_veye_bsp.tar.gz

3.5.4 Upgrade Image(For Jetpack4.x or MV series cameras)

Backup old version Image

cp /boot/Image /boot/Image.backup

cp /boot/Image.sig /boot/Image.sig.backup

Under the bsp package directory, find the corresponding version of the Image package, decompress it, and execute:

sudo cp <path to your Image dir>/Image /boot/Image -f

For Xavier NX Devkit

Need to use the signed file(For example,file inside Image_l4t_r32.*.*_veyecam_signed_4_xavier),copy Image and Image.sig to /boot/ dir on the Jetson Xavier board:

sudo cp <path to your Image dir>/Image* /boot/Image -f

Effective after restart.

3.5.5 install camera modules(For Jetpack5.x)

Check linux version:

uname -r

Find the corresponding directory in nvidia_jetson_veye_bsp/ko :

sudo cp nvidia_jetson_veye_bsp/ko/$(uname -r)/* /lib/modules/$(uname -r)/kernel/drivers/media/i2c/ -f

Specially,for Jetpack5.1 version:

sudo cp nvidia_jetson_veye_bsp/ko/5.10.104-tegra-l4t35.2.1/* /lib/modules/$(uname -r)/kernel/drivers/media/i2c/ -f

Specially,for Jetpack5.1.1 version:

sudo cp nvidia_jetson_veye_bsp/ko/5.10.104-tegra-l4t35.3.1/* /lib/modules/$(uname -r)/kernel/drivers/media/i2c/ -f General

Register the modules to the system by executing the following command.

sudo depmod Special

If using a camera module with fpdlink interface. You must manually control the loading order to ensure that ds90ub954.ko is loaded before the camera driver is loaded.

After the system boots, manually insert the drivers in order, e.g.

sudo insmod ds90ub954.ko

sudo insmod cs_imx307.ko

The command to load the driver can be added to the startup script.

3.5.6 Upgrade dtb

Under the bsp package directory, find the dtb file corresponding to your camera module model and L4T version number.

sudo mkdir /boot/veyecam/

sudo cp <path to your dtb dir>/<DTB file name> /boot/veyecam/ -f

Backup extlinux.conf file first

cp /boot/extlinux/extlinux.conf / boot/extlinux/extlinux.conf.back

Then, edit the /boot/extlinux/extlinux.conf file and add the following line.

FDT /boot/veyecam/<DTB file name>

Note: <DTB file name> should be replaced with the corresponding dtb name of the mainboard, ensure that the file specified in the FDT line actually exists correctly.

Effective after restart.

3.6 Upgrade Jetson Board using Host PC

This section provides the second method of upgrading the system.

This method has the same goal as the method in the previous section, and one of the two can be chosen.

This method is complicated and not recommended for Nano, Xavier, Orin.

Specifically, for TX2 systems, only the methods in this section can be taken to upgrade.

3.6.1 Burn the standard Image

Note: if your Jetson board has correctly burned the standard version Image, you can skip this step.

You can burn the standard Image using SDK Manager or following the steps below.

  • Set PATH

Assume SDK install directory is <TOPDIR>.

export TOP_DIR=<absolute path to top dir accroding to your jetpack version and board name;for example /home/xumm/nvidia/nvidia_sdk/JetPack_4.5_Linux_JETSON_XAVIER_NX_DEVKIT/>

export L4T_DIR=$TOP_DIR/Linux_for_Tegra

  • Build default image, flashing to Jetson Board, prepare L4T environment

cd $L4T_DIR

sudo ./  

- Nano

sudo ./ jetson-nano-devkit mmcblk0p1

sudo ./ jetson-nano-2gb-devkit mmcblk0p1

- TX2

sudo ./ jetson-tx2 mmcblk0p1

- TX2 NX(p3509-0000 carrier board)

sudo ./ jetson-xavier-nx-devkit-tx2-nx mmcblk0p1

- AGX Xavier

sudo ./ jetson-xavier mmcblk0p1

- Xavier NX Devkit

sudo ./ jetson-xavier-nx-devkit mmcblk0p1

3.6.2 Download our bsp package for Jetson

cd $L4T_DIR


tar -xzvf nvidia_jetson_veye_bsp.tar.gz

export RELEASE_PACK_DIR=$L4T_DIR/nvidia_jetson_veye_bsp

3.6.3 Upgrade Image and DTB

Extract the downloaded `nvidia_jetson_veye_bsp.tar.gz`, and locate the Image corresponding to the specific version.

  • Installing the Kernel

Whether you use a prebuild kernel or you build it yourself

- Nano and TX2

copy Image to /boot/ dir on the Jetson Nano or TX2 board:

sudo cp <path to your Image dir>/Image /boot/Image -f

- AGX Xavier and Xavier NX Devkit

Need to use the signed file(For example,file inside Image_l4t_r32.*.*_veyecam_signed_4_xavier),copy Image and Image.sig to /boot/ dir on the Jetson Xavier board:

sudo cp <path to your Image dir>/Image /boot/Image -f

sudo cp <path to your Image dir>/Image.sig /boot/Image -f

on the Host PC:

cd $L4T_DIR

sudo ./ -k kernel jetson-xavier mmcblk0p1

- Xavier NX

on the Host PC:

cd $L4T_DIR

sudo ./ -k kernel jetson-xavier-nx-devkit mmcblk0p1

  • Flashing dtb file

Enter the recovery mode,and on the Host PC:

cp <path to your dtb dir>/dtbfilename $L4T_DIR/kernel/dtb/ -f

cd $L4T_DIR

- Nano

sudo ./ -r -k DTB jetson-nano-qspi-sd mmcblk0p1

sudo ./ -r -k DTB jetson-nano-devkit mmcblk0p1

sudo ./ -r -k DTB jetson-nano-2gb-devkit mmcblk0p1

- TX2

sudo ./ -r -k kernel-dtb jetson-tx2 mmcblk0p1

- TX2 NX(p3509-0000 carrier board)

sudo ./ -r -k kernel-dtb jetson-xavier-nx-devkit-tx2-nx mmcblk0p1

- AGX Xavier

sudo ./ -r -k kernel-dtb jetson-xavier mmcblk0p1

- Xavier NX

sudo ./ -r -k kernel-dtb jetson-xavier-nx-devkit mmcblk0p1

Reset Jetson Board after flashing.

3.7 Are Image and DTB upgrade successful ?

3.7.1 For DTB

DTB varies from platform and from camera module.

- Nano A02/ Nano 2G

ls /proc/device-tree/host1x/i2c@546c0000/

- Nano B01

ls /proc/device-tree/cam_i2cmux/i2c@*

- TX2 Devkit

ls /proc/device-tree/i2c@3180000/tca9548@70/i2c@*


ls /proc/device-tree/i2c@3180000/tca9548@77/i2c@*

- AGX Xavier/AGX Orin

ls /proc/device-tree/i2c@3180000/tca9548@70/i2c@*


ls /proc/device-tree/i2c@3180000/tca9548@77/i2c@*

- Xavier NX and TX2 NX(p3509-0000 carrier board)

ls /proc/device-tree/cam_i2cmux/i2c@*

You should be able to find the camera model you used.

3.7.2 For Image

ls /sys/bus/i2c/drivers/

When installing the camera correctly, the relevant directory for the camera should exist, such as veyecam csx307 cssc132 mvcam, etc.

3.8 Protection against being overwritten by upgrades

After making sure Image and dtb are successfully updated, please execute the following command to prevent kernel and dtb from being overwritten by update.

sudo apt-mark hold nvidia-l4t-kernel nvidia-l4t-kernel-dtbs

3.9 Build the drivers from source

Please refer to: Nvidia Jetson platform VEYE camera driver source code compilation guide.

Could be used for Flashing or Upgrading.

4 Applications and Test

4.1 Check system status

Run the following command to confirm whether the camera is probed.


dmesg | grep veye  

The output message appears as shown below:

camera id is veyecam

sensor is IMX327/IMX462/IMX385

subdev veyecam [i2c_bus]-003b bound

  • For CS-MIPI-IMX307

dmesg | grep csx307  

The output message appears as shown below.:

Detected CS307 sensor

subdev csx307 [i2c_bus]-003b bound

  • For CS-MIPI-SC132

dmesg | grep cssc132  

The output message appears as shown below.:

subdev cssc132 [i2c_bus]-003b bound

  • For VEYE-MIPI-IMX335

dmesg | grep imx335

The output message appears as shown below.:

camera id is VEYE-MIPI-IMX335

subdev veye_imx335 [i2c_bus]-003b bound

  • Run the following command to check the presence of video node.

ls /dev/video*

The output message appears as shown below.


  • For VEYE-MIPI-327(using VEYE-MIPI-327 dtb)

dmesg | grep veye327  

The output message appears as shown below:

Detected VEYE327 sensor

subdev veye327 [i2c_bus]-003b bound

The [i2c_bus] in the driver prompt message indicates the i2c bus corresponding to this camera.

4.2 Video Stream Toolkits Manual

The camera appears as /dev/videoX device node,where X is between [0-5].

During the Linux boot process, the cameras are detected in the order of i2c bus from smallest to largest. For example, if only one camera is connected, X is 0 regardless of the hardware connection to the location. If 5 cameras are connected, X is reflected as [0-4] according to i2c bus from smallest to largest.

In gstreamer command ,v4l2src and nvv4l2camerasrc has a param device=/dev/videoX to identify which camera to use.

4.2.1 Gstreamer Usage

export DISPLAY=:0

  • Preview FHD

gst-launch-1.0 nvv4l2camerasrc device=/dev/video0 ! "video/x-raw(memory:NVMM),format=(string)UYVY, width=(int)1920, height=(int)1080" ! nvvidconv ! "video/x-raw(memory:NVMM),format=(string)I420" ! nv3dsink sync=false

gst-launch-1.0 nvv4l2camerasrc device=/dev/video0 ! "video/x-raw(memory:NVMM),format=(string)UYVY, width=(int)1920, height=(int)1080" ! nvvidconv ! "video/x-raw(memory:NVMM),format=(string)NV12" ! nv3dsink sync=false

  • Preview FHD(using xvimagesink sink if supported)

export DISPLAY=:0

gst-launch-1.0 -e v4l2src io-mode=4 device=/dev/video0 do-timestamp=true ! 'video/x-raw, width=1920, height=1080, framerate=30/1, format=UYVY' ! xvimagesink sync=false

  • Preview 720p@60 (CS-MIPI-IMX307)

gst-launch-1.0 nvv4l2camerasrc ! "video/x-raw(memory:NVMM),format=(string)UYVY, width=(int)1280, height=(int)720, framerate=(fraction)60/1" ! nvvidconv ! "video/x-raw(memory:NVMM),format=(string)I420" ! nv3dsink sync=false

  • Preview 1280*1080@45 (CS-MIPI-SC132)

gst-launch-1.0 nvv4l2camerasrc ! "video/x-raw(memory:NVMM),format=(string)UYVY, width=(int)1280, height=(int)1080, framerate=(fraction)45/1" ! nvvidconv ! "video/x-raw(memory:NVMM),format=(string)I420" ! nv3dsink sync=false

  • Preview 640*480p@130 (CS-MIPI-IMX307)

gst-launch-1.0 nvv4l2camerasrc ! "video/x-raw(memory:NVMM),format=(string)UYVY, width=(int)640, height=(int)480, framerate=(fraction)130/1" ! nvvidconv ! "video/x-raw(memory:NVMM),format=(string)I420" ! nv3dsink sync=false

  • Preview 2 cameras 1080p HD



CAPS="video/x-raw(memory:NVMM),format=(string)UYVY, width=1920, height=1080"

gst-launch-1.0 nvcompositor name=comp sink_0::xpos=0 sink_0::ypos=0 sink_0::width=$WIDTH sink_0::height=$HEIGHT sink_1::xpos=$WIDTH sink_1::ypos=0 sink_1::width=$WIDTH sink_1::height=$HEIGHT ! nv3dsink nvv4l2camerasrc device=/dev/video0 ! $CAPS ! nvvidconv ! "video/x-raw(memory:NVMM),format=(string)I420"! comp. nvv4l2camerasrc device=/dev/video1 ! $CAPS ! nvvidconv ! "video/x-raw(memory:NVMM),format=(string)I420"! comp.

  • Record FHD in H.264 format to a video file

gst-launch-1.0 nvv4l2camerasrc num-buffers=300 ! "video/x-raw(memory:NVMM),format=(string)UYVY, width=(int)1920, height=(int)1080" ! nvvidconv ! "video/x-raw(memory:NVMM),format=(string)NV12" ! nvv4l2h264enc control-rate=1 bitrate=10000000 ! h264parse ! qtmux ! filesink location=filename.mp4 -e

  • Playback of saved video file

gst-launch-1.0 filesrc location=filename.mp4 ! qtdemux ! queue ! h264parse ! nvv4l2decoder ! nvoverlaysink -e

  • Capturing FHD still image  

gst-launch-1.0 v4l2src num-buffers=1 ! "video/x-raw,format=(string)UYVY, width=(int)1920, height=(int)1080" ! nvvidconv ! "video/x-raw(memory:NVMM),format=(string)I420" ! nvjpegenc ! filesink

4.2.2 VEYE-MIPI-IMX335 gstreamer example

Since VEYE-MIPI-IMX335 supports only a few specific resolution modes, its driver we use use_sensor_mode_id mode.

./ video mode v4l2-ctl sensor_mode video format
1 0 2592x1944@20fps
2 1 2592x1944@12.5fps
3 2 2560x1440@25fps
4 3 2560x1440@30fps
  • prepare

sudo apt-get install v4l-utils

Refer to the following section and download the tool.

  • 2592x1944@20fps mode preview, framerate statistics

v4l2-ctl -d /dev/video0 --set-ctrl sensor_mode=0

./ -w -f videomode -p1 1 -b [busnum]

v4l2-ctl -d /dev/video0 --set-ctrl preferred_stride=5376


gst-launch-1.0 nvv4l2camerasrc device=/dev/video0 ! "video/x-raw(memory:NVMM), width=(int)2592, height=(int)1944" ! nvvidconv ! "video/x-raw(memory:NVMM),format=(string)I420" ! nv3dsink sync=false

Framerate statistics

gst-launch-1.0 nvv4l2camerasrc device=/dev/video0 ! "video/x-raw(memory:NVMM),format=(string)UYVY,width=(int)2592,height=(int)1944" ! nvvidconv ! "video/x-raw(memory:NVMM),format=(string)I420" ! fpsdisplaysink video-sink=fakesink -v

  • 2560x1440@30fps mode video encode and capture

v4l2-ctl -d /dev/video0 --set-ctrl sensor_mode=3

./ -w -f videomode -p1 4 -b [busnum]

v4l2-ctl -d /dev/video0 --set-ctrl preferred_stride=5120

Video encode

gst-launch-1.0 nvv4l2camerasrc num-buffers=300 ! "video/x-raw(memory:NVMM),format=(string)UYVY, width=(int)2560, height=(int)1440" ! nvvidconv ! "video/x-raw(memory:NVMM),format=(string)NV12" ! nvv4l2h264enc control-rate=0 bitrate=10000000 ! h264parse ! qtmux ! filesink location=filename.mp4 -e

Video Replay

gst-launch-1.0 filesrc location=filename.mp4 ! qtdemux ! queue ! h264parse ! nvv4l2decoder ! nv3dsink -e


gst-launch-1.0 v4l2src num-buffers=1 ! "video/x-raw,format=(string)UYVY, width=(int)2560, height=(int)1440" ! nvvidconv ! "video/x-raw(memory:NVMM),format=(string)I420" ! nvjpegenc ! filesink location=jpgname.jpg

4.2.3 Jetson multimedia-api samples

The Jetson Linux API is available on the Jetson platform for developers to use. Please refer to the official nVidia documentation for the installation of the jetson_multimedia_api package.

For VEYE and CS series cameras, the ISP function is already integrated in the camera, so you cannot use libargus to get data, but can directly use the standard V4L2 interface to get data from the /dev/videoX device file.

The following two samples can be run directly. 12_camera_v4l2_cuda

./camera_v4l2_cuda -d /dev/video0 -s 1920x1080 -f UYVY v4l2cuda

./capture-cuda -d /dev/video0 -f UYVY -m -o out.ppm -s 1920x1080 -c 1

4.2.4 v4l2-ctl Application Examples install v4l2-utils

sudo apt-get install v4l-utils Configure parameters using v4l2-ctl
  • List the data formats supported by the camera

v4l2-ctl -d /dev/video0 --list-formats-ext

  • Frame rate statistics

v4l2-ctl -d /dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat=UYVY--stream-mmap --stream-count=-1 --stream-to=/dev/null

  • Save image to file

v4l2-ctl -d /dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat=UYVY --stream-mmap --stream-count=1 --stream-to=uyvy-1920x1080.yuv

4.2.5 yavta install yavta

git clone

cd yavta;make Save image to file

./yavta -c1 -FUYVY-1920x1080.yuv --skip 0 -f UYVY -s 1920x1080 /dev/video0

4.2.6 Opencv

To import camera data from v4l2 devices to opencv, we provide several samples.

We provide 2 samples here.

4.3 Using i2c script to modify camera parameters


Video Control Toolkits Manual :VEYE-MIPI-327 I2C


Video Control Toolkits Manual :CS-MIPI-X I2C


Video Control Toolkits Manual :VEYE-MIPI-IMX335 I2C

5 How to port the driver to a third party board

5.1 driver porting

For Image, we have added functionality to the official standard Image and have not made any deletions. In general, you can use our compiled Image directly. for special cases, please refer to the source code for integration.

For modules it is even easier to just use them. Compiling from source code and is very simple, so I won't go into details here.

5.2 dts porting

We only provide dtb for some boards of Nano, TX2, Xavier, Orin. For the types not provided, it is necessary to:

1. get the dts source code of that board.

2. put our camera related dts to the whole.

3. recompile to get the dtb of the corresponding board.

The operation steps are not complicated, but there are some third-party base board manufacturers do not open dts source code. This will require the cooperation of all parties to do so.

6 FAQ and bug list

6.1 Problem of system update not taking effect on a system with an SSD hard drive

If an SSD hard drive is installed in a system and mounted on the / directory, it may cause regular system update operations (Image, ko, dtb) to be completely ineffective.

The reason for this is that the board comes with an eMMC storage device, and the Image, ko, and dtb that take effect during the boot stage are stored in the eMMC.

After the boot is completed, if the SSD hard drive is mounted on the / directory, it may cause the files stored on the eMMC to be inaccessible.

The solution in this case is to manually mount the mmcblk0p1 partition of the eMMC to a specific directory, and perform all system update operations based on this directory.

6.2 VEYE cameras on Jetpack5.x

Jetpack5.x has more stringent requirements for mipi signals in xavier and orin platforms. VEYE-MIPI-xxx series cameras need firmware hdver>=7 to be perfectly supported.

6.3 CS-MIPI-IMX307 combined with Orin nano and Orin NX Green Screen

When CS-MIPI-IMX307 is powered by the 3.3V mode of the FFC cable, the MIPI receiver state machine of Orin nano and Orin NX (Jetpack5.1.1) will enter an incorrect state.

It is recommended to refer to this article and modify the power supply mode of CS-MIPI-IMX307 to use the 5V power supply mode.

6.4 Jetpack5.0.1 DP

This version has many bugs, such as not supporting nvv4l2camerasrc, not recommended to use.

6.5 nv3dsink

Jetpack 5.x no longer supports nvoverlaysink, use nv3dsink instead.

6.6 cboot of L4T32.7.2 on Xavier

For the Xavier series, there is a bug in the cboot of L4T32.7.2 that must be fixed before the upgrade can be done.

[Cboot] Cboot in 32.7.2 fails to read extlinux.conf

We compiled the correct version of cboot and put it here.

After downloading, put it in Linux_for_Tegra/bootloader directory and execute the following command on PC to burn cboot.

  • AGX Xavier

sudo ./ -r -k cpu-bootloader jetson-xavier mmcblk0p1

  • Xavier NX

sudo ./ -r -k cpu-bootloader jetson-xavier-nx-devkit mmcblk0p1

7 Document History

  • 20230427

Add support for Jetpack5.1.1.

  • 20230222

Add support for Jetpack5.1.

  • 20220831

Improve the description of VEYE series and MV series under Jetpack 5.0.2.

  • 20220824

Add support for Jetpack5.0.2.

  • 20220720

Add multimedia-api samples and v4l2 samples.

  • 20220714

Add L4T32.7.2 Note。

  • 20220629

Add support for Jetpack 5.0.1DP and tune through AGX-Orin.

  • 20220110

Add VEYE-MIPI-IMX385 support.

  • 20220105

Use nvv4l2h264enc instead of omxh264enc in gstreamer command,because omxh264enc has been deprecated.

  • 20211025

Use nvcamerasrc instead of v4l2src in gstreamer command , and the data goes directly into DMA memory.

8 References

Jetson start up:

Jetson Download Center:

Xavier NX:

TX2 development kit:

SDK Manager:

L4T Doc:

TX2 user guide: link