Maximizing performances of TX2

Hello everyone,
I’m trying to set up OpenPTrack on a Jetson TX2 (guide here: I know this guide is for the TX1 and not TX2, but I’m trying to make it work anyway. For example I’ve changed the names of CPU/GPUSetter and MaxPerformance fromt […]TX1 to […]TX2, but kept the scripts the same as in the guide (points 4.1, 4.2 and 4.3).
Now if I try running point 12 with the command:

sudo MaxPerformanceTX2 &> /dev/null

nothing happens, and when typing:

sudo Status

I get:

CPUs active (it should be 0-3):

    CPUs freq (it should be 2320500):
    CPU governor (it should be userspace):

    GPU clock (it should be 852000000):
cat: /sys/kernel/debug/clock/override.gbus/rate: No such file or directory

    GPU memory clock (it should be 924000000):
cat: /sys/kernel/debug/clock/override.emc/rate: No such file or directory

    USB Autosuspending state (they all should be -1):

So I’ve checked if the two files of the error are present, but actually inside the folder “/sys/kernel/debug/” there’s not a “clock” folder, and I can’t find the required files.
What can I do?

You may just boost your TX2 with:

sudo nvpmodel -m0
sudo /home/nvidia/

You may look at the latter script for further details.

Thank you!
Now, if I execute these commands and then check the status with

sudo Status

I can see the performances have been improved but the memory clocks still refer to the wrong files… Is there a way to change it back to default?

I don’t know about this Status command, I suppose it’s a script from the mentioned github repository.
Such a script uses sysfs nodes, but these nodes’ paths change among L4T versions and boards (seems it was for TX1).

You may get the details of clocks with

sudo /home/nvidia/ --show

and see the EMC clock has been correctly set. You may fix your ‘Status’ script with right sysfs paths that you can find in

If you run

sudo /home/nvidia/ --store

after boot, it will save the clocks config into ~/l4t_dfs.conf and you can later restore this clocks config with

sudo /home/nvidia/ --restore

That was really helpful, thank you again (and sorry for the n00b question)!