Coreboot

Coreboot
Copyright © 2008 Konsult Stuge Copyright © 2008 coresystems GmbH Image and typog · Attribution · source
Name	Coreboot
Title	Coreboot
Developer	Linux Foundation contributors, Google, Chromium OS developers, independent contributors
Released	1999
Programming language	C, Assembly language
Operating system	Linux kernel-based systems, NetBSD, FreeBSD
License	GNU General Public License

Coreboot is an open-source firmware project that initializes hardware and launches operating systems on personal computers, servers, and embedded devices. It replaces proprietary firmware such as BIOS and firmware often provided by vendors like AMI and Phoenix Technologies with a minimal, auditable payload that can hand off control to bootloaders, kernels, or runtime firmware. The project intersects with efforts by organizations such as Google, academic institutions, and independent developers to produce fast, flexible, and secure platform initialization.

History

Coreboot began in 1999 as a response to restrictive proprietary firmware and was influenced by earlier open projects and activists in the free software movement, including contributors associated with GNU Project and Free Software Foundation. Over time, it attracted participation from corporations such as Google during the development of Chromebook hardware and collaborations with community-driven distributions like Debian and Fedora Project. Key milestones include support for modern chipsets from Intel Corporation and Advanced Micro Devices, integration with payloads like Das U-Boot and SeaBIOS, and partnerships with hardware vendors for open hardware initiatives exemplified by Purism and System76.

Architecture and Components

Coreboot's architecture divides firmware responsibilities into board-specific initialization, chipset-specific drivers, and payload handoff. The project integrates with payload projects including GRUB and TianoCore (UEFI implementation by the UEFI Forum community) as well as bootloaders like GRUB and U-Boot to launch kernels such as the Linux kernel or operating systems like Chrome OS. Initialization stages often involve secondary firmware such as TPM modules from manufacturers like Infineon Technologies or secure enclaves such as Intel Management Engine. Board-level support often references design work from companies like ASUS, Lenovo, and Acer Inc. while leveraging open standards from groups like the Linux Foundation.

Supported Platforms and Hardware

Coreboot supports a wide range of architectures, including processors from Intel Corporation x86 families, AMD x86-64 families, and embedded architectures using ARM cores present in devices by NVIDIA and Rockchip. Supported hardware spans consumer notebooks by Dell, HP Inc., and Acer Inc., developer-focused systems from Purism and System76, and server platforms by vendors who collaborate with projects like Open Compute Project. Peripheral controller support covers components by vendors such as Intel Corporation chipset southbridges, Realtek network interfaces, and Broadcom[sic] controllers. Community-maintained porting includes work for Chromebooks manufactured by Acer Inc., Google-branded devices, and custom development boards used by research institutions like MIT.

Firmware Development and Tooling

Development workflows use toolchains including GCC and Clang compilers, assembly tools from GNU Binutils, and build systems like Make and CMake. Testing and continuous integration rely on infrastructures such as Buildbot and Jenkins contributed by corporate and community maintainers. Emulation and debugging employ environments like QEMU for virtual platforms and hardware debuggers including JTAG interfaces supported by tools from Segger and the OpenOCD project. Collaboration and source code management happen on platforms influenced by Git and hosted repositories that echo development practices from projects like Linux kernel.

Security and Verification

Security efforts intersect with hardware security technologies such as Trusted Platform Module chips, Intel Boot Guard, and secure boot concepts advanced by the UEFI Forum. Coreboot integrates with payloads that implement measured boot and attestation services compatible with cloud providers and enterprise systems like Amazon Web Services and Google Cloud Platform. Formal verification and fuzzing efforts draw on research from institutions including University of Cambridge and ETH Zurich, while vulnerability disclosures have engaged coordination with maintainers of Linux kernel and vendor security teams. Hardening techniques include signed payloads, measured launch using TPM PCRs, and reproducible builds encouraged by projects like Reproducible Builds.

Adoption and Use Cases

Adoption ranges from consumer devices in the Chromebook ecosystem to enterprise servers in data centers managed by contributors to the Open Compute Project. Hardware vendors such as Purism ship systems with stock open firmware for privacy-focused consumers, and development boards from vendors like Raspberry Pi Foundation and BeagleBoard communities motivate embedded use. Use cases include secure boot chains for cloud infrastructure, fast boot for kiosks and digital signage by organizations like Intel Corporation partners, and research platforms in academic labs at institutions like Stanford University.

Licensing and Community

The project is distributed under the GNU General Public License, encouraging contributions from companies and individuals, with governance practices influenced by foundations such as the Linux Foundation. The community comprises developers affiliated with corporations like Google and independent contributors collaborating through mailing lists and conferences including FOSDEM and Linux Plumbers Conference. Commercial support and consulting are offered by firms experienced with firmware engineering, and the ecosystem includes projects like Heads and Coreboot-based distributions that extend deployment models.

Category:Firmware