Main Certificate private key
Type: stringFormat: fileMain Certificate private key used to sign certificate. It can be replaced by signProvider key.
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.
Used for anti-rollback protection. New firmware must have the same or higher FW version. This value is the minimum firmware version will be stored in BCA and the firmware version specified in SBX file is then compared with this value.
life cycle state model to protect code from reading from the device internal flash, which is called code read protection feature. There are different levels of protections in the system, so that access to the on-chip flash and use of ISP can be restricted. Four levels of Read Out Protection (ROP) are supported. This read out protection is a mechanism that allows user to enable different levels of protection in the system. It is a 8-bit field FTFA_FSEC associated with flash security byte (0x40c byte address). It can be programmed by customer. Check the SRM for more information. If not provided, value in application will be used.
Path to certificate block.
Not mandatory if the hash is written in OTP
Main Certificate private key used to sign certificate. It can be replaced by signProvider key.
Main Certificate private key used to sign certificate. It can be replaced by signProvider key.
Signature provider configuration in format 'type=<identifier>;<key1>=<value1>;<key2>=<value2>'.
Build only the boot headers (Vector table, BCA, FCB) 0x0..0x800 binary without the application. This is needed for device HSM provisioning file in case the user set ROP2, ROP3.