Repository navigation
Bootloader Types
BootBench classifies every bootloader by where it starts and what it hands off to. That is the whole test, and it is why two projects that look similar can land in different types.
%%{init: {"flowchart": {"htmlLabels": true}}}%%
flowchart TB
subgraph MONO["Monolithic boot"]
direction TB
B_OS["Operating system"]:::os
B_T3["<b>Type 3</b><br/>Monolithic bootloader<br/><i>U-Boot, MCUboot, barebox</i>"]:::t3
B_HW["Hardware"]:::hw
B_HW --> B_T3 --> B_OS
end
subgraph SPLIT["Staged boot"]
direction TB
A_OS["Operating system<br/>or hypervisor"]:::os
A_T2["<b>Type 2</b><br/>OS bootloader<br/><i>GRUB, shim, systemd-boot</i>"]:::t2
A_T1["<b>Type 1</b><br/>Firmware bootloader<br/><i>EDK II, coreboot, SeaBIOS</i>"]:::t1
A_HW["Hardware"]:::hw
A_HW --> A_T1 --> A_T2 --> A_OS
end
classDef hw fill:#ececec,stroke:#666;
classDef t1 fill:#eef3fb,stroke:#4a6fa5;
classDef t2 fill:#f3f0fb,stroke:#7a5aa5;
classDef t3 fill:#eefbf3,stroke:#4a8f6a;
classDef os fill:#fdf3e7,stroke:#b07a3a;
Boots from hardware and presents a hardware-agnostic interface to whatever runs next. It may load another bootloader or a standalone application, but it does not itself prepare an operating system.
The test: Starts at the reset vector with nothing initialised. Ends by publishing an interface — UEFI Boot Services, the BIOS interrupt table, the RISC-V SBI — and handing off.
14 in the corpus: LakeBIOS, coreboot, edk2, edk2-platforms, firmware-open, hostboot, lbmk, mu_basecore, openbios, openfirmware, opensbi, oreboot, seabios, slimbootloader
Boots from an already-initialised system and prepares an operating system or hypervisor.
The test: Starts with the machine already up. Its job is to find a kernel, load it, and transfer control with the right arguments and tables. This is why Type 2 bootloaders are configuration-driven and often scriptable.
28 in the corpus: CloverBootloader, MiniVisorPkg, OpenCorePkg, aboot, bootboot, bootloader, chameleon, depthcharge, easyboot, grub, ipxe, kexec-tools, limine, linuxboot, lk, lk2nd, open-iscsi, petitboot, quibble, refind, shim, skiboot, syslinux, systemd, tboot-mirror, tosaithe, u-root, x86-bootloader
Combines both jobs: boots directly from hardware into an operating system with no handoff between stages.
The test: Starts at reset and ends in the application or kernel. Nothing sits between, so the interfaces a staged boot exposes between stages simply do not exist.
20 in the corpus: Adafruit_nRF52_Bootloader, IMBootloader, STM32duino-bootloader, arduino-variometer, arm-trusted-firmware, barebox, firmware, harmony, katapult, mbed-bootloader, mcuboot, openblt, optiboot, redboot, rustBoot, stm32-mw-openbl, tock-bootloader, trusted-firmware-m, u-boot, wolfBoot
Type 1 and Type 2 chained together are staged booting — modular and hardware-abstracting, at the cost of firmware size and start-up time, and typical of desktops, servers and phones. Type 3 is monolithic booting — smaller and faster but tightly coupled to the board, and typical of IoT devices and microcontrollers.
A few projects genuinely straddle the line, and their pages say so rather than presenting the placement as settled:
- arm-trusted-firmware spans reset to OS handoff, so it is Type 3 here — but in a staged setup where BL33 is U-Boot it behaves as Type 1.
- lk is Type 2 as Qualcomm's aboot, running after the SoC's primary bootloader; on platforms where it is the only stage it is Type 3.
- open-iscsi is boot-path infrastructure rather than a bootloader that transfers control to a kernel. It is the weakest fit in the corpus.