VEYE CS Camera source for Jetson - Revision history

Xumm: /* Overview */

2024-05-22T06:55:19Z

Overview

Xumm: /* Overview */

2023-09-25T06:17:07Z

Overview

Xumm: /* Modify Kconfig and Makefile */

2023-07-20T03:41:21Z

Modify Kconfig and Makefile

Admin: /* Jetpack version VS. L4T version */

2023-03-09T12:45:35Z

Jetpack version VS. L4T version

Admin: /* Jetpack version VS. L4T version */

2023-02-22T06:34:28Z

Jetpack version VS. L4T version

Admin: /* Setting Up the Environment */

2023-02-19T03:53:37Z

Setting Up the Environment

Admin: /* Overview */

2022-08-31T08:52:32Z

Overview

Admin: /* Overview */

2022-08-24T07:32:35Z

Overview

Admin: /* Jetpack version VS. L4T version */

2022-08-24T03:51:24Z

Jetpack version VS. L4T version

Admin: /* Build modules */

2022-08-17T09:20:58Z

Build modules

@@ Line 35: / Line 35: @@
 *Jetpack5.1.1, L4T r35.3.1
 *Jetpack5.1.2, L4T r35.4.1
 ====Check the current L4T version====
@@ Line 124: / Line 125: @@
 <code>./source_sync.sh -t jetson_35.4.1</code>
 ==== Setting Up the Environment ====
 Assume SDK install directory is <TOPDIR>，source code is in $L4T_DIR/sources directory.

@@ Line 33: / Line 33: @@
 *Jetpack5.0.2, L4T r35.1
 *Jetpack5.1, L4T r35.2.1
 ====Check the current L4T version====
@@ Line 114: / Line 116: @@
 <code>./source_sync.sh -t jetson_35.2.1</code>
 ==== Setting Up the Environment ====
 Assume SDK install directory is <TOPDIR>，source code is in $L4T_DIR/sources directory.
@@ Line 256: / Line 266: @@
 <code>cp $RELEASE_PACK_DIR/Xavier-NX/JetPack_<ver>_Linux_JETSON_XAVIER_NX_DEVKIT/dts\ dtb/<camera model>/tegra194-p3509-0000-a00.dtsi $XAVIER_DTS_PATH/jakku/kernel-dts/common/</code>
 ==== build ====
@@ Line 293: / Line 312: @@
 ===== AGX Orin =====
-<code>$COMMON_DTS_PATH/tegra234-p3701-0000-p3737-0000.dtb</code><br />
+<code>$COMMON_DTS_PATH/tegra234-p3701-0000-p3737-0000.dtb</code>

@@ Line 188: / Line 188: @@
 ===== Modify Kconfig and Makefile =====
-<code>cp $RELEASE_PACK_DIR/drivers_source/cam_drv_src/Kconfig_<ver> $NVIDIA_PATH/drivers/media/i2c/</code>
+Modify the Kconfig and Makefile files under the <code>$NVIDIA_PATH/drivers/media/i2c/</code> directory to add the corresponding camera driver compilation options.
 ===== build =====

@@ Line 29: / Line 29: @@
 *Jetpack4.6.1, L4T r32.7.1
 *Jetpack4.6.2, L4T r32.7.2
 *Jetpack5.0.1DP,L4T r34.1.1
 *Jetpack5.0.2, L4T r35.1

@@ Line 31: / Line 31: @@
 *Jetpack5.0.1DP,L4T r34.1.1
 *Jetpack5.0.2, L4T r35.1
 ====Check the current L4T version====
@@ Line 109: / Line 110: @@
 <code>./source_sync.sh -t jetson_35.1</code>
 ==== Setting Up the Environment ====
 Assume SDK install directory is <TOPDIR>，source code is in $L4T_DIR/sources directory.
@@ Line 267: / Line 271: @@
 <code>cd $L4T_DIR/sources/kernel/kernel-5.10/</code>
 <code>make ARCH=arm64 O=$TEGRA_KERNEL_OUT dtbs</code>

← Older revision		Revision as of 03:53, 19 February 2023
Line 200:		Line 200:

	<code>./nvbuild.sh -o $TEGRA_KERNEL_OUT</code>		<code>./nvbuild.sh -o $TEGRA_KERNEL_OUT</code>
		+
		+	<code>nvbuild.sh</code> is only included in the <code>kernel_src.tbz2</code> tar file that is part of <code>public_sources.tbz2</code>. If the kernel sources were synced from the Git server, you need to manually copy <code>nvbuild.sh</code> from the tar file.

	==== Build completed ====		==== Build completed ====

@@ Line 1: / Line 1: @@
 [[VEYE CS Camera source for Jetson/zh|查看中文]]
-'''Nvidia Jetson platform VEYE and CS series camera driver source code compilation guide'''
+'''Nvidia Jetson platform VEYE camera driver source code compilation guide'''
 === Overview ===
@@ Line 158: / Line 158: @@
 <code>export RELEASE_PACK_DIR=$L4T_DIR/nvidia_jetson_veye_bsp</code>
