Procedure

1. Open Graphics Analyzer.
2. Click Open the Device Manager .
3. Select the Linux/IP tab.
   Results: The Device Manager automatically shows any Linux devices on the same local network and subnet as the host that are running the aga-daemon application. Alternatively, you can connect to the IP address of the device.
4. Connect to your device using one of the following methods:
   Figure 3-4 The Device Manager dialog

   

   
   
   
   • Select a Linux device. If no Linux devices have been detected, you can directly connect to the device using the IP address instead.

     Note:

     For Linux devices on IPv6 networks, automatic browsing of devices is not supported. Connect to the device using the IP address.
   • Enter the IP address of the device, and the port that the daemon is running on. Then click Start Capture.

     Note:

     • IPv4 and IPv6 are supported. Devices that have both IPv4 and IPv6 addresses are accessible with either address.
     • The default port is 5002. To change the default port, use the --port/-p option and specify a different port number between 1 and 65535. You must then enter the new port number in the Device Manager > TCP/IP tab
     • The Device Manager obtains the GL Vendor, GL Renderer, and GL Version strings of the device by dynamically loading the libGLESv2 library. If this library could not be found or loaded, the strings appear as Unknown.
   Results: Graphics Analyzer connects to your device and installs the layer driver and daemon application that it uses to communicate with it. When the connection is established, the Device Manager closes and the live capture is shown.
5. Optionally, select a preset configuration, or choose which API assets are captured.
   Figure 3-5 Trace Config dialog

   

   
   
   

   The more asset types you enable, the slower the application runs, the more memory is required, and the larger the generated capture file is. See 3.4 Configure tracing assets for more information.

6. Perform your test scenario on the device. Graphics Analyzer displays the data it receives from the device.
7. When you see a problem area in the capture:
   • Use the pause, step, and play buttons to locate a frame that you want to analyze more closely. See 3.5 Pause, step frames, and resume.
   • Click the camera icon to capture the framebuffer output at the current frame. See 3.6 Capturing framebuffer content.
   • Capture extra frame data by enabling Overdraw, Shader map or Fragment count modes, then click the camera icon to collect the data. Learn more about these modes in Chapter 4 Analyzing your capture.
8. When you have captured the data you need, click Stop tracing .
   Results: The frames are listed in the Trace Outline view. To identify the type of frame capture you performed, an icon is shown next to the frames when you have captured extra data.
9. To show only the frames where you have captured extra data, select the Show Only Frames With Features Enabled check box.
   Figure 3-6 Show only frames with features enabled

   

   
   
   
10. Expand a frame to see the render passes and draw calls within it. Select frames, renderpasses, and draw calls to explore their data using the different data views. See Chapter 5 The Graphics Analyzer interface for more information about the views.