I've encountered a GPU driver error reporting many traces in my console. There are also issues manifesting in my application. How can I report this issue to get assistance from TI?
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
TI platforms that contain a graphics accelerator (GPU) can observe a crash or an abnormality that manifests in many different ways including:
A Linux kernel panic/crash
Display output rendering incorrectly
Random artifacts in the output
Tearing, freezing or general corruption
Recoverable or unrecoverable failures in other modules
A failure in the graphics driver
Furthermore, due to the many other modules/accelerators on the SoC, the system can manifest issues outside the GPU context.
The focus of this post are the issues relating to GPU driver or hardware failures. GPU application failures, like incorrect usage of OpenGL APIs, can be debugged in a different manner.
Below is the debugging procedure in chronological order. When posting a ticket about a possible GPU issue, please include at least the Basic Debug. Preferably also the PVR Debug Dump.
The first step to analyze the issue is listing the symptoms seen, for example:
Also, provide the following details about the issue:
The easier it is for TI Engineers to reproduce the issue, the quicker we can root-cause.
It is important to save the console logs when the issue is present. This will give an idea of the application running on the GPU and other useful information from the trace, like the GPU driver version. But it usually is not sufficient and requires further logs.
To narrow-down on the issue, more debug information is usually needed to get firmware logs and other GPU driver information. This information can be gathered for the GPU-related incidents in the following manner:
The GPU contains a separate CPU which runs its firmware. This firmware can provide logs, but are not enabled by default. To enable and capture these logs, please follow the steps below:
More logs might be required, and more flags will need to be enabled. Further guidance will be provided by the TI Engineer.
PVRCarbon is another powerful tool that can be used to record and play-back an application execution. You can find the details and the tool on Imagination Technologies' website:
This tool can be used to record the OpenGLES API calls to the driver and "play" them back as if you were running the application. The instructions are as follows:
To play back the PVRCarbon file created, please use the following steps.