You copied the Doc URL to your clipboard.

Troubleshooting Graphics Analyzer Mode issues

If you encounter a problem running Graphics Analyzer, consult the following list of possible errors. These errors are listed in the order in which Streamline detects them.

Problem

Solution

Error message generated:

No Graphics Analyzer Daemon running on target device.

Launch aga-daemon on the target device.

Error message generated:

Timed out connecting to Graphics Analyzer Daemon. Perhaps Graphics Analyzer is already connected.

Arm Streamline detected that aga-daemon is already busy tracing and cannot perform a new tracing request.

Stop any ongoing tracing operations.

Error message generated:

Unsupported version of Graphics Analyzer Daemon is running.

Install a newer version of aga-daemon which supports the Graphics Analyzer mode feature.

Error message generated:

No Graphics Analyzer executable found. Please check the location specified in Preferences->External Tools.

Open Window > Preferences > Streamline > External Tools and set the path to the Graphics Analyzer executable in the Graphics Analyzer Installation field.

Error message generated:

Unsupported version of installed Graphics Analyzer application found. Version x.x.x found, but at least version 4.0.0 required.

Upgrade to Graphics Analyzer version 4.0.0.

Error message generated:

Mali Graphics Debugger x.x.x reported an invalid protocol version number. Please make sure the version of Graphics Analyzer you are using is compatible with this version of Streamline.

Upgrade to Graphics Analyzer version 4.0.0.

Error message generated:

Unable to detect Graphics Analyzer application version. Please ensure the executable path is valid.

Ensure the path in the dialog at Window > Preferences > Streamline > External Tools points to a valid installation of Graphics Analyzer.

Error message generated:

An error occurred when attempting to detect Graphics Analyzer Daemon version.

Ensure that the connection with the target device is working correctly, and that the correct version of aga-daemon is installed and running on the device. Also ensure that aga-daemon is contactable through port 5002 and is not, for example, blocked by a firewall.

Error message generated:

Could not determine hostname for target device, or 'adb forward' failed.

If Arm Streamline cannot determine the hostname for the target device, it is not possible for it to work out the IP address where aga-daemon is running.

Alternatively for adb targets, the command adb forward failed and Arm Streamline was not able to forward the aga-daemon port so that it could communicate with aga-daemon.

For adb connections, ensure that the path to the adb executable is set in the dialog at Window > Preferences > Streamline > External Tools. Also ensure that there are no conflicting port forwarding rules which are already configured with adb.

For non-adb connections, treat this error as a bug.