# Secure boot GPIO mapping
Source: [https://docs.qualcomm.com/doc/80-PV086-5P/topic/secure-boot-gpio-mapping.html](https://docs.qualcomm.com/doc/80-PV086-5P/topic/secure-boot-gpio-mapping.html)
The secure boot ensures that the QTI code and the OEM code cannot be modified by another entity. The secure boot configuration is application-based. The applications code creates a root of trust (ROT):
- It is responsible for validating the code image and for validating the boot code stored in external memory.
- It confirms the code originated from a trusted authority (authenticity) and verifies that the code is in its original form (integrity).
- The digital signatures validate the external code image and establish the system security level.
- The ROT verifies the code image version (compares the signed version label to the value in Qfuse).
- Version control ensures that an old revoked code image is unusable.
See the *QRB5165 QFPROM Programming Reference Guide* (80-PV086-97) for details.
| Fuse name | Bit no. in row | Blow value | Comments |
| --- | --- | --- | --- |
| OEM\_SECURE\_BOOT1\_ROM\_PK\_HASH\_IDX0 | 0 | 0 | If PK\_HASH\_IN\_FUSE = 0, this value
selects which root certificate hash to use from the ROM table. |
| OEM\_SECURE\_BOOT1\_ROM\_PK\_HASH\_IDX1 | 1 | 0 | If PK\_HASH\_IN\_FUSE = 0, this value
selects which root certificate hash to use from the ROM table. |
| OEM\_SECURE\_BOOT1\_ROM\_PK\_HASH\_IDX2 | 2 | 0 | If PK\_HASH\_IN\_FUSE = 0, this value
selects which root certificate hash to use from the ROM table. |
| OEM\_SECURE\_BOOT1\_ROM\_PK\_HASH\_IDX3 | 3 | 0 | If PK\_HASH\_IN\_FUSE = 0, this value
selects which root certificate hash to use from the ROM table. |
| OEM\_SECURE\_BOOT1\_PK\_HASH\_IN\_FUSE | 4 | 0 | For boot configuration 1: