Secure Boot

The Secure Boot feature ensures that only authenticated and trusted firmware runs on the device, protecting it from unauthorized modifications and malicious code. This security mechanism establishes a root of trust and prevents unauthorized firmware from executing. iWave’s Secure Boot solution for i.MX processor’s provides an end-to-end secure boot process, leveraging High Assurance Boot (HAB) and cryptographic authentication to protect firmware integrity and authenticity.

CONTACT SALES

Documents

Datasheet

Features	Details
Signing Process	The Code Signing Tool (CST) generates a hash of the bootloader. A private key signs the hash to produce a signature (CSF – Code Signing File). The signed bootloader, along with the signature, is prepared for secure boot verification.
Verification Process	Boot ROM (Read-Only Memory) contains the High Assurance Boot (HAB) module. During boot, the bootloader and its signature are loaded into memory. The system re-generates a hash of the bootloader. The pre-stored public key (burned into e-Fuse) is used to verify the signature. If the computed hash matches the signed hash, execution continues (Run). If verification fails, the boot process is aborted to prevent untrusted code execution.
Key Features	Cryptographic Signing: The bootloader is hashed and signed using a private key to ensure authenticity. Public Key Storage in e-Fuse: The public key used for verification is stored in an e-Fuse, preventing unauthorized modifications. High Assurance Boot (HAB): A hardware security module (HAB) inside the Boot ROM performs signature verification. Hash Comparison & Authentication: The bootloader hash is recomputed and compared against the signed hash before execution. Failure Prevention Mechanism: If authentication fails, the boot process is aborted to prevent execution of tampered firmware.