-===Build kernel(Jetpack4.x)===
+===Build kernel===
-This chapter is for Jetpack4.x version.
+For Jetpack version 4.x and for using MV series cameras under Jetpack version 5.x, the kernel needs to be compiled.
 ==== kernel patch for MV series ====
@@ Line 175: / Line 175: @@
 <code>patch -p1 < [path to]veye_mv_l4t_[version].patch</code>
-==== patch code ====
+==== For Jetpack 4.x, the camera driver is compiled into the Image ====
 <code>cp $RELEASE_PACK_DIR/drivers_source/cam_drv_src/* $NVIDIA_PATH/drivers/media/i2c/</code>
@@ Line 185: / Line 187: @@
 <code>cp $RELEASE_PACK_DIR/drivers_source/cam_drv_src/Makefile_<ver> $NVIDIA_PATH/drivers/media/i2c/</code>
-==== build ====
+===== build =====
 <code>cd $L4T_DIR/sources/kernel/kernel-4.9/</code>
@@ Line 192: / Line 194: @@
 <code>make ARCH=arm64 O=$TEGRA_KERNEL_OUT Image -j4</code>
 Completed Image file is $TEGRA_KERNEL_OUT/arch/arm64/boot/Image，could be used for Flashing or Upgrading.
@@ Line 198: / Line 208: @@
 <code>sudo cp $TEGRA_KERNEL_OUT/arch/arm64/boot/Image $L4T_DIR/kernel/ -f</code>
-*For xavier，need sign the file
+*For Xavier and Orin，need sign the file
 <code>cd $L4T_DIR</code>
@@ Line 204: / Line 214: @@
 <code>./l4t_sign_image.sh --file kernel/Image --chip 0x19</code>
 ===Build modules(Jetpack5.x)===
-For version later than Jetpack 5.x, non-MV series products, can compile the driver directly as modules to get the ko file. It is recommended to compile the driver directly on  Jetson Board.
+For version later than Jetpack 5.x, can compile the driver directly as modules to get the ko file. It is recommended to compile the driver directly on  Jetson Board.
 <code>cd $RELEASE_PACK_DIR/drivers_source/cam_drv_src/</code>

@@ Line 4: / Line 4: @@
 === Overview ===
 ==== Jetpack version VS. L4T version ====
@@ Line 33: / Line 46: @@
 The following operations are done in HOST PC.
-*Cross-compiling Toolchain
+==== Cross-compiling Toolchain ====
-Please refer to this [https://docs.nvidia.com/jetson/l4t/index.html#page/Tegra%2520Linux%2520Driver%2520Package%2520Development%2520Guide%2Fxavier_toolchain.html%23wwpID0ESHA link] to install toolchain on your Host PC.
+* Jetpack5.x
-*L4T source code and Rootfs
+Please refer to this [https://docs.nvidia.com/jetson/archives/r35.1/DeveloperGuide/text/AT/JetsonLinuxToolchain.html link] to install toolchain on your Host PC.
 Please download the Linux_for_Tegra SDK via SDK Manager first.
-You could use SDK Manager or [https://developer.nvidia.com/embedded/downloads directly download] to get source code.
+You could use SDK Manager or [https://developer.nvidia.com/embedded/downloads directly download] to get source code. I recommend the direct download method.
 Sync code as this if you use SDK Manager:
@@ Line 89: / Line 105: @@
 <code>./source_sync.sh -t jetson_34.1.1</code>
-*Setting Up the Environment
+''- Jetpack5.0.2''
 Assume SDK install directory is <TOPDIR>，source code is in $L4T_DIR/sources directory.
@@ Line 102: / Line 121: @@
 <code>export ARCH=arm64</code>
 <code>export TEGRA_KERNEL_OUT=$L4T_DIR/sources/kernel/out_kernel</code>
@@ Line 118: / Line 133: @@
 <code>export XAVIER_DTS_PATH=$L4T_DIR/sources/hardware/nvidia/platform/t19x</code>
 ===Download our bsp package for Jetson===
 <code>cd $L4T_DIR</code>
@@ Line 124: / Line 158: @@
 <code>export RELEASE_PACK_DIR=$L4T_DIR/nvidia_jetson_veye_bsp</code>
-===Build kernel===
+===Build kernel(Jetpack4.x)===
 This chapter is for Jetpack4.x version.
@@ Line 169: / Line 203: @@
 <code>./l4t_sign_image.sh --file kernel/Image --chip 0x19</code>
-===Build modules===
+===Build modules(Jetpack5.x)===
 For version later than Jetpack 5.x, non-MV series products, can compile the driver directly as modules to get the ko file. It is recommended to compile the driver directly on  Jetson Board.
 <code>cd $RELEASE_PACK_DIR/drivers_source/cam_drv_src/</code>
-<code>make -f Makefile_local</code>
+<code>make -f Makefile</code>
 ===Build DTS===
 Patch code first.