What problem does it solve? Customizing clock behavior on NVIDIA Jetson targets requires editing low-level firmware files (BPMP DTB) and boot scripts (nvpower.sh) before flashing, with SoC-specific rules and multi-node edits that are easy to get wrong. This Skill guides agents through locking or capping CPU/GPU/EMC clocks, toggling EMC/CPU DVFS, and changing cpufreq governors safely within the overlay-tracker workflow. ## Core Features & Use Cases - BPMP DTB clock edits: Set max-rate-custom ceilings on named clock nodes, including the multi-node T23x GPU cap across nafll_gpusys and every nafll_gpcX partition. - EMC DVFS control: Disable or re-enable EMC DVFS with the correct SoC-conditional node set (bwmgr + cactmon on all SoCs, plus osp-controller deletion on T26x Thor only). - nvpower.sh governor edits: Change cpufreq/devfreq governors, pin devices to Fmax, or set min/max/static rates via the boot-time script. - Use Case: Pin an Orin AGX devkit to MAXN for an overnight stress run — remove clock ceilings, disable EMC DVFS, set performance governors, and deploy via the promote/flash chain. ## Quick Start Ask the agent to lock the GPU clock to a specific rate or disable EMC DVFS on your Jetson target using the jetson-customize-clocks skill before flashing the image.