Unable to Flash and Apply Different Power Mode Configurations on Jetson Orin

Thanks, Wayne.

Just to confirm:

  1. Do super and maxn_super modes support up to 40W power budget?
  2. Is the power budget different between super and non-super modes, or are they the same?

@WayneWWW

Please refer to the document here. It has the answer for the power budget number.

Hi Wayne,

We flashed the board using the jetson-orin-nano-devkit-super-maxn.conf configuration. As per the NVIDIA documentation, this mode is expected to support up to 40W.

However, after booting, we’re still not seeing any indication of a 40W mode.
Attaching a screenshot of the Power Mode UI for your reference.

We’ve already shared all related logs and results from testing this on the official Orin NX devkit with super-maxn.

Could you please confirm if this is expected behavior, or if there’s anything else we need to enable to reflect the 40W support?

regards,
Sunil

@WayneWWW

No, it is not expected. I guess your flash has something wrong again.

Hi Wayne,

We’ve already performed a clean reflash using the default BSP and jetson-orin-nano-devkit-super-maxn.conf.

Please find the following details already shared:

  • jetson-orin-nano-devkit-super-maxn.conf
  • Flash log: jetson_orin_nx_super_maxn_flash_logs.txt
  • Screenshot after boot: jetson_orin_nx_dvkit_sprmaxn_pwr_modes.png
  • jtop output after jetson_clocks: jetson_orin_nx_dvkit_sprmaxn_jtop_with_jetson_clk.png
  • tegrastats output after jetson_clocks: jetson_orin_nx_dvkit_sprmaxn_tegrastats_with_jetson_clk.txt

Please review and let us know if anything still looks incorrect.

Also, once flashed properly, should the super-maxn mode support 40W power budget at runtime?

regards,
Sunil

@WayneWWW

jetson_orin_nx_super_maxn_flash_logs.txt (338.4 KB)
jetson_orin_nx_dvkit_sprmaxn_tegrastats_with_jetson_clk.txt (12.6 KB)



jetson-orin-nano-devkit-super-maxn.conf.txt (2.2 KB)

For this you need to select 0:MAXN mode i think.. Just cross check..
MAXN is internally might be mapped to 40W power budget

How did you modify your custom kernel device tree?
You should make it based on tegra234-p3768-0000+p3767-0000-nv-super.dts.

Your /etc/nvpmodel.conf seems still link to a non super mode config. 40W should be listed on it.

Hi Wayne,

Yes, we did modify our custom DTS based on tegra234-p3768-0000+p3767-0000-nv-super.dts — we’ll share it with you for reference.

However, for now we’re testing only with the Jetson Orin NX devkit and using the default configuration (super-maxn) without any modifications.

We’ve already shared:

  • All logs
  • Config files
  • Boot screenshots
  • jtop and tegrastats output

So even without custom changes, the devkit itself should reflect 40W mode, correct?

Let’s focus on debugging the devkit setup first.

regards,
Sunil

@WayneWWW

Hi,

Please do thing steps by steps.

Go back and use default BSP to flash everything here. Make sure you saw 40W in your result.

Then start to modify the things you are changing here step by step and see which one start to make things different.

I guess it is from your dtb modification…

1 Like

Hi Wayne,

  1. The issue has been resolved.
  2. The fix was to append -super at the end of the custom DTS filename to ensure it is used during flashing in super mode.
    Example:
  • Default: tegra234-bpmp-3767-0000-3768-super.dtb
  • Custom: my-custom-super.dtb

Thanks for the guidance.

Best regards,
Sunil

@WayneWWW

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