+---------------+ Verifies +------------------+ Verifies +------------------+ | On-Chip ROM | -----------------> | Bootloader (U-Boot| -----------------> | Operating System | | (ISBC) | | or UEFI / FIT) | | (Linux Kernel) | +---------------+ +------------------+ +------------------+ Phase 1: Power-On and Initialization The SoC powers up or resets.
“When programming the SFP (Secure Fuse Processor), the OTPMK must be written before enabling the Secure Boot flag. Writing the flag first without a valid key will permanently lock the device into an unrecoverable state.” qoriq trust architecture 2.1 user guide
Before you can begin implementing secure boot on your QorIQ-based system, you must ensure that the target board is prepared: Trust Architecture 2
Before the CPU boots the operating system, it validates the signature of the bootloader. Trust Architecture 2.1 uses NXP's HAB framework to ensure the integrity of the Platform Boot Loader (PBL). 2.3. Trusted State Machine This logic controls the device's lifecycle state: Device can be debugged. Production: Secure boot is enabled, debug is restricted. Secure/Locked: Fully locked down, maximum protection. 2.4. Cryptographic Acceleration (SEC) Production: Secure boot is enabled, debug is restricted
The (also known as Trust 2.1) is a specialized security framework for NXP's QorIQ SoCs, such as the T-series and LS-series. It provides a Hardware Root of Trust through features like Secure Boot, cryptographic acceleration, and tamper detection.