# Debug Source: [https://docs.qualcomm.com/doc/80-70014-20/topic/debug.html](https://docs.qualcomm.com/doc/80-70014-20/topic/debug.html) The debug methods available for the VPU and GStreamer plugins are mentioned here. ## Debug VPU Figure : Debug VPU workflow Page-1 Stop capturing logs Stop capturing logs Run the use case Run the use case Start capturing logs Start capturing logs Set the log level using debugfs node Set the log level using debugfs node Choose the log level Choose the log level Mount debugfs Mount debugfs VPU driver debug log level VPU driver debug log level VPU firmware debug log level VPU firmware debug log level Following are the steps to debug the VPU driver and VPU firmware: 1. Mount the `debugfs` node, using the following command: mount -t debugfs none /sys/kernel/debug/Copy to clipboard 2. Choose VPU driver debug log level and debug log value as listed in the following table. You can also select multiple debug log levels by using the bitmask of debug log values. | Debug log level | Debug log value | | --- | --- | | VIDC\_ERR | 0x00000001 | | VIDC\_HIGH | 0x00000002 | | VIDC\_LOW | 0x00000004 | | VIDC\_PERF | 0x00000008 | | VIDC\_PKT | 0x00000010 | | VIDC\_BUS | 0x00000020 | | VIDC\_STAT | 0x00000040 | | VIDC\_ENCODER | 0x00000100 | | VIDC\_DECODER | 0x00000200 | | VIDC\_PRINTK | 0x10000000 | | VIDC\_FTRACE | 0x20000000 | Note: The VPU driver debug logs are limited to error scenarios, and the default debug level is set to `VIDC_ERR`. 3. Set the VPU driver debug log value to the `/sys/module/iris_vpu/parameters/msm_vidc_debug`node. 1. The following is a sample command to enable all message levels: echo 0x1000037F > /sys/module/iris_vpu/parameters/msm_vidc_debugCopy to clipboard 4. Choose VPU firmware debug log level and debug log value as listed in the following table. You can also select multiple debug log levels by using the bitmask of debug log values. | Debug log level | Debug log value | | --- | --- | | FW\_LOW | 0x00000001 | | FW\_MED | 0x00000002 | | FW\_HIGH | 0x00000004 | | FW\_ERROR | 0x00000008 | | FW\_FATAL | 0x00000010 | | FW\_PERF | 0x00000020 | | FW\_CACHE\_LOW | 0x00000100 | | FW\_CACHE\_MED | 0x00000200 | | FW\_CACHE\_HIGH | 0x00000400 | | FW\_CACHE\_ERROR | 0x00000800 | | FW\_CACHE\_FATAL | 0x00001000 | | FW\_CACHE\_PERF | 0x00002000 | | FW\_PRINTK | 0x10000000 | | FW\_FTRACE | 0x20000000 | Note: The VPU firmware debug logs are limited to error and fatal scenarios, and the default debug level is set to `FW_ERROR | FW_FATAL`. 5. Set the VPU firmware debug log value to the `/sys/module/iris_vpu/parameters/msm_fw_debug`node. 1. The following is a sample command to enable all message levels: echo 0x1000037F > /sys/module/iris_vpu/parameters/msm_fw_debugCopy to clipboard 6. Start capturing kernel messages for both the VPU driver and the firmware using the following command and run the usecase: cat /proc/kmsgCopy to clipboard ## Debug GStreamer plugins Qualcomm GStreamer video plugins are compliant with the standard GStreamer framework. For information on the debug methods for the GStreamer plugins, see [Debug GStreamer Plugins](https://gstreamer.freedesktop.org/documentation/tutorials/basic/debugging-tools.html). Last Published: Jul 12, 2024 [Previous Topic Configure](https://docs.qualcomm.com/bundle/publicresource/80-70014-20/topics/configure.md) [Next Topic References](https://docs.qualcomm.com/bundle/publicresource/80-70014-20/topics/references.md)