2,021
edits
Changes
Jump to navigation
Jump to search
Line 4:
Line 4: − + Line 16:
Line 16: + + + + + + + Line 56:
Line 63: + + Line 65:
Line 74: + + + + + + Line 79:
Line 94: − + Line 86:
Line 101: − + + Line 102:
Line 118: − + + + + + + + Line 124:
Line 146: − + − − + + Line 141:
Line 163: + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 151:
Line 201: + + Line 171:
Line 223: − ====== bug 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. − − [https://elinux.org/Jetson/L4T/r32.7.x_patches <nowiki>[Cboot] Cboot in 32.7.2 fails to read extlinux.conf</nowiki>] − − We compiled the correct version of cboot and put it [https://github.com/veyeimaging/nvidia_jetson_veye_bsp/tree/master/cboot_l4t_32.7.2 here]. − − After downloading, put it in Linux_for_Tegra/bootloader directory and execute the following command on PC to burn cboot. − − *AGX Xavier − − <code>sudo ./flash.sh -r -k cpu-bootloader jetson-xavier mmcblk0p1</code> − − *Xavier NX − − <code>sudo ./flash.sh -r -k cpu-bootloader jetson-xavier-nx-devkit mmcblk0p1</code> − + − + − + − + Line 210:
Line 247: − + − − <code>sudo cp <path to your Image dir>/Image.sig /boot/Image.sig -f</code> Line 224:
Line 259: + + + + + + + + + + + + + + + + + + + + + + Line 236:
Line 293: − + Line 250:
Line 307: + + Line 296:
Line 355: − + − + − prebuilt Image on github:https://github.com/veyeimaging/nvidia_jetson_veye_bsp/tree/master/kernel_image+ Line 371:
Line 430: − − =====For Image===== − <code>ls /sys/bus/i2c/drivers/</code> − − There should have veye327 veyecam csx307 cssc132 directory. Line 409:
Line 463: + + + + Line 414:
Line 472: − + Line 486:
Line 544: − + + − + − + − + Line 503:
Line 562: − + − + − + Line 521:
Line 580: − + Line 533:
Line 592: − + Line 576:
Line 635: − + Line 596:
Line 655: − + − − ===== gstreamer examples on Jetpack5.x ===== − On Jetpack5.x： − − # nvoverlaysink is obsolete, nv3dsink can be used instead. − # There are still bugs in nvv4l2camerasrc, use v4l2src for now. − − *Preview 1080p HD − − <code>gst-launch-1.0 v4l2src device=/dev/video0 ! "video/x-raw,format=(string)UYVY,width=(int)1920, height=(int)1080" ! nvvidconv ! "video/x-raw(memory:NVMM),format=(string)NV12" ! nv3dsink -e</code> − − * Video Encode1080p HD − − <code>gst-launch-1.0 v4l2src num-buffers=300 ! "video/x-raw,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</code> − − *Capture − − <code>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 location=jpgname.jpg</code> Line 662:
Line 703: − Opencv appsink cannot read from NVMM memory. You would use nvvidconv for copying into standard CPU memory.+ − + Line 681:
Line 722: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
→Overview
===Overview===
===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
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.2.2,L4T r32.2.1
* Jetpack4.6.1, L4T r32.7.1
* Jetpack4.6.1, L4T r32.7.1
*Jetpack4.6.2,L4T r32.7.2
*Jetpack4.6.2,L4T r32.7.2
*Jetpack4.6.3,L4T r32.7.3
*Jetpack4.6.4,L4T r32.7.4
*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!'''
We provide two ways to do so: '''Prebuilt Binaries''' or '''Source Code. Yes, It's Open Source!'''
|}
|}
====How to check the current L4T version====
====How to check the current L4T version====
===== Method 1 =====
On Jetson board
On Jetson board
It means L4t Version is 32.4.3
It means L4t Version is 32.4.3
===== Method 2 =====
Refer to this [https://pypi.org/project/jetson-stats/ link] to install jetson-stats:
<code>jtop</code>
===Hardware Setup===
===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.
We have designed a 6cam interposer board for TX2 devkit,Xavier and Orin, It support up to 6 cameras at the same time.
<br />
<br />
[[File:ADP-N1-V2.0 XAVIER 6CAM.jpg|link=http://wiki.veye.cc/index.php/File:ADP-N1-V2.0%20XAVIER%206CAM.jpg|alt=Connect VEYE cameras to AGX Xavier|center|thumb|800x800px|Connect VEYE cameras to AGX Xavier]]
[[File:ADP-N1-V2.0 XAVIER 6CAM.jpg|link=http://wiki.veye.cc/index.php/File:ADP-N1-V2.0%20XAVIER%206CAM.jpg|alt=Connect VEYE cameras to AGX Xavier|center|thumb|800x800px|Connect VEYE cameras to AGX Xavier]]
<br />'''Be sure to screw the ADP adapter board to the bottom board.'''
<br />'''Be sure to screw the ADP adapter board to the bottom board to ensure that the adapter plate is installed flat.'''
====NVIDIA Nano ，TX2 NX and Xavier NX Devkit====
====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:
The Xavier NX interface is compatible with raspberry pi and Jetson Nano. The connection mode is shown in figure:
[[File:Xavier NX connection with CS-MIPI-IMX307.jpg|alt=Xavier NX connection with CS-MIPI-IMX307|center|thumb|800x800px|Xavier NX connection with CS-MIPI-IMX307]]
[[File:Xavier NX connection with CS-MIPI-IMX307.jpg|alt=Xavier NX connection with CS-MIPI-IMX307|center|thumb|800x800px|Xavier NX connection with CS-MIPI-IMX307]]
[[File:Jetson nano to Veye327.jpg|link=http://wiki.veye.cc/index.php/File:Jetson%20nano%20to%20Veye327.jpg|alt=Jetson Nano A02 与VEYE模组连接|center|thumb|800x800px|VEYE327 connection with Jetson Nano A02]]
[[File:Jetson nano to Veye327.jpg|link=http://wiki.veye.cc/index.php/File:Jetson%20nano%20to%20Veye327.jpg|alt=Jetson Nano A02 与VEYE模组连接|center|thumb|800x800px|VEYE327 connection with Jetson Nano A02]]
[[File:VEYE camera connection with Orin Nano and Orin NX.jpg|center|thumb|800x800px|VEYE camera connection with Orin Nano and Orin NX]]
<br />
===Upgrade Jetson Nano, TX2,Xavier and Orin system===
===Upgrade Jetson Nano, TX2,Xavier and Orin system===
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 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.
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.
====BSP package introduction====
====BSP package introduction====
=====Nano A02=====
=====Nano A02=====
<code>tegra210-p3448-0000-p3449-0000-a02.dtb</code>
<code>tegra210-p3448-0000-p3449-0000-a02.dtb</code>
=====Nano B01 Devkit=====
===== Nano B01 =====
<code>tegra210-p3448-0000-p3449-0000-b00.dtb</code>
<code>tegra210-p3448-0000-p3449-0000-b00.dtb</code>
=====Nano B01 4G emmc=====
<code>tegra210-p3448-0002-p3449-0000-b00.dtb</code>
===== Nano 2GB =====
===== Nano 2GB =====
<code>tegra210-p3448-0003-p3542-0000.dtb</code>
<code>tegra210-p3448-0003-p3542-0000.dtb</code>
=====XAVIER NX Devkit=====
=====XAVIER NX Devkit=====
<code>tegra194-p3668-all-p3509-0000.dtb</code>
<code>tegra194-p3668-all-p3509-0000.dtb</code>
Specially, For Jetpack5.x, must use this dtb：
* Jetson Xavier NX (P3668-0000) For developer kit only:
<code>tegra194-p3668-0000-p3509-0000.dtb</code>
* Jetson Xavier NX (P3668-0001) Commercial module:
<code>tegra194-p3668-0001-p3509-0000.dtb</code>
=====AGX Orin=====
=====AGX Orin=====
<code>tegra234-p3701-0000-p3737-0000.dtb</code>
<code>tegra234-p3701-0000-p3737-0000.dtb</code>
===== Orin NX=====
*Jetson Orin NX 16G(P3767-0000):
<code>tegra234-p3767-0000-p3768-0000-a0.dtb</code>
*Jetson Orin NX 8G (P3767-0001):
<code>tegra234-p3767-0001-p3768-0000-a0.dtb</code>
===== Orin Nano=====
*Jetson Orin Nano 8G(P3767-0003) and Jetson Orin Nano Devkit(P3767-0005):
<code>tegra234-p3767-0003-p3768-0000-a0.dtb</code>
*Jetson Orin Nano 4G (P3767-0004):
<code>tegra234-p3767-0004-p3768-0000-a0.dtb</code>
==== DTB file name and camera module correspondence ====
==== 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.
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.
2, The ones with fpdlink as suffix correspond to fpdlink coaxial model module.
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..
====Upgrade directly on the jetson board====
====Upgrade directly on the jetson board====
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.
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.
=====Download the bsp package to the Jetson board=====
=====Download the bsp package to the Jetson board=====
On Jetson Board:
On Jetson Board:
<code>wget <nowiki>https://github.com/veyeimaging/nvidia_jetson_veye_bsp/releases/latest/download/nvidia_jetson_veye_bsp.tgz</nowiki></code>
<code>wget <nowiki>https://github.com/veyeimaging/nvidia_jetson_veye_bsp/releases/latest/download/nvidia_jetson_veye_bsp.tar.gz</nowiki></code>
Or type in the address bar of your browser：<code><nowiki>https://github.com/veyeimaging/nvidia_jetson_veye_bsp/releases/latest/download/nvidia_jetson_veye_bsp.tgz</nowiki></code>
Or type in the address bar of your browser：<code><nowiki>https://github.com/veyeimaging/nvidia_jetson_veye_bsp/releases/latest/download/nvidia_jetson_veye_bsp.tar.gz</nowiki></code>
<code>tar -xzvf nvidia_jetson_veye_bsp.tgz</code>
<code>tar -xzvf nvidia_jetson_veye_bsp.tar.gz</code>
=====Upgrade Image(For Jetpack4.x)=====
=====Upgrade Image(For Jetpack4.x or MV series cameras)=====
Backup old version Image
Backup old version Image
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:
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:
<code>sudo cp <path to your Image dir>/Image /boot/Image -f</code>
<code>sudo cp <path to your Image dir>/Image* /boot/Image -f</code>
Effective after restart.
Effective after restart.
<code>sudo cp nvidia_jetson_veye_bsp/ko/$(uname -r)/* /lib/modules/$(uname -r)/kernel/drivers/media/i2c/ -f</code>
<code>sudo cp nvidia_jetson_veye_bsp/ko/$(uname -r)/* /lib/modules/$(uname -r)/kernel/drivers/media/i2c/ -f</code>
'''Specially，for Jetpack5.1 version''':
<code>sudo cp nvidia_jetson_veye_bsp/ko/5.10.104-tegra-l4t35.2.1/* /lib/modules/$(uname -r)/kernel/drivers/media/i2c/ -f</code>
'''Specially，for Jetpack5.1.1 version''':
<code>sudo cp nvidia_jetson_veye_bsp/ko/5.10.104-tegra-l4t35.3.1/* /lib/modules/$(uname -r)/kernel/drivers/media/i2c/ -f</code>
====== General ======
Register the modules to the system by executing the following command.
<code>sudo depmod</code>
<code>sudo depmod</code>
====== 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.
<code>sudo insmod ds90ub954.ko</code>
<code>sudo insmod cs_imx307.ko</code>
The command to load the driver can be added to the startup script.
=====Upgrade dtb=====
=====Upgrade dtb=====
Backup extlinux.conf file first
Backup extlinux.conf file first
<code>cp /boot/extlinux/extlinux.conf / boot/extlinux/extlinux.conf .back</code>
<code>cp /boot/extlinux/extlinux.conf / boot/extlinux/extlinux.conf.back</code>
Then, edit the ''/boot/extlinux/extlinux.conf'' file and add the following line.
Then, edit the ''/boot/extlinux/extlinux.conf'' file and add the following line.
This method has the same goal as the method in the previous section, and one of the two can be chosen.
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.
Specifically, for TX2 systems, only the methods in this section can be taken to upgrade.
<code>cd $L4T_DIR</code>
<code>cd $L4T_DIR</code>
<code>wget <nowiki>https://github.com/veyeimaging/nvidia_jetson_veye_bsp/releases/latest/download/nvidia_jetson_veye_bsp.tgz</nowiki></code>
<code>wget <nowiki>https://github.com/veyeimaging/nvidia_jetson_veye_bsp/releases/latest/download/nvidia_jetson_veye_bsp.tar.gz</nowiki></code>
<code>tar -xzvf nvidia_jetson_veye_bsp.tgz</code>
<code>tar -xzvf nvidia_jetson_veye_bsp.tar.gz</code>
<code>export RELEASE_PACK_DIR=$L4T_DIR/nvidia_jetson_veye_bsp</code>
<code>export RELEASE_PACK_DIR=$L4T_DIR/nvidia_jetson_veye_bsp</code>
=====Upgrade Image and DTB=====
=====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
*Installing the Kernel
====Are Image and DTB upgrade successful ?====
====Are Image and DTB upgrade successful ?====
=====For DTB=====
=====For DTB=====
DTB varies from platform and from camera module.
DTB varies from platform and from camera module.
You should be able to find the camera model you used.
You should be able to find the camera model you used.
=====For Image=====
<code>ls /sys/bus/i2c/drivers/</code>
When installing the camera correctly, the relevant directory for the camera should exist, such as veyecam csx307 cssc132 mvcam, etc.
==== Protection against being overwritten by upgrades ====
==== 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.
After making sure Image and dtb are successfully updated, please execute the following command to prevent kernel and dtb from being overwritten by update.
<code>sudo apt-mark hold nvidia-l4t-kernel nvidia-l4t-kernel-dtbs</code>
<code>sudo apt-mark hold nvidia-l4t-kernel nvidia-l4t-kernel-dtbs</code>
====Build the drivers from source====
====Build the drivers from source====
Please refer to: [[VEYE CS Camera source for Jetson|Nvidia Jetson platform VEYE and CS series camera driver source code compilation guide]].
Please refer to: [[VEYE CS Camera source for Jetson|Nvidia Jetson platform VEYE camera driver source code compilation guide]].
Could be used for Flashing or Upgrading.
Could be used for Flashing or Upgrading.
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.
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 has a param device=/dev/videoX to identify which camera to use.
In gstreamer command ，v4l2src and nvv4l2camerasrc has a param device=/dev/videoX to identify which camera to use.
=====Gstreamer Usage=====
=====Gstreamer Usage=====
<code>export DISPLAY=:0</code>
*Preview FHD
*Preview FHD
<code>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" ! nvoverlaysink sync=false</code>
<code>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</code>
<code>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" ! nvoverlaysink sync=false</code>
<code>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</code>
* Preview FHD(using xvimagesink sink)
* Preview FHD(using xvimagesink sink if supported)
<code>export DISPLAY=:0</code>
<code>export DISPLAY=:0</code>
*Preview 720p@60 (CS-MIPI-IMX307)
*Preview 720p@60 (CS-MIPI-IMX307)
<code>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" ! nvoverlaysink sync=false</code>
<code>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</code>
*Preview 1280*1080@45 (CS-MIPI-SC132)
*Preview 1280*1080@45 (CS-MIPI-SC132)
<code>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" ! nvoverlaysink sync=false</code>
<code>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</code>
*Preview 640*480p@130 (CS-MIPI-IMX307)
*Preview 640*480p@130 (CS-MIPI-IMX307)
<code>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" ! nvoverlaysink sync=false</code>
<code>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</code>
*Preview 2 cameras 1080p HD
*Preview 2 cameras 1080p HD
<code>CAPS="video/x-raw(memory:NVMM),format=(string)UYVY, width=1920, height=1080"</code>
<code>CAPS="video/x-raw(memory:NVMM),format=(string)UYVY, width=1920, height=1080"</code>
<code>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 ! nvoverlaysink 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.</code>
<code>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.</code>
*Record FHD in H.264 format to a video file
*Record FHD in H.264 format to a video file
*Capturing FHD still image
*Capturing FHD still image
<code>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 location=jpgname.jpg</code>
<code>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 location=jpgname.jp</code>
===== VEYE-MIPI-IMX335 gstreamer example =====
===== VEYE-MIPI-IMX335 gstreamer example =====
Preview
Preview
<code>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" ! nvoverlaysink sync=false</code>
<code>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</code>
Framerate statistics
Framerate statistics
Video Replay
Video Replay
<code>gst-launch-1.0 filesrc location=filename.mp4 ! qtdemux ! queue ! h264parse ! nvv4l2decoder ! nvoverlaysink -e</code>
<code>gst-launch-1.0 filesrc location=filename.mp4 ! qtdemux ! queue ! h264parse ! nvv4l2decoder ! nv3dsink -e</code>
Capture
Capture
<code>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</code>
<code>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</code>
===== Jetson multimedia-api samples =====
===== Jetson multimedia-api samples =====
===== Opencv =====
===== Opencv =====
To import camera data from v4l2 devices to opencv, we provide several samples.
We provide 2 samples [https://github.com/veyeimaging/nvidia_jetson_veye_bsp/tree/master/samples/opencv here].
We provide 2 samples [https://github.com/veyeimaging/nvidia_jetson_veye_bsp/tree/master/samples/opencv here].
====Video Control Toolkits Manual====
====Using i2c script to modify camera parameters====
*VEYE-MIPI-CAM2M Series（VEYE-MIPI-327、VEYE-MIPI-IMX327S、VEYE-MIPI-IMX462、VEYE-MIPI-IMX385）
*VEYE-MIPI-CAM2M Series（VEYE-MIPI-327、VEYE-MIPI-IMX327S、VEYE-MIPI-IMX462、VEYE-MIPI-IMX385）
===How to port the driver to a third party board===
===How to port the driver to a third party board===
==== 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.
==== 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.
=== FAQ and bug list ===
==== 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.
==== 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.
==== 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 [[Power supply mode switching|article]] and modify the power supply mode of CS-MIPI-IMX307 to use the 5V power supply mode.
==== Jetpack5.0.1 DP ====
This version has many bugs, such as not supporting nvv4l2camerasrc, not recommended to use.
==== nv3dsink ====
Jetpack 5.x no longer supports nvoverlaysink, use nv3dsink instead.
==== 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.
[https://elinux.org/Jetson/L4T/r32.7.x_patches <nowiki>[Cboot] Cboot in 32.7.2 fails to read extlinux.conf</nowiki>]
We compiled the correct version of cboot and put it [https://github.com/veyeimaging/nvidia_jetson_veye_bsp/tree/master/cboot_l4t_32.7.2 here].
After downloading, put it in Linux_for_Tegra/bootloader directory and execute the following command on PC to burn cboot.
*AGX Xavier
<code>sudo ./flash.sh -r -k cpu-bootloader jetson-xavier mmcblk0p1</code>
*Xavier NX
<code>sudo ./flash.sh -r -k cpu-bootloader jetson-xavier-nx-devkit mmcblk0p1</code>
=== Document History ===
=== 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
* 20220720