nvidia-skill-finder
Use for NVIDIA-related requests where an NVIDIA skill might help, even if the user did not ask for a skill. Trigger on NVIDIA products, hardware, software,…
Reclaim DRAM by disabling unused subsystems across MB1 BCT, MB2 BCT, kernel reserved-memory, and SWIOTLB. Use for headless or no-camera Jetson deployments; not for CPU/GPU frequency tuning.
$ npx -y skills add NVIDIA/skills --skill jetson-optimize-memory --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/jetson-optimize-memoryContext preview
The summary Claude sees to decide when to auto-load this skill.
Reclaim DRAM by disabling unused subsystems across MB1 BCT, MB2 BCT, kernel reserved-memory, and SWIOTLB. Use for headless or no-camera Jetson deployments; not for CPU/GPU frequency tuning.
name: jetson-optimize-memory
description: >-
Reclaim DRAM by disabling unused subsystems across MB1 BCT, MB2 BCT,
kernel reserved-memory, and SWIOTLB. Use for headless or no-camera
Jetson deployments; not for CPU/GPU frequency tuning.
version: 0.0.1
license: "Apache-2.0"
argument-hint: "headless | no-camera | swiotlb"
metadata:
data-classification: public
author: "Jetson Team"
tags:
- memory
- dram
- carveout
- swiotlb
domain: memoryMemory is reserved across four layers ordered by boot chronology (higher row = earlier in boot, closer to hardware):
| Layer | Content | Key files | |---|---|---| | MB1 BCT | firmware carveouts | per-module misc DTS | | MB2 BCT | firmware loading + AST controls | per-module misc DTS | | Kernel DTS | reserved-memory and driver binding | per-module DTS | | SWIOTLB | DMA bounce pool size | `<module>.conf.common` (`CMDLINE_ADD`) |
**Critical rules:**
request to disable a carveout/cluster/node not in that table.
controls AND removing the AST that references it.**
of how the source `#ifdef`/`#else` looks. Verify the merged binary.
-> OpenRM. Follow the shared derived-platform rule in `target-platform-contract.md`; stop on mismatches instead of guessing.
---
| Keyword | MB1 BCT carveouts | MB2 BCT | Kernel DTS | |---|---|---|---| | `headless` | DCE-family (see chip table) | DCE `auxp_controls` + DCE AST(s) | `display@<addr>` (and `dce@<addr>` if exposed) → disabled | | `no-camera` | RCE/VI/ISP-family | RCE `auxp_controls` (each instance) + RCE AST(s) | recommended: VI/ISP/NVCSI → disabled |
| Scenario | T234 (Orin) | T264 (Thor) | |---|---|---| | `headless` | `CARVEOUT_BPMP_DCE`, `CARVEOUT_DCE`, `CARVEOUT_DCE_TSEC`, `CARVEOUT_TSEC_DCE`, `CARVEOUT_DISP_EARLY_BOOT_FB` | `CARVEOUT_DCE`, `CARVEOUT_TSEC_DCE`, `CARVEOUT_HPSE_DCE`, `CARVEOUT_DISP_EARLY_BOOT_FB` | | `no-camera` | `CARVEOUT_RCE`, `CARVEOUT_CAMERA_TASKLIST` | `CARVEOUT_RCE`, `CARVEOUT_RCE1`, `CARVEOUT_RCE_RW`, `CARVEOUT_VI_TASKLIST`, `CARVEOUT_VI1_TASKLIST`, `CARVEOUT_ISP_TASKLIST`, `CARVEOUT_ISP1_TASKLIST` |
> **Post-boot:** `headless` → `sudo systemctl set-default multi-user.target`.
---
File: `Linux_for_Tegra/bootloader/generic/BCT/tegra<chip>-mb1-bct-misc-<module>.dts` (e.g. `tegra234-mb1-bct-misc-p3767-0000.dts` for Orin Nano, `tegra264-mb1-bct-misc-p3834-0008-p4071-0000.dts` for Thor).
For each carveout, add inside the existing `carveout` node:
aux_info@<CARVEOUT_NAME> {
pref_base = <0x0 0x0>;
size = <0x0 0x0>;
alignment = <0x0 0x0>;
};---
File: `Linux_for_Tegra/bootloader/generic/BCT/tegra<chip>-mb2-bct-misc-<module>.dts` (includes `tegra<chip>-mb2-bct-common.dtsi`).
For each target cluster:
1. Override `auxp_controls@<index>`:
auxp_controls@<index> {
enable_init = <0>;
enable_fw_load = <0>;
enable_unhalt = <0>;
};2. `/delete-node/ auxp_ast_config@<idx>;`
Look up indices in `common.dtsi`: `auxp_controls@N` carries a comment naming its cluster; `auxp_ast_config@N` has `ast_region` children whose `carveout = <CARVEOUT_…>;` lines identify the owner.
---
DTB=Linux_for_Tegra/kernel/dtb/<platform-dtb-name>.dtb dtc -I dtb -O dts -o /tmp/platform.dts $DTB # edit: status = "disabled" on target nodes dtc -I dts -O dtb -o $DTB /tmp/platform.dts
**Display** — disable `display@<addr>`, plus `dce@<addr>` if exposed as a separate kernel node.
**Camera** — under `host1x@<addr>`, disable whichever of `vi*` / `isp*` / `nvcsi` exist on the BSP (only emit present nodes):
Locate the display controller node in the decompiled DTS and disable it. The node's unit address is chip-specific — find it by `compatible` string (e.g. `nvidia,tegra234-display`) rather than hard-coding the address.
host1x@<addr> {
vi0@<addr> { status = "disabled"; };
vi1@<addr> { status = "disabled"; };
isp@<addr> { status = "disabled"; };
isp1@<addr> { status = "disabled"; };
nvcsi@<addr> { status = "disabled"; };
};---
The NVIDIA IOMMU covers peripheral DMA, so SWIOTLB is rarely used. Edit `CMDLINE_ADD` (**never** `CMDLINE`) in `Linux_for_Tegra/<module>.conf.common`:
# Total bytes = swiotlb_value × 2048; 4 MiB pool: CMDLINE_ADD="... swiotlb=2048"
---
After every patched MB1/MB2 BCT `.dts`, reproduce the BSP's compile + decompile using the same `-D…` flags from `bct_flags.append(...)` in `bootloader/tegraflash_impl_t<chip>.py`:
gcc -E -nostdinc -x assembler-with-cpp \
-DENABLE_<FLAG_1> -DENABLE_<FLAG_2> \
-I bootloader -I bootloader/generic/BCT \
-o /tmp/cpp.dts <patched-bct.dts>
dtc -q -I dts -O dtb -o /tmp/cpp.dtb /tmp/cpp.dts
dtc -q -I dtb -O dts /tmp/cpp.dtb | lessConfirm in the merged output:
has `size = <0x0 0x0>` and `pref_base = <0x0 0x0>`.
---
sudo cat /proc/iomem | grep -iE 'nv-reserved|cma|fb|carveout' ls /proc/device-tree/reserved-memory/ dmesg | grep -iE 'firmware|carveout|bpmp|reserved|fail|error' | head -20 free -m
| Scenario | Sysfs | dmesg grep | |---|---|---| | Display off | `ls /sys/class/drm/` (empty) | `tegra-drm\|nvdisplay\|dce\|host1x\|fb0` | | Camera off |
Official, NVIDIA-verified Agent Skills for Claude Code, Codex, and other coding agents.
Use for NVIDIA-related requests where an NVIDIA skill might help, even if the user did not ask for a skill. Trigger on NVIDIA products, hardware, software,…
Official NVIDIA-authored guidance for NVIDIA cuDF GPU DataFrames, pandas acceleration, dask-cuDF, ETL, joins, groupby, CSV/Parquet I/O, nullable semantics, and…
Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.
Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.
Calibrate a new dataset from live RTSP camera streams via the AutoMagicCalib REST API. Use when the user provides RTSP URLs or asks to calibrate live cameras;…
Run end-to-end calibration on the shipped sample dataset (sdg_08_2_sample_data_010926.zip) against a running AMC microservice. Use when user says 'test sample…