</>EmbeddedInterview

How does a Raspberry Pi boot, and how is it different from a typical SoC?

MediumEmbedded Linux & Boot

Short answer: On the Raspberry Pi the GPU (VideoCore) boots first, not the ARM cores. The GPU's ROM loads the boot firmware (on Pi 1–3 bootcode.bin and start.elf from the SD card's FAT partition; on Pi 4/5 a bootloader stored in an on-board SPI EEPROM), reads config.txt, loads the device tree, the kernel (kernel8.img for 64-bit) and cmdline.txt, and only then releases the ARM cores to run the kernel.

Raspberry Pi 3 sequence

  1. Power on: the ARM cores are held in reset; the VideoCore GPU runs its ROM.
  2. GPU ROM reads bootcode.bin from the first FAT partition of the SD card (USB/network boot is possible on later revisions) and runs it from the GPU's L2 cache.
  3. bootcode.bin enables SDRAM and loads start.elf (the main GPU firmware).
  4. start.elf reads config.txt (memory split between GPU and ARM, overlays, arm_64bit, clock settings), loads the DTB for the board plus any overlays (dtoverlay=), loads the kernel image and cmdline.txt, and puts them in RAM.
  5. It releases the ARM cores, which start executing the kernel (optionally via U-Boot if kernel=u-boot.bin). From here it is the normal Linux boot: start_kernel() → mount root (usually the second partition, ext4) → init.

Pi 4 and Pi 5: the first-stage bootloader lives in an SPI EEPROM on the board, can be updated, and supports USB and network boot. bootcode.bin is no longer used.

Differences from a typical industrial SoC

Raspberry Pi Typical i.MX / AM62x / STM32MP
GPU boots first, closed firmware ARM core runs the boot ROM directly
Boot files on a FAT partition boot ROM reads a fixed offset or partition (raw image)
config.txt replaces most bootloader setup SPL + U-Boot (+ TF-A, OP-TEE) do the setup
Secure boot only on newer models (signed boot images) Secure boot with fused keys is standard

Why it matters in an interview: the Pi is the most common board people have used. Being able to say what is different shows you understand which parts are Pi-specific and which are general Linux.