How chipsalliance/caliptra works
Project type and purpose
• Caliptra is neither a web app nor a traditional full-stack project; it is a hardware IP + firmware reference design (Root of Trust for Measurement) intended to be integrated into datacenter-class SoCs. This repository houses governance, documentation, and pointers to code across multiple repos (RTL, ROM, FMC, runtime, subsystem, MCU, DPE, etc.).
File structure
• Top-level items (.github, doc/, README, CONTRIBUTING, SECURITY) revolve around process, docs, and governance.
• There is no source code here; actual implementations live in external repos (caliptra-rtl, caliptra-sw, caliptra-ss, caliptra-mcu-sw, caliptra-dpe, etc.).
• Within doc/: comprehensive spec for Caliptra 1.x and 2.x, FIPS compliance, branding, OCP_LOCK, trademark.
README for additional insights
• Caliptra provides:
• Hardware (RTL) for a RoT block inside an SoC
• ROM: immutable bootloader code
• FMC (First-Stage Controller) firmware
• Runtime firmware for higher-level services (attestation, key management)
• Subsystem MCU and DPE profiles as optional components
• The lifecycle: power-on → ROM → FMC → runtime → external attestation
a. Main components
• SoC (host processor subsystem)
• Caliptra RoT block
• Hardware RTL (crypto engines, state machines, MMIO registers)
• On-chip ROM (bootloader)
• FMC firmware (first-stage code)
• Runtime firmware (attestation, measured boot, key services)
• Optional: DPE environment, Subsystem MCU
• External services
• Attestation verifier (cloud or management controller)
• Identity provisioning authority
• OCP bus interconnect / host agent (access to Caliptra registers via I3C or APB)
b. Relationships & interactions
• On power-on, the hardware RTL vector jumps into ROM.
• ROM performs basic self-tests & hands off to FMC.
• FMC measures subsequent firmware stages, initializes crypto engines, then loads and starts runtime.
• Runtime implements attestation protocols, key wrapping/unwrapping, manifest-based authorization.
• The host/management controller interacts through MMIO or mailbox registers (I3C, APB).
• External verifier polls or requests signed measurements/CSRs.
c. Architectural patterns & design principles
• Layered boot sequence: immutable → measured → attested
• Hardware–firmware co-design: hardware enforces isolation and atomic measurements; firmware drives the logic;
• Principle of least privilege (FMC and runtime run in isolated hardware contexts)
• Modular specifications: separate repos for RTL, firmware (ROM, FMC, runtime), subsystem (MCU), DPE, etc.
d. Key technologies
• Verilog/SystemVerilog RTL for hardware
• Rust/C for firmware (ROM, FMC, runtime)
• MMIO register libraries (caliptra-ureg)
• I3C or APB bus interfaces
• Crypto primitives (ECC, LMS, ML-DSA)
Detail without overthinking
• Break the block into as many logical sub-components as needed (self-test FSM, key vault, mailbox interface, etc.).
• Every piece that plays a role in secure boot, measurement, and attestation.