3.6.7. Rogue Debug Info

Rogue graphics drivers include the following tools bundled with their user mode libraries:

Table 3.17 Included rogue debug tools


Control debug verbosity and other device info


Dump diagnostic information for an application


Start, Stop, Restart and configure the GPU using a powervr.ini file


Attempt a number of blit opperations and display them to the screen


Attempt a number of compute tasks on the core


Attempt a number of processes on the core to stress the KickSync API


Render a triangle to the attached display


Attempt to twiddle a number of textures in a number of pixel formats

While future releases of ti-img-rogue-umlibs may include more tools, this is the core set expected to be available in most ti-img-rogue-umlibs releases and are the most useful for verifying GPU functionality.

The order of operation to verify fundamental GPU functionality is as follows:

  1. Use rgx_kicksync_test to verify the GPU can communicate with the kernel module.

  2. Use rgx_compute_test to verify that the GPU is able to handle a proper compute load.

  3. Use rgx_triangle_test to verify that the GPU is able to render to an output buffer.

If fundamental functionality has been verified and you are still experiencing issues try checking the output of the following:

target # pvrdebug -dd


When raising a ticket on e2e forums it is useful to include the output of this command if available.

This will dump all device information as reported by the kernel module. Please insure that the debug info reports:

Comparison of UM/KM components: MATCHING

User mode and Kernel mode components must move in lockstep. If they do not match this could lead to the kernel module failing to initialize or undefined behavior.