NXP chip family identifier.
Revision of silicon. The 'latest' name, means most current revision.
Definition if application is Execute in Place(XiP) or loaded to RAM during reset sequence.
Specification of final master boot image authentication.
The path for result binary file.
The input application image to by modified to Master Boot Image.
Specification of Trust Zone configuration file for advanced settings. It could be as YAML TrustZone configuration file as pre-prepared binary TrustZone configuration.
Application loading address in RAM if not XiP, otherwise address of load in XiP.
Image version is used for dual boot. The boot ROM decides which image to boot first based on the image version. It boots the one with the newer image version first, and in case of a failure, it boots the older one.
If true, add additional CRC image that is computed from all data execution mage and optionally TrustZone.
Defines which set is used to authenticate the container.
Which key from SRK set is being used.
The value must be equal or greater than the version stored in fuses or PFR to provide proper rollback protection. For example, on the MCXN556s series, the fuse version is used for rollback protection, where it is joined with the image version to create a firmware version 'fwversion = (imageVersion << 8) | (fuseversion)'. During rollback protection, the firmware version is checked against 'SECUREFWVERSION' in the CFPA page.
Signature provider configuration in format 'type=<identifier>;<key1>=<value1>;<key2>=<value2>' or a private key used for sign the container header. Header can be signed by SRK. The referenced SRK must not have been revoked.
Signature provider configuration in format 'type=<identifier>;<key1>=<value1>;<key2>=<value2>' or a private key used for second sign (PQC only) of the container header. Header can be signed by SRK. The referenced SRK must not have been revoked.
SRK (Super Root key) table definition.
CA Flag is used by HAB to indicate if the SRK is allowed to sign other keys
Table containing the used SRK records. All SRKs must be of the same type. Supported signing algorithms are: RSA-PSS, ECDSA, Dilithium or SM2. Supported hash algorithms: sha256, sha384, sha512, sha3256, sha3384, sha3_512, sm3. Supported key sizes/curves: prime256v1, sec384r1, sec512r1, rsa2048, rsa4096, dilithium3, sm2. Certificate may be of Certificate Authority. Dilithium algorithms are supported just in new type of AHAB container
Must contain a minimum of 4 items
Must contain a maximum of 4 items
Path to SRK Key file.
CA Flag is used by HAB to indicate if the SRK is allowed to sign other keys
Table containing the used SRK Dilithium records. All SRKs must be of the same type. Supported signing algorithms are: Dilithium level 3. Supported hash algorithms: sha3256, sha3384, sha3_512. Certificate may be of Certificate Authority.
Must contain a minimum of 4 items
Must contain a maximum of 4 items
Path to SRK Key file.
The file that contains AHAB certificate. It could be used already prepared binary form signed by SRK, or it is possible to use configuration YAML file of certificate and the AHAB export process it will export it itself.
HASH type of image.
Target core id to select kind of image.