Jetson Orin Nano (Jetpack 6.2.1) Super Mode for Manufacturing Module

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
1

We are trying to setup Jetson Orin Nano Manufacturing Module with Jetpack 6.2.1, there are two issues we’ve encountered:

  1. We’ve followed this instruction to replace the nvpmodel.conf file to enable super mode.

When we run “jtop”, it shows the 25W and MAXN_SUPER profile, and we are able to enable these modes.
However when we observe the control tab, the value of warning and critical for VDD_IN current is just 3A and 4A respectively, which means actually it won’t run for higher than 20W.

image
image902×539 20.8 KB

2. Also for GPU clock, it seems it could just go up to 612MHz, while the nvpmodel.conf setting is 918MHz.

image
image898×540 22.8 KB

We’ve cross checked with development kit and does not see both issues mentioned above.

We would like to ask how to replicate the super mode performance in manufacturing version. Thanks

2

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, I’ll address the issues you’ve encountered with setting up the Jetson Orin Nano Manufacturing Module with Jetpack 6.2.1.

Issue 1: No MAXN after upgrade to JP6.2.1 on Orin Nano

You’ve followed the instructions to replace the nvpmodel.conf file to enable super mode, but you’re not seeing the MAXN mode after upgrading to Jetpack 6.2.1. The link is created in /etc/systemd/nvpowersh, but it doesn’t link to /etc/nvpmodel/nvpmodel-p3767-0003-super.conf.

The issue might be due to the fact that the p3767-0003 is the Orin Nano module without an SD card slot, and the p3767-0005 is the Orin Nano module with an SD card slot. Both modules use either nvpmodel-p3767-0003-super.conf or nvpmodel-p3767-0003.conf. Make sure you’re using the correct configuration file for your module.

Issue 2: VDDIN current warning and critical values are too low

When you run jtop, it shows the 25W and MAXN_SUPER profile, and you’re able to enable these modes. However, when you observe the control tab, the value of warning and critical for VDDIN current is just 3A and 4A, respectively, which means it won’t run for higher than 20W.

This issue might be related to the power budget settings in the nvpmodel.conf file. The nvpmodel-p3767-0003-super.conf file has a power budget of 25W, but the actual power consumption might be limited by the VDDIN current settings. You can try adjusting the VDDIN current settings in the nvpmodel.conf file to see if it resolves the issue.

Issue 3: GPU clock frequency is lower than expected

The GPU clock frequency seems to be limited to 612MHz, while the nvpmodel.conf setting is 918MHz. This issue might be related to the GPU clock frequency settings in the nvpmodel.conf file. You can try adjusting the GPU clock frequency settings to see if it resolves the issue.

Comparison with Development Kit

You’ve cross-checked with the development kit and didn’t see both issues mentioned above. This suggests that the issues might be specific to the manufacturing module or the Jetpack 6.2.1 version.

Replicating Super Mode Performance in Manufacturing Version

To replicate the super mode performance in the manufacturing version, you can try the following:

  1. Ensure you’re using the correct nvpmodel.conf file for your module (either nvpmodel-p3767-0003-super.conf or nvpmodel-p3767-0003.conf).
  2. Adjust the VDDIN current settings in the nvpmodel.conf file to allow for higher power consumption.
  3. Adjust the GPU clock frequency settings in the nvpmodel.conf file to match the expected frequency.
  4. Verify that the nvpmodel.conf file is correctly linked in /etc/systemd/nvpowersh.
  5. Reboot the system and re-run jtop to verify that the super mode performance is replicated.

If you’re still experiencing issues, you may want to try flashing the manufacturing module with the jetson-orin-nano-devkit-super configuration to see if it resolves the issues.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

5

It is a nice try using LLM to response questions.

Issue 1: We COULD see MAXN profile, we are concerning for BOTH 25W and MAXN settings in nvpmodel.conf is not the same as what we seen when running jtop.

Issue 2: We could not see any settings related to VDDIN current settings in nvpmodel.conf. We suppose it is not set in nvpmodel.conf as we do not see we could set it using NVIDIA power estimator tool. Please advice on how to do so, or which document we should referring to.

Issue 3: Same as 1, we’ve already set the max. GPU clock frequency as 918MHz, but it shows only up to 624MHz in jtop.

image
image636×559 7.54 KB

6

Hi,

Please ensure you have done above suggestion. The system needs to be re-flashed to have super mode enabled. the commands are listed in

Quick Start — NVIDIA Jetson Linux Developer Guide

8

Thanks, we could see the clock settings and vdd_in current limit as expected for super mode after we flash from command line instead of SDK manager.

10

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.