# Secure device debugging

Source: [https://docs.qualcomm.com/doc/80-88500-4/topic/85_Secure_device_debugging.html](https://docs.qualcomm.com/doc/80-88500-4/topic/85_Secure_device_debugging.html)

The secure devices cannot be debugged like the nonsecure devices. For secure devices,
    all the logs and dump collection are disabled and tools such as QFIL and ADB are not
    supported.

The secure devices debugging needs specific utilities and prior work of customized image
      generation to get the debug information out of secure device and flash the debug images in the
      device.

Table : Debug utility details

| Debug utility | Details |
| --- | --- |
| Debug policy | Debug policy images with right configurations are needed to be flashed in the device via verified image programming (VIP). It enables the logs and dumps collection on the secure device. |
| VIP | VIP utility is used to flash signed images on the secure device. |
| System debug interface (SDI) | SDI needs to be properly configured in order to collect the dump. |

- For information on debug policy, see <cite class="cite">Sectools: Debug Policy Tool User Guide</cite>
        (80-NM248-6).
- For information on VIP, see <cite class="cite">Qualcomm Firehose Validated Image Programming
          Guide</cite> (80-P9116-1).

**Parent Topic:** [Security](https://docs.qualcomm.com/doc/80-88500-4/topic/76_Security.html)

Last Published: Aug 18, 2023

[Previous Topic
Secure storage](https://docs.qualcomm.com/bundle/publicresource/80-88500-4/topics/84_Secure_storage_.md) [Next Topic
Crypto APIs](https://docs.qualcomm.com/bundle/publicresource/80-88500-4/topics/86_Crypto_APIs.md)