メニュー
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.
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.
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).
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 | deploy |
| description | 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. |
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.
To deploy use this bash command:
./scripts/deploy_kernel.sh $VERSION <TARGET_IP> [USERNAME] [REMOTE_PATH]
Defaults: USERNAME=administrator, REMOTE_PATH='git.USER.NAME'
The command must have all 3 arguments to perform the full deploy. Ask the user to provide username and remote path if not provided. Save in memory for the next deploy command. Ask the user to confirm the TARGET_IP before proceeding. Save in memory the last used TARGET_IP for the next deploy command.
Deploy packs build artifacts into kernel_mod/$VERSION/, SCPs to the Jetson, runs the on-device install script, then reboots.
Without a TARGET argument, deploy only packages locally (no SCP/reboot).
Reboot of the Jetson will take about 2-5 minutes. After reboot, the new kernel/modules should be active.
After deploy and reboot, SSH into the Jetson and run:
sudo dmesg | grep d4xx # Check driver probe — expect "d4xx" probe messages with no errors
ls -l /dev/video* # Should show 6 video devices per camera (video0–video5)
v4l2-ctl -d0 --stream-mmap # Verify streaming works
If dmesg shows no d4xx messages or /dev/video* devices are missing, the driver did not load — check for patch/build version mismatch or missing DTB overlay.
Deploy packs the following from images/$VERSION/:
JP 6.x (Orin):
tegra234-camera-d4xx-overlay*.dtbo)tegra234-*.dtb)JP 5.x / 4.6.1 (Xavier):
./scripts/deploy_kernel.sh — Works for all JetPack versions./build_all.sh $VERSION) before deploying.dmesg for errors. Ensure the correct JetPack version was used for both build and deploy.sudo reboot.