菜单
Build the RealSense MIPI platform driver for NVIDIA Jetson. Use when the user wants to build the kernel/driver/DTBs for a specific JetPack version or troubleshoot build issues. Triggers on requests mentioning build, compile, make, or JetPack version numbers (4.6.1, 5.0.2, 5.1.2, 6.0, 6.1, 6.2, 6.2.1).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run librealsense CI (libCI) unit tests on a remote Jetson device over SSH. Executes run-unit-tests.py with jetson/nightly context, collects test output, dmesg logs, and individual test logs, saves them locally, and produces a detailed analysis report. Use when the user wants to: run libCI, run librealsense tests, run unit tests on jetson, run live tests, run nightly tests, test camera with librealsense, run libCI regression, run libCI with repeat.
Deploy the RealSense MIPI platform driver to a NVIDIA Jetson device. Use when the user wants to deploy, flash, install kernel/modules/DTBs to a Jetson, or verify a deployment. Triggers on requests mentioning deploy, flash, install kernel, push to jetson, or update jetson.
Run the D4XX StreamToMetaData streaming stability test on a Jetson device over SSH. Executes StreamingTestRunner.py with fixed test profiles (DEPTH+IR+COLOR at 848x480@30fps), analyzes output for streaming errors, checks dmesg for D4XX/GMSL driver errors, and produces a summary report. Supports multiple iterations with a compiled end report. Use when the user wants to: run streaming test, run stability test, run StreamToMetaData, test streaming on jetson, run streaming iterations, stress test camera, start/stop test, cycle test, or check streaming reliability.
Run V4L2 pytest tests on a remote Jetson device over SSH. Use when the user wants to run v4l2 tests, test the V4L2 driver on Jetson, run pytest for v4l2_test, check V4L2 functionality, or validate camera driver changes. Collects test results, dmesg logs, and provides detailed analysis of failures including error classification and root cause diagnosis.
Verify a deployed RealSense MIPI platform driver on a Jetson device. Use when the user wants to check if deployment succeeded, verify the driver is working, or test camera functionality. Triggers on requests mentioning verify deployment, check deployment, test driver, verify camera, or deployment status.
Set up a fresh development workspace for the RealSense MIPI platform driver on a Linux VM. Use when the user has cloned the repo and needs to prepare for building — installing dependencies, downloading NVIDIA sources, applying patches, building, and configuring git. Triggers on requests mentioning setup workspace, prepare environment, first time setup, new workspace, get started, fresh clone, initialize workspace, or onboarding.
| name | build |
| description | Build the RealSense MIPI platform driver for NVIDIA Jetson. Use when the user wants to build the kernel/driver/DTBs for a specific JetPack version or troubleshoot build issues. Triggers on requests mentioning build, compile, make, or JetPack version numbers (4.6.1, 5.0.2, 5.1.2, 6.0, 6.1, 6.2, 6.2.1). |
Valid versions: 4.6.1, 5.0.2, 5.1.2, 6.0, 6.1, 6.2, 6.2.1
Always ask the user which JetPack version to target if not specified.
All commands run from the repository root. The $VERSION placeholder below refers to the JetPack version (e.g., 6.2).
Ask the user whether they need to apply patches or just copy d4xx.c and build.
Requires git config user.name and git config user.email to be set.
Always reset patches before re-applying:
./apply_patches.sh $VERSION reset
./apply_patches.sh $VERSION
Copy the driver source directly to the build tree:
cp kernel/realsense/d4xx.c sources_$VERSION/nvidia-oot/drivers/media/i2c/d4xx.c
cp kernel/realsense/d4xx.c sources_$VERSION/kernel/nvidia/drivers/media/i2c/d4xx.c
Where $VERSION is the actual JetPack version (e.g., 6.2, 5.1.2), matching the sources_* directory name.
./build_all.sh $VERSION
Flags:
--clean — remove previous build artifacts before building--dev-dbg — enable CONFIG_DYNAMIC_DEBUG and CONFIG_DYNAMIC_DEBUG_CORE in kernelOutput directory: images/$VERSION/ (normalized: images/6.x/ for JP 6.x, images/5.x/ for JP 5.x).
JP 6.x (Orin): Out-of-tree module build. Builds kernel image, NVIDIA OOT modules (nvidia-oot, nvgpu, etc.), device tree overlays (tegra234-camera-d4xx-overlay*.dtbo). Sources in sources_6.*/. i.e for JP6.2 sources will be located at sources_6.2/
JP 5.x / 4.6.1 (Xavier): In-tree kernel build with tegra_defconfig. Builds kernel image, DTBs, and modules. Sources in sources_5.x/ or sources_4.6.1/.
Native builds on aarch64 skip toolchain setup. Cross-compilation toolchains are in l4t-gcc/$VERSION/ (installed by setup_workspace.sh):
aarch64-linux-gnu-aarch64-buildroot-linux-gnu-aarch64-buildroot-linux-gnu-kernel/realsense/d4xx.c → sources_*/nvidia-oot/drivers/media/i2c/ (JP 6.x) or sources_*/kernel/nvidia/drivers/media/i2c/ (JP 4/5)hardware/realsense/tegra234-camera-d4xx-overlay*.dts → overlay dir (JP 6.x)hardware/realsense/tegra194-camera-d4xx-*.dtsi → DT dir (JP 4/5)./apply_patches.sh $VERSION reset first, then re-apply.git config user.name and git config user.email before apply_patches.sh../setup_workspace.sh $VERSION first (downloads NVIDIA sources + toolchain).BUILD_NUMBER env var is set (common in CI), it changes the kernel vermagic string.