Cannot enable SUPER_MAXN mode

Robotics & Edge Computing Jetson Systems Jetson Orin NX
,
1

I have been trying to get a 16GB Orin NX to use the higher clock frequencies in ‘super’ mode. In super mode, the GPU frequency should be 1173MHz, but I see max 918 MHz after running sudo jetson_clocks. I replaced /etc/nvpmodel.conf with /etc/nvpmodel/nvpmodel_p3767_0000_super.conf. I added FDT /boot/tegra234-p3768-0000+p3767-0000-nv-super.dtb to /boot/extlinux/extlinux.conf. After replacing nvpmodel.conf, I was able to select ‘MAXN SUPER’ from the GUI in Ubuntu but can still only achieve 918 MHz as seen in tegrastats. I am having the same issue on an Orin Nano (8GB) as well. The Nx is installed on a Waveshare carrier board: Jetson Orin Nano/NX AI Base Board, Waveshare Orin Nano/NX Base Board Based on Jetson Orin Nano and Jetson Orin NX module | JETSON-ORIN-IO-BASE and the Nano is installed on an Auvidea JNX42: https://auvidea.eu/product/jnx42-70784/
Could there be some sort of software disable due to the carrier boards I am using? I looked in the sdkmanager for any sort of ‘super mode enable’ and found nothing. Any suggestions are appreciated!

2

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

To address your issue, let’s break down the steps you’ve taken and the potential causes for the clock frequency limitation in Super Mode on your Jetson Orin NX and Jetson Orin Nano devices.

Steps Taken:

  1. You replaced /etc/nvpmodel.conf with /etc/nvpmodel/nvpmodel-p3767-0000-super.conf.
  2. You added FDT boot tegra234-p3768-0000-p3767-0000-nv-super.dtb to boot/extlinux/extlinux.conf.
  3. You selected MAXN_SUPER from the GUI in Ubuntu.

Expected Outcome:

In Super Mode, the GPU frequency should be 1173 MHz, but you’re only achieving 918 MHz as seen in tegrastats.

Potential Causes:

  1. Carrier Board Limitations: The Waveshare carrier board (JETSON-ORIN-IO-BASE) for the Jetson Orin NX and the Auvidea JNX42 carrier board for the Jetson Orin Nano might have limitations or configurations that prevent the devices from reaching the higher clock frequencies in Super Mode.
  2. Software Disable: There might be a software disable or configuration that prevents the devices from using the higher clock frequencies in Super Mode. You’ve checked the SDK Manager, but there might be other software configurations or settings that need to be adjusted.
  3. Thermal or Power Limitations: The devices might be thermally or power limited, preventing them from reaching the higher clock frequencies in Super Mode.

Suggestions:

  1. Verify Carrier Board Configurations: Check the documentation and configurations for the Waveshare and Auvidea carrier boards to ensure they support the higher clock frequencies in Super Mode.
  2. Check Software Configurations: Review the software configurations and settings on your devices to ensure there are no limitations or disables preventing the use of higher clock frequencies in Super Mode.
  3. Monitor Thermal and Power: Use tools like tegrastats and jetson_clocks to monitor the thermal and power usage of your devices. If the devices are thermally or power limited, you might need to adjust the cooling or power supply to enable the higher clock frequencies.
  4. Contact NVIDIA Support: If you’ve checked all the above and still can’t achieve the higher clock frequencies in Super Mode, contact NVIDIA support for further assistance.

Comparison with Other Devices:

If you have access to other Jetson Orin NX or Jetson Orin Nano devices with different carrier boards, try testing Super Mode on those devices to see if the issue is specific to the Waveshare and Auvidea carrier boards.

By following these steps and suggestions, you should be able to identify and potentially resolve the issue preventing your Jetson Orin NX and Jetson Orin Nano devices from reaching the higher clock frequencies in Super Mode.

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

4

For NV devkit case, you should flash the super mode config manually.

Sdkmanager won’t flash super mode by default.

For a custom board case, not sure if vendor provided any custom BSP. The kernel dtb from the BSP we provided may not work on their board.

5

Thank you for your reply. That directly contradicts this, does it not?

6

Are you sure you are flashing the board with sdkmanager+ jetpack6.2?
Your flash log will tell what thing got flashed too.

7

yes, I tried 6.2 and 6.2.1, L4T 36.4.3 and 36.4.4

8

Solved for both Nx and Nano:

download and untar the image from https://auvidea.eu/firmware/

In ~/nvidia-jetson/Linux_for_Tegra

For the JNX42, repeatedly hammer:

sudo ./flash_orin_nx_nano_jnx42_super.sh

Expect it to fail usb write a bunch of times first. Use a USB hub a good USB cable and unplug ethernet.

For the Waveshare:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -p “-c ./bootloader/generic/cfg/flash_t234_qspi.xml” -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-orin-nano-devkit-super external

9

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