SPRUJ17I March 2022 – August 2025 AM2631 , AM2631-Q1 , AM2632 , AM2632-Q1 , AM2634 , AM2634-Q1
softwareRevision: = SEQUENCE {
revision: INTEGER -- Software revision
}DESCRIPTION
The information in the software revision is used to indicate the version of the image which is being loaded.
revision:
This is the version number. This will be matched to the EFUSE programmed version to indicate if the image loading should be done or not.
| Value | ||
|---|---|---|
| This is applicable only for HSSE devices. | ||
| HSM Runtime + R5 SBL |
| EFUSE Revision | Certificate Revision | Description |
|---|---|---|
| 0 | 0 | Ignore the revision checking. Images will *always* be loaded |
| 0 | >0 | Device does not mandate revision checking. Images will be loaded |
| >0 | 0 | EFUSE Version > Certificate Version. Image will *never* be loaded. |
| >0 | >0 | Image will be loaded only if the Certificate revision >= EFUSE revision |
Revision Information is read from the following EFUSE fields.
| EFUSE | Description |
|---|---|
| SWRV_SBL | This is used to perform the revision checking while loading the R5 SBL |
SWRV_HSM | This is used to perform the revision checking while loading the HSM Runtime |
The number of bits for each of the EFUSE in the table above is 64bits. The revision EFUSE supports dual redundancy; this implies that a maximum of 32 revisions can be supported.
Note: The EFUSE SWRV_APP is read and is passed as is by the HSM Boot ROM to the application via the Asset Interface. This EFUSE has a length of 192bits and the interpretation of this is left to the HSM Runtime developers.