NVIDIA Jetson Orin - Set Values Manually

Follow us on:

Share This Page

Facebook Twitter LinkedIn WhatsApp Email Copy Link

Close

Send Email Using

Gmail (Web) Thunderbird (default mail app)

Close

🚧 Documentation is under development

The NVIDIA Jetson Orin guide is currently under active development. Some sections may be incomplete or change without notice.

Questions? Contact RidgeRun or email to support@ridgerun.com.

NVIDIA Jetson Orin

< >

Contents Pin

• Introduction
  • SoM Overview
  • Carrier Boards
    • NVIDIA developer kit
    • Auvidea X230D
    • Connect Tech Forge
  • Software Development Support
• JetPack 7.2
  • Getting Started
    • Installing JetPack
    • Flashing the board with GUI installer
    • JetPack Components
  • Compiling Source Code
    • Obtaining Sources
    • Building Kernel, OoT Modules and DTBs
  • Flashing the Board from Cmdline
    • Flashing Filesystem
  • Performance Tuning
    • Evaluating Performance
    • Set Values Manually
    • Tuning Power
    • Software Encoders For Jetson Orin Nano
• JetPack 6.1
  • Getting Started
    • Installing JetPack
    • Flashing the board with GUI installer
    • JetPack Components
  • Compiling Source Code
    • Obtaining Sources
    • Building Kernel, OoT Modules and DTBs
  • Flashing the Board from Cmdline
    • Flashing Filesystem
• JetPack 5.0.2
  • Getting Started
    • Installing JetPack
    • Flashing the board with GUI installer
    • JetPack Components
  • Compiling Source Code
    • Obtaining Sources
    • Compiling Kernel, OoT Modules and DTB
  • Flashing the Board from Cmdline
    • Flashing Filesystem
  • Performance Tuning
    • Evaluating Performance
    • Set Values Manually
    • Tuning Power
    • Maximizing Performance
    • Software Encoders For Jetson Orin Nano
• Development in the Board
  • Getting into the Board
    • Using Serial Console
    • Using SSH
    • Using Ubuntu Login
    • Installing Packages
• Emulation
  • Flashing commands for emulation
• Supported Cameras
  • IMX477+J20 Driver
• GStreamer Pipelines
  • Capture and Display
  • H264
  • H265
• RidgeRun Products
  • GstPTZR
  • GstCUDA
  • GstColorTransfer
  • GstWebRTC
  • GstRtspSink
  • GstInterpipe
  • GstInference
  • GstVPI
  • GStreamer Daemon
  • GstShark
• RidgeRun Reference Designs
  • Panoramic Stitching and WebRTC Streaming
• Reference Documentation
• Contact Us

These procedures follow NVIDIA's Jetson Linux r39.2 Orin guide. Power-mode, thermal, and electrical limits constrain clock requests.

Manage CPU State

Use an existing secondary CPU, such as cpu1:

cat /sys/devices/system/cpu/online
cat /sys/devices/system/cpu/cpu1/online

Enable:

echo 1 | sudo tee /sys/devices/system/cpu/cpu1/online

Disable:

echo 0 | sudo tee /sys/devices/system/cpu/cpu1/online

Select the CPU Performance Governor

For workloads underperforming with schedutil, NVIDIA suggests the performance governor. Inspect available governors, then select it if listed:

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo performance | sudo tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

CPUFreq policies may cover multiple CPUs. The performance governor requests the highest frequency permitted by the policy.

Change CPU Frequency

CPUFreq values use kHz. Hardware limits (cpuinfo_*) differ from policy limits (scaling_*).

CPU_PATH=/sys/devices/system/cpu/cpu1/cpufreq
cat "$CPU_PATH/cpuinfo_min_freq"
cat "$CPU_PATH/cpuinfo_max_freq"
cat "$CPU_PATH/cpuinfo_cur_freq"
cat "$CPU_PATH/scaling_min_freq"
cat "$CPU_PATH/scaling_max_freq"
cat "$CPU_PATH/scaling_available_frequencies"

Choose a listed frequency within the current policy range and active power mode's limits. Set equal policy limits for a fixed frequency request:

read -r -p "CPU frequency from the list (kHz): " CPU_FREQ
echo "$CPU_FREQ" | sudo tee "$CPU_PATH/scaling_min_freq"
echo "$CPU_FREQ" | sudo tee "$CPU_PATH/scaling_max_freq"

The minimum cannot exceed the maximum. If increasing beyond the current maximum, raise the maximum first; if decreasing below the current minimum, lower the minimum first. To retain a range, set the two limits to different supported values.

Change GPU Frequency

Read limits and supported frequencies:

GPU_PATH=/sys/devices/platform/17000000.gpu/devfreq/17000000.gpu
cat "$GPU_PATH/min_freq"
cat "$GPU_PATH/max_freq"
cat "$GPU_PATH/cur_freq"
cat "$GPU_PATH/available_frequencies"

Select a listed value within the current limits; use equal limits for a fixed frequency request:

read -r -p "GPU frequency from the list: " GPU_FREQ
echo "$GPU_FREQ" | sudo tee "$GPU_PATH/min_freq"
echo "$GPU_FREQ" | sudo tee "$GPU_PATH/max_freq"

For a range, write distinct supported values to min_freq and max_freq.

Change Memory Frequency

Inspect EMC limits and current rate:

sudo cat /sys/kernel/debug/bpmp/debug/clk/emc/min_rate
sudo cat /sys/kernel/debug/bpmp/debug/clk/emc/max_rate
sudo cat /sys/kernel/debug/bpmp/debug/clk/emc/rate

EMC limits cannot be changed through these debugfs nodes. Choose a rate between the reported limits, using their units:

read -r -p "EMC rate within the reported limits: " EMC_FREQ
echo 1 | sudo tee /sys/kernel/debug/bpmp/debug/clk/emc/mrq_rate_locked
echo 1 | sudo tee /sys/kernel/debug/bpmp/debug/clk/emc/state
echo 1 | sudo tee /sys/kernel/debug/bpmp/debug/bwmgr/bwmgr_halt
echo "$EMC_FREQ" | sudo tee /sys/kernel/debug/bpmp/debug/clk/emc/rate

Maximize Clocks with jetson_clocks

jetson_clocks sets CPU, GPU, and EMC clocks to the active power mode's maxima. Select the power mode beforehand; changing it afterward requires a reboot.

Inspect and save before applying:

sudo /usr/bin/jetson_clocks --show
sudo /usr/bin/jetson_clocks --store
sudo /usr/bin/jetson_clocks

Alternatively, maximize clocks and fan speed:

sudo /usr/bin/jetson_clocks --fan

Restore saved settings:

sudo /usr/bin/jetson_clocks --restore

References

NVIDIA Jetson Orin

Back to top ↑ < >