Qoriq Trust Architecture 2.1 User Guide [portable] -

The ISBC uses an RSA public key (stored as a hash in fuses) to verify the digital signature of the initial boot image.

Once fused, this process is irreversible. Incorrectly fused devices cannot be recovered. 4. Verification and Lockout

Security is disabled; unverified code executes freely. Debug interfaces remain completely open. Full debug, no validation required.

Must be in OEM Closed, and all fuses must be verified. Check: Use sec_mon status command in U-Boot: qoriq trust architecture 2.1 user guide

Proving a device is genuine and manufactured by an authorized entity.

⚠️ WARNING: Fuse programming is irreversible. Writing incorrect hash values will permanently brick the processor. Ensure all values are verified via test scripts prior to burning. Step 5: Blowing the Secure Boot Fuse

The hardware compares this computed hash against the permanently blown into the OTP eFuses. The ISBC uses an RSA public key (stored

The Security Fuse Processor handles non-volatile storage via physical One-Time Programmable (OTP) fuses. The SFP houses the , which dictates which public keys are trusted to validate system software, alongside device-specific configuration bits. Cryptographic Acceleration and Assurance Module (CAAM) INTRODUCTION TO QORIQ TRUST ARCHITECTURE

QorIQ Trust Architecture (TA) 2.1 is an evolution of NXP’s security features, designed to integrate seamlessly with ARM TrustZone technology. It is an "opt-in" scheme, allowing OEMs to control tradeoffs in cryptographic strength, debug visibility, and anti-cloning mitigation. Core Objectives

Anchors trust in hardware-fused keys.

The key features—secure boot, secure debug, anti-tamper, run-time integrity checking, and secret key protection—work together to create a comprehensive security solution. The support for key revocation and rollback protection ensures that systems can be updated and secured even after deployment, while the integration with Arm TrustZone provides an additional layer of defense.

If the device unexpectedly enters the "Fail" state, check if the external tamper pins are floating. Unused tamper pins must be tied to their appropriate inactive voltage levels. Security Best Practices

The provides a robust, manageable framework for bringing secure, trusted products to market using NXP Layerscape processors. By understanding and implementing the guidelines in the QORIQTRUST2.1UG , developers can protect their intellectual property, ensure device integrity, and mitigate the risk of modern cyberattacks. Full debug, no validation required

A secure boot architecture is only as safe as its cryptographic keys. TA 2.1 employs a rigorous key hierarchy to separate root manufacturing keys from operational code-signing keys. Super Root Keys (SRK)

Because this architecture involves sensitive security implementations, the and requires a Non-Disclosure Agreement (NDA) with NXP to access. Core Components of Trust Architecture 2.1