SPRUJ17H March 2022 – October 2024 AM2631 , AM2631-Q1 , AM2632 , AM2632-Q1 , AM2634 , AM2634-Q1
The Debug Object Identifier has the following format:-
Debug::= SEQUENCE {
uid OCTET STRING -- Device unique ID
debugType INTEGER -- Debug type
coreDbgEn INTEGER -- Enable core debug mask
secCoreDbgEn INTEGER -- Enable secure core debug mask
}
The debug object identifier if specified allows the debug ports to be enabled for a specific device. It also can be used to specify the Key protections.
OPTIONS
UID: This is the unique identifier associated with the device. Device specific unique identifiers can be retrieved using the following: -
1. SOC Identifier while operating in a peripheral boot mode
2. Assets on the successful load of the HSM Runtime
The UID field of all 0’s is considered to be a wildcard.
Debug Type:
The debug type is described as follows:-31 | 18 | 16 | 15 | 0 | ||
Reserved | CUST | Debug Type |
Key Protections:
Key Protection | Value | Description |
CUST | 0 | Do not disable access to customer keys |
1 | Disable access to customer keys |
Debug Type:
Value | Description |
0 | Disable debug |
1 | Preserve debug state |
2 | Enable non-secure debug (Public Debug) |
3 | Reserved |
4 | Enable secure and non-secure debug (Full Debug) |
5-65635 | Reserved |
coreDbgEn and secCoreDbgEn: These fields are not used and will be ignored.
Value | Description | |
---|---|---|
R5 SBL Image: |
| |
HSM Runtime Image: |
|
Value | Description | |
---|---|---|
Outer certificate |
|