I am unable to run teh Nvidia SDK manager on teh host Windows 11 machine, even though I have installed Nvidia nsight systems on teh host machine (Win 11) and the Nsighst CLI version on teh device (Jetson Orin Nano Development kit). The SDK manager says that there are ano available versions for teh Win11 host, & the Nvidia Systems says that the target is not supported:
[Error] Target is not supported.
This version of Nsight Systems does not support profiling on the selected target.
Missing directory with target binaries:
C:\Program Files\NVIDIA Corporation\Nsight Systems 2025.5.1\target-linux-tegra-armv8
However, I can run teh nsys commands on teh Jetson with my Python segmentation script, since I have all teh required specifications (given below).
metazet@metazet-desktop:~/path_detection_jetson/software4metazet$ nsys status -e
Timestamp counter supported: Yes
CPU Profiling Environment Check
Root privilege: disabled
Linux Kernel Paranoid Level = 0
Linux Distribution = Ubuntu
Linux Kernel Version = 5.15.148-tegra: OK
Linux perf_event_open syscall available: OK
Sampling trigger event available: OK
Intel(c) Last Branch Record support: Not Available
CPU Profiling Environment (process-tree): OK
CPU Profiling Environment (system-wide): OK
How do I run teh Nsights Systems on my host system ?
The flash software must run on Linux. JetPack/SDK Manager (a front end to the flash software) further restricts this to various Ubuntu releases. The end target (in this case the original Nano which is a small form factor TX1) restricts this even more when using the JetPack/SDKM front end (command line flash lacks some options, but it does open up to a wider array of Linux host PCs for flash). You are advised to use Ubuntu 18.04 for this case; if on command line, then you still must use a Linux host.
There are things like VMs which NVIDIA does not support. It isn’t possible for NVIDIA to provide information to all of the different VMs, this would be up to the VM support. The major tips on what to do if you do use a VM (without NVIDIA support) would be to make sure your filesystem underneath it is ext4, and to make sure that the USB pass-through always goes to the VM (a Jetson in recovery mode is a custom USB device; the USB disconnects and reconnects during flash, and often VMs need more configuration to keep that connection).
Some people do use WSL2, but this has its own custom setup which NVIDIA won’t guarantee. Containers have a use sometimes, but this too is up to the end user to research and set up.
I don’t know if Nsight will work with a Jetson from Windows once the Jetson is flashed, but it might. When running normally a Jetson is not a custom USB device and so there is a lot more Windows might work with.
Incidentally, one of the best ways to deal with this is to add a second disk to your host PC and dual boot.