7-9 October, 2026 Prague, Czechia View More Details & Registration Important Note:Timing of sessions and room locations are subject to change.
The Sched app allows you to build your schedule but is not a substitute for your event registration. You must be registered for Open Source Summit Europe 2026 to participate in the sessions. If you have not registered but would like to join us, please go to the event registration page to purchase a registration.
Sign up or log in to add sessions to your schedule and sync them to your phone or calendar.
The last decade has shown a clear trend in dramatically increasing the boot process of modern SoC. If the i.MX6 bootflow reads like a short novel, the i.MX95 or TI K3 bootflow is a whole encyclopedia.
Today's heterogeneous SoCs combine CPUs of different types — Cortex-R/M cores alongside the application-class Cortex-A — and boot now begins on one of the smaller cores before handing control over to the Cortex-A. There are good reasons for this, such as meeting functional-safety requirements, but it is also a real burden for system designers who simply want to run Linux on the Cortex-A cores and make use of the GPU or VPU.
Each new component needs its own firmware: ideally built from open source, though closed-source pieces remain in the chain. The result is no shortage of cryptic acronyms — TF-A, FF-A, TEE, SCMI, PSCI, SCP, FIP.
This talk sheds some light into the dark. It explains what each of these components actually does and how they fit together. Attendees will leave able to map this general picture onto their own SoC, see which parts are open source and which are not, and know where to look when the bootflow misbehaves.
Marco joined the Pengutronix graphics team in 2017. His work covers everything from system architecture to low-level bootloader firmware up to kernel and user-space development.
