Skip to main content
Sets up a Jetson for Axol’s real-time control and camera loops. These settings reset at every reboot. You don’t need to run it yourself. axol provision applies it as its last step. The one-command install’s axol.service applies it at every boot with axol provision --boot. axol jetson.setup is another name for axol provision --boot.
It needs root. Run it as root, or it asks for your sudo password once. If it can’t get root, it logs the manual command and continues. On a computer that isn’t a Jetson it does nothing.

​
What it sets

If it can’t move the CAN interrupt, it logs a warning with the manual echo N | sudo tee /proc/irq/<irq>/smp_affinity_list command. It also warns if irqbalance is running, because that service can undo the change.

​
Supported Jetsons

  • Orin NX 16GB (ZED Box)
  • AGX Orin (32GB, 64GB and Industrial)
  • Thor T5000

​
Power mode changes that need a reboot

Some power mode changes take effect only after a reboot. jetson.setup never reboots by itself, so it can’t interrupt an install or a robot session. It saves the new mode, and the Jetson applies it at the next boot. When axol provision makes the change, it reboots at the end of its run.
NVIDIA calls MAXN and MAXN SUPER experimental, unconstrained modes. It doesn’t recommend sustained heavy work in them unless the module was flashed with the matching -maxn configuration and its more conservative thermal settings. Make sure the robot has enough power and cooling, and watch for thermal throttling during long local inference or training. jetson.setup doesn’t change the board’s thermal settings.
The control loop also needs the real-time scheduling permission that axol provision installs for your login. Without it, the control loop won’t start from a manual axol serve or axol teleop.