Qoriq Trust Architecture 21 User Guide Jun 2026
The TA 21 framework relies on several tightly integrated hardware components working in unison. Understanding these pillars is essential for proper system implementation. Internal Boot ROM (IBR)
: Dictates whether debugging interfaces (JTAG) are open or permanently locked. qoriq trust architecture 21 user guide
+-----------------+ +-----------------------+ +-----------------------+ | Internal ROM | ---> | Validate Command | ---> | Verify Bootloader | | (IBR) Code | | Sequence File (CSF) | | Signature (RSA) | +-----------------+ +-----------------------+ +-----------------------+ | v +-----------------+ +-----------------------+ +-----------------------+ | Execute Secure | <--- | Transition to | <--- | Match Public Key | | OS / Kernel | | Secure State (AS) | | with Fuse Hash | +-----------------+ +-----------------------+ +-----------------------+ Step 1: Power-On Reset (POR) The TA 21 framework relies on several tightly
A multi-stage process that verifies each piece of software in the boot chain before it is launched. For more details, visit NXP Community
The QorIQ Trust Architecture 2.1 User Guide provides essential technical details for implementing silicon-based security, such as Secure Boot and ARM TrustZone, on NXP Layerscape processors. It is a critical, NDA-protected document that enables advanced features like hardware root of trust and runtime integrity checking. For more details, visit NXP Community .
The boot process begins with on-chip ROM code (immutable). The ROM verifies the Pre-Boot Loader (PBL) or Secondary Pre-Boot Loader (SPBL) through digital signatures (RSA or ECDSA). The TA 2.1 user guide details:
The Trust Architecture enjoys robust support within the Linux kernel, evidenced by its integration into mainline drivers. A key example is the update to the nvmem subsystem driver for the . A kernel commit (33a1c6618677) titled "nvmem: sfp: Add support for TA 2.1 devices" explicitly added compatibility for Trust Architecture 2.1 devices. The commit notes that there are few differences between TA 2.1 and TA 3.0, especially for read-only support.
