SPRADI3 June 2024 AM625 , AM62P , AM67 , AM67A , AM68 , AM68A , AM69 , AM69A , DRA829J , DRA829J-Q1 , DRA829V , DRA829V-Q1 , TDA4AEN-Q1 , TDA4AH-Q1 , TDA4AL-Q1 , TDA4AP-Q1 , TDA4APE-Q1 , TDA4VE-Q1 , TDA4VEN-Q1 , TDA4VH-Q1 , TDA4VL-Q1 , TDA4VM , TDA4VM-Q1 , TDA4VP-Q1 , TDA4VPE-Q1
As mentioned in Section 2.6, the HWR logs contain logs for the GPU driver and firmware. To collect the logs
from the GPU, a utility is available called pvrlogdump.
pvrlogdump comes with the GPU driver installation. The utility
saves the logs in the /tmp directory by default and output the
names of the files so the files are easy to extract. Alongside the files generated
by pvrlogdump, it is also useful to share the console of the
execution of the app as this shows when the HWR happened. The following is an
example of the pvrlogdump command output:
root@j721s2-evm:~# pvrlogdump
Checking driver state ............... initialised
Checking for debugfs ................ found
Checking for lockdep ................ not found
Checking for ftrace ................. not found
Checking for firmware log groups .... not found
There are no AppHints enabled in /etc/powervr.ini or in debugfs for any of the firmware log groups. Unless 'pvrdebug' tool was used for that purpose there will be no information in firmware log. Please consider enabling some of the firmware log groups before the problem occurs.
Dumping data ........................
[ 163.767302] PVR_K: 1005: User requested PVR debug info
[ 163.772711] PVR_K: 1005: ------------[ PVR DBG: START (High) ]------------
…
[ 164.363015] PVR_K: 1005: ------------[ PVR DBG: END ]------------
done
Archiving data ...................... done
File /tmp/pvrlogdump_2402262237.txt.gz was created.