SPRUJ55D September 2023 – July 2025 AM263P2 , AM263P2-Q1 , AM263P4 , AM263P4-Q1
The Boot Information Object Identifier has the following format:-
bootInfo ::= SEQUENCE {
cert_type: INTEGER, -- identifies the certificate type
boot_core: INTEGER, -- identifies the boot core
core_opts: INTEGER, -- Core Options
load_addr: OCTET STRING, -- Global address image destination
image_size: INTEGER, -- Image size in bytes
}DESCRIPTION
The Boot Information Object identifier provides information about the image which is being loaded. This information is mandatory and needs to be present in the all the X.509 certificates else the image boot will fail.
OPTIONS
Certificate Type: The certificate type defines the type of the image which is being loaded by the Boot-ROM. The following table illustrates the supported values.
| Value | Description |
|---|---|
| 0x1 | R5 SBL Boot Image |
| 0x2 | HSM Runtime Image |
| Value | Description |
|---|---|
| 0x0 | HSM Core |
| 0x10 | R5 Core |
Core Options: The core options are documented in the table below.
| Value | Description |
|---|---|
| 0x0 | Lock Step Mode |
| Non-Zero | Dual Core Mode |
The core options work in conjunction with the following EFUSE configurations:-
1. DUAL_CORE_BOOT_ENABLE
2. DUAL_CORE_SWITCH_DISABLE
These will determine the final operational mode in which the R5 will be executed. The following table summarizes the operation:
| Dual Core Boot Enable | Dual Core Switch Disable |
Core Options |
Description |
|---|---|---|---|
| 0 | 1 | 0 | Case1: Executing in Lock Step Mode Switching to dual boot is *Disabled* Certificate requests to execute in Lock Step Mode Result: R5 will be started in Lock Step Mode. |
| 0 | 1 | 1 | Case2: Executing in Lock Step Mode Switching to dual boot is *Disabled* Certificate requests to execute in Dual Core Mode Result: Error: Dual Boot Switching is disabled |
| 0 | 0 | 0 | Case3: Executing in Lock Step Mode Switching to dual boot is *Enabled* Certificate requests to execute in Lock Step Mode Result: R5 will continue to execute in Lock Step Mode |
| 0 | 0 | 1 | Case4: Executing in Lock Step Mode Switching to dual boot is *Enabled* Certificate requests to execute in Dual Core Mode Result: R5 will switch from Lock Step to Dual Core Mode. |
| 1 | 1 | 0 | Case5: Executing in Dual Core Mode Switching to dual boot is *Disabled* Certificate requests to execute in Lock Step Mode Result: Error: Switching from Dual Core to Lock Step is not allowed. |
| 1 | 1 | 1 | Case6: Executing in Dual Core Mode Switching to dual boot is *Disabled* Certificate requests to execute in Dual Core Mode Result: R5 will continue to execute in Dual Core Mode. |
| 1 | 0 | 0 | Case7: Executing in Dual Core Mode Switching to dual boot is *Enabled* Certificate requests to execute in Lock Step Mode Result: Error: Switching from Dual Core to Lock Step is not allowed. |
| 1 | 0 | 1 | Case8: Executing in Dual Core Mode Switching to dual boot is *Enabled* Certificate requests to execute in Dual Core Mode Result: R5 will continue to execute in Dual Core Mode. |
Load Address: The load address will be the address in the system where the image will be loaded. This information is provided and the R5 SBL and HSM Runtime developers need to ensure that the images account for this.
| Value | Description |
|---|---|
| 0x70002000 | R5 SBL Load Address |
| 0x0 | HSM Runtime Load Address |
Image Size: This is the size in bytes of the R5 SBL or HSM Runtime Image to which the certificate has been attached.