I have a Jetson AGX running JetPack 6.2 and am trying to profile an application remotely from macOS using Nsight Systems Version: 2025.3.1.90-253135822126v0 OSX. When I attempt to do so, I get this error:
This version of Nsight Systems does not support profiling on the selected target.
Missing directory with target binaries:
/Applications/NVIDIA Nsight Systems.app/Contents/target-linux-tegra-armv8
It works fine remotely profiling a Linux x86 application.
Is remote profiling support for the Tegra platform? If so, how do I enable it?
Remote profiling of the Tegra platform is currently unsupported. Please note the supported platforms section here: Nsight Systems - Supported Platforms.
As an alternative, please try Nsight Systems CLI directly on the board ( User Guide — Profiling from the CLI) and use macOS host to view the report.
Thanks for the response. Is there a way to hack in support? e.g. copy a collection of files into the application bundle (perhaps from the Windows version?) for Tegra so that they are available during the remote deployment process? I ask because the code->test->iterate cycle is frequent enough that this convenience saves significant time and reduces chances for mistakes.
Short of that, how should I submit a feature request for this capability?
When you upload and run your code on Jetson board, maybe you could incorporate Nsight Systems CLI into your testing procedures to capture reports? There are also options in the tool to analyze it or export the data to other formats for further custom analysis. This way you could automate everything and won’t even need to copy the reports back (but you still could for viewing if needed).
Not sure if that’s an option for you, but you could also run GUI directly on Jetson (and use VNC for remote profiling). That being said - only Linux host is being able to profile Jetson target right now (either Linux x86 or Jetson Linux). You could potentially copy required files to macOS host, but we won’t be able to support you with that, as this is unsupported and untested scenario. Missing directory error may be fixed but host configuration for Jetson profiling may be basically not present or be incorrect.
I will take that feature request and submit to our internal tracker (#5362803). Thanks.