0.5 osfc-2025 2025-10-07 2025-10-10 4 00:05 https://talks.osfc.io https://talks.osfc.io/media/osfc-2025/img/pretaxl_2_fOQ8IYf.png US/Pacific Main Keynote 2025-10-07T09:45:00-07:00 09:45 00:20 This keynote will share a comprehensive overview of Google's journey to a planet-scale deployment of LinuxBoot. We will discuss our broad-strokes deployments across a diverse and extensive hardware fleet, including Intel x86, AMD x86, and Arm servers, as well as switches, storage appliances, IPUs and more. Attendees will gain an unique perspective on the challenges and successes of implementing a unified boot solution at an unprecedented scale. ​Our talk will highlight three core messages. First, LinuxBoot has been successfully deployed and is operating at planet scale, demonstrating its robustness and viability for even the most demanding infrastructure. Second, we will show how LinuxBoot, by leveraging the full power of a Linux kernel, can boot any operating system, providing a flexible and powerful solution that breaks traditional vendor lock-in. Finally, we will delve into the security benefits, showing how LinuxBoot is security-hardened by default, providing a critical layer of trust from the earliest stages of the boot process. This presentation offers an inside look at a transformative project that is redefining how we think about boot firmware in the cloud computing era. osfc-2025-78484-planet-scale-deployment-of-linuxboot-at-google David Hu en false Planet Scale Deployment of LinuxBoot at Google https://talks.osfc.io/osfc-2025/talk/JUR9JU/ https://talks.osfc.io/osfc-2025/talk/JUR9JU/feedback/ Main Keynote 2025-10-07T10:15:00-07:00 10:15 00:20 The UEFI Forum is a technology consortium that champions firmware innovation through industry collaboration of technology leaders, while standardizing an interface that simplifies platform initialization and firmware bootstrap operations. The UEFI Forum’s extensible, globally-recognized Unified Extensible Firmware Interface (UEFI) and Advanced Configuration and Power Interface (ACPI) specifications bring new functionality and enhanced security to the evolution of devices, firmware and operating systems. The specifications also facilitate interoperability between platforms and systems – complying with next-generation technologies. In the State of the UEFI, UEFI Forum President Mark Doran will demystify standardized firmware by providing an overview of the UEFI Forum, a status update on the UEFI and ACPI specifications, the UEFI Forum’s working group structure, Code First approach and EDK2 process. Attendees will learn how current members can become involved in the development of future specifications and how adjacent communities can collaborate with the UEFI Forum. Finally, attendees will learn about key firmware industry updates about security, post-quantum crypto and more. osfc-2025-78483-state-of-the-uefi-a-standardized-approach-to-firmware en false State of UEFI - UEFI 2025 DevCon - Slides https://talks.osfc.io/osfc-2025/talk/SXS7MD/ https://talks.osfc.io/osfc-2025/talk/SXS7MD/feedback/ Main Keynote 2025-10-07T10:45:00-07:00 10:45 00:20 How did 9elements end up to become the biggest Open-Source Independent Firmware Vendor in the world? Probably by accident. osfc-2025-78485-how-to-run-a-company-with-open-source Christian Walter en false Slides https://talks.osfc.io/osfc-2025/talk/LNJAGZ/ https://talks.osfc.io/osfc-2025/talk/LNJAGZ/feedback/ Main Talk 2025-10-07T11:15:00-07:00 11:15 00:30 How do small hardware teams avoid death by iteration? This talk explores how systems engineering tools like Dependency Structure Matrix (DSM), Weighted Decision Matrix, and Tradeoff Studies can help hardware-firmware teams reduce unplanned rework, clarify interdependencies, and make better decisions faster. The talk will explore practical strategies for applying these tools from concept evaluation through firmware release planning. osfc-2025-74994-death-by-iteration Emmanuel Odunlade en Small hardware teams and startups often face tight constraints and hidden iteration loops, and unmanaged change propagation can quietly burn through time, money, and morale. While software teams can often "fail fast," hardware development demands more foresight. This talk shows how systems architecture tools like Dependency Structure Matrix (DSM), Weighted Decision Matrix, and Tradeoff Studies can help teams make smarter decisions early and maintain flexibility without chaos. The talk will walk through real-world examples of: Mapping component dependencies to predict ripple effects of change Evaluating competing concepts with structured decision frameworks Managing features across electrical, mechanical, and firmware domains Prioritizing decisions when architecture isn’t fully frozen It will also touch on how these tools can live inside lean processes, so they don’t slow teams down, but actually help them go faster, more confidently. If you’ve ever had to ship a board revision because a tiny dependency was missed, or found yourself stuck in the purgatory of change propagation while the market moved on, this talk might be for you. false Slide https://talks.osfc.io/osfc-2025/talk/AV9UZC/ https://talks.osfc.io/osfc-2025/talk/AV9UZC/feedback/ Main Talk 2025-10-07T13:30:00-07:00 13:30 00:30 System software development presents a fundamental challenge that every bare metal project must solve: bridging the gap between the processor's minimal boot state and a fully functional execution environment capable of running high-level code. When a processor first transfers control to system software - whether firmware, kernel, hypervisor, or any bare metal application - it operates in a primitive state with no stack, no memory management, and minimal initialization of the processor. This creates an immediate dependency: before any C, Rust, or other high-level language code can execute, developers must craft assembly routines to establish the required runtime environment for the software component. The RISC-V architecture's elegant design philosophy amplifies both the opportunity and complexity of this challenge. RISC-V defines two primary base instruction set architectures (ISA) - RV32I (32-bit registers and addresses) and RV64I (64-bit registers and addresses). As articulated in the RISC-V unprivileged specification[1], the ISA represents "the software visible interface to a wide variety of implementations rather than the design of a particular hardware artifact." It also defines RISC-V Execution Environment Interface (EEI), which standardizes critical aspects of program execution: initial processor state, privilege mode behavior (Machine, Supervisor, and User modes), instruction semantics, and interrupt/exception handling. While this standardization creates opportunities for code reuse and shared expertise across RISC-V projects, the reality is that most projects end up implementing similar runtime initialization routines from scratch. Recognizing this common need, we(Rivos) developed rv-runtime-generator, an open-source Rust-based tool that automates the generation of RISC-V runtime initialization code. Rather than forcing each project to solve the same fundamental problem repeatedly, rv-runtime-generator provides a configurable solution that adapts to diverse system software requirements. This talk will dive into the architectural design of the rv-runtime-generator tool and provide examples demonstrating its application in the rapid development of runtime environments for RISC-V software components. osfc-2025-75066-bootstrapping-risc-v-systems-introducing-rv-runtime-generator Furquan Shaikh en false OSFC Presentation https://talks.osfc.io/osfc-2025/talk/X9DJ8M/ https://talks.osfc.io/osfc-2025/talk/X9DJ8M/feedback/ Main Talk 2025-10-07T14:15:00-07:00 14:15 00:30 dutctl is a command-line utility and service ecosystem for managing test devices in open-source firmware development environments. By providing a unified interface to interact with development boards across different platforms, dutctl eliminates the fragmentation of device management tools that has long plagued firmware development workflows. osfc-2025-78064-announcing-dutctl-a-streamlined-device-management-for-open-firmware-development Jens Topp en ## What is dutctl? dutctl is an open-source command-line tool and service ecosystem designed specifically for managing development and test devices in firmware development environments. It provides a unified interface for interacting with various development boards, test fixtures, and embedded platforms, regardless of their underlying communication protocols or management interfaces. The project consists of: - A command-line client (dutctl) for direct device interaction - A server component for managing remote device access - Device agents that run close to hardware and expose a consistent API - A flexible plugin architecture for extending functionality ## The Problem dutctl Solves Firmware development has long suffered from fragmented tooling. Each hardware vendor typically provides their own management utilities, each with different interfaces, capabilities, and quirks. This creates several challenges: 1. Developers must learn multiple tools and interfaces 2. Automation becomes difficult across heterogeneous device fleets 3. Collaboration is hindered by inconsistent tooling 4. CI/CD pipelines become complex and brittle 5. Device sharing across teams is manual and error-prone dutctl addresses these issues by providing a consistent, programmable interface to diverse hardware, enabling standardized workflows regardless of the underlying devices. ### Who Can Use dutctl dutctl serves several key user groups in the open firmware community: - **Firmware Developers**: Streamline daily development tasks with consistent device control - **QA Engineers**: Build reliable test automation across diverse hardware - **DevOps Teams**: Integrate hardware testing into CI/CD pipelines with per-commit verification - **Open Hardware Projects**: Provide consistent management interfaces for your custom boards - **Educational Institutions**: Simplify device access for students learning firmware development Whether you're working on coreboot, LinuxBoot, OpenBMC, or custom firmware projects, dutctl helps manage your development and test devices more efficiently. ### Key Features 1. **Unified Command Interface**: Control various devices through consistent commands 2. **Remote Device Management**: Access and control devices over the network 3. **Bidirectional Command Streaming**: Real-time interaction with device outputs 4. **Multi-Architecture Support**: Test on different architectures in parallel 5. **Extensible Plugin System**: Add support for new hardware components and protocols 6. **Scalability**: Enable distributed device fleets and team collaboration ### Try & Contribute We invite the open firmware community to: 1. **Try dutctl**: Download and integrate it into your firmware development workflow 2. **Provide Feedback**: Help us refine the tool to better meet community needs 3. **Contribute**: Add support for your hardware platforms and use cases The Code is available on https://github.com/blindspotsoftware/dutctl false Slides https://talks.osfc.io/osfc-2025/talk/7DXCNN/ https://talks.osfc.io/osfc-2025/talk/7DXCNN/feedback/ Main Talk 2025-10-07T15:30:00-07:00 15:30 00:30 This presentation presents a secure alternative to the IPMI lanplus protocol for remote server management, employing an HTTPS interface with WebSocket technology. This design eliminates the need to store plaintext passwords on the BMC, thus mitigating credential leakage risks, and this presentation will demonstrate how this enables completely password-free access to the BMC. By integrating IPMI command passthrough into the bmcweb Redfish implementation, the design reuses Redfish session authentication and privilege models, enabling advanced authentication methods like mutual TLS and SSO. Performance evaluations show that this binary protocol over HTTPS-WebSocket matches native lanplus speed while improving security. The modifications to ipmitool, bmcweb, and ipmid provide a practical, secure, and scalable remote server management solution. The design doc and the implementation are open-sourced and submitted to OpenBMC and ipmitool for review. osfc-2025-71481-ipmi-https-interface-towards-a-password-free-bmc Lei Yu en false IPMI-HTTPS Interface MR to ipmitool IPMI-HTTPS Interface in OpenBMC under review IPMI_HTTPS_Interface_Towards_a_Password-Free_BMC_OSFC_2025.pdf https://talks.osfc.io/osfc-2025/talk/DKWH38/ https://talks.osfc.io/osfc-2025/talk/DKWH38/feedback/ Main Talk 2025-10-07T16:15:00-07:00 16:15 00:30 This talk introduces an open platform and proof-of-concept for developing OpenBMC firmware on Arm servers using the Neoverse Fixed Virtual Platform (FVP). Co-developed by Arm and 9elements, the platform enables early development and validation of BMC features—such as telemetry, RAS logging, and Redfish—before silicon is available. The session highlights system architecture, SBMR-defined interfaces, and key lessons from enabling server manageability in a virtualized Arm environment. osfc-2025-75125-developing-openbmc-firmware-on-arm-servers-using-the-arm-fixed-virtual-platform-fvp Samer El-Haj-Mahmoud en This session presents a virtualized development platform that brings OpenBMC to Arm’s Neoverse Fixed Virtual Platform (FVP). Co-developed by Arm and 9elements, the platform supports early firmware bring-up, testing, and standards validation without requiring physical hardware. The talk covers the high-level architecture, which includes a virtual BMC and an Auxiliary Satellite Management Controller (SatMC), and demonstrates how the platform enables critical server manageability features defined by Arm’s Server Base Manageability Requirements (SBMR), including: - The SBMR-defined side-band interface using MCTP/PLDM - In-band host communication via IPMI and Redfish - Out-of-band Redfish and IPMI access - Use cases such as RAS event logging, boot progress reporting, and telemetry collection The presentation also highlights a hybrid development configuration that pairs the virtual host with a physical ASPEED AST2600 EVK acting as the BMC. Attendees will gain insight into how virtual infrastructure can accelerate OpenBMC development, streamline integration workflows, and validate standards-based manageability features on Arm servers— even before silicon is available. false Advancing server manageability on Arm Neoverse Compute Subsystem (CSS) with OpenBMC Arm SBMR specification OpenBMC upstream - meta-fvp-base OpenBMC on FVP Base and Arm FVP platform https://talks.osfc.io/osfc-2025/talk/VJYNY8/ https://talks.osfc.io/osfc-2025/talk/VJYNY8/feedback/ Main Talk 2025-10-07T17:00:00-07:00 17:00 00:30 This talk presents a behavior-based fault injection approach for OpenBMC firmware. By injecting faults at the I/O layer and using real-world failure models, we enhance grey-box testing coverage without modifying code or restarting services. Leveraging tools like Frida and eBPF, our method enables efficient, interpretable, and cross-environment validation of BMC robustness. osfc-2025-73207-openbmc-behavior-based-fault-injection-testing-method Lei YuJia, Chunhui en This presentation introduces a behavior-based fault injection testing methodology tailored for OpenBMC firmware. In BMC (Baseboard Management Controller) development, a significant portion of engineering effort is devoted to handling abnormal system behaviors. Ensuring stability and robustness under such conditions remains a critical challenge, particularly given the complex reproduction scenarios associated with many OpenBMC-related faults. Traditional testing techniques often fall short in addressing these difficulties. To overcome these limitations, we adopt a behavior-driven approach inspired by fuzz testing. By injecting faults at the I/O layer, we enrich the diversity of grey-box test scenarios. Our methodology begins with constructing fixed fault models derived from real-world failure cases, as recorded in systems like JIRA. These models are then programmatically mutated to expand the coverage of fault types and injection points. A newly developed fault injection toolchain is used to perform comprehensive validation of OpenBMC firmware, with a focus on exception handling and recovery mechanisms. The proposed approach offers several key advantages: - Low Dependency: Faults are injected dynamically at runtime without requiring modifications to source code, service restarts, or firmware reflashing. - High Reliability: Tests are conducted directly on release firmware builds, ensuring result accuracy without altering runtime configurations. - Strong Interpretability: Injection events, timing, and fault models are explicitly derived from known issues, making test results easier to analyze and correlate. - Cross-Scenario Compatibility: The method supports execution across different environments, including QEMU virtual platforms and physical hardware targets. To implement this methodology, we leverage dynamic instrumentation tools such as Frida and eBPF, along with custom-developed scripts. The testing framework supports multiple techniques, including: - Operation-sequence-based fault injection - Log-keyword-based fault triggering - Interception of system libraries and components By leveraging these methods, we can accelerate the iteration and refinement of OpenBMC, thereby substantially enhancing its stability and robustness. false OpenBMC_Behavior-Based_Fault_Injection_Testing_Method_OSFC_2025 https://talks.osfc.io/osfc-2025/talk/WQTKQT/ https://talks.osfc.io/osfc-2025/talk/WQTKQT/feedback/ Main Talk 2025-10-08T09:30:00-07:00 09:30 00:30 Intel® FSP (Firmware Support Package) is a critical component in the silicon bring-up processes, traditionally provided by Intel® as a binary to be integrated with a bootloader of customer’s choice (while source is provided for specific purposes). As the demands of firmware development and enabling evolve, Intel recognizes the need for securing Intel assets like FSP, is more critical than ever. Intel is introducing “Signed FSP and Verified Boot Architecture” to provide integrity protection to Intel® FSP binary. This is the latest addition to the slew of capabilities that are already part of FSP, that will continue to expedite development cycles, enhance co-validation with customers, increase the velocity of deploying fixes in a secure manner and help customers launch products faster into the market. This strategic shift involves significant architectural changes, such as simplifying bootloader – FSP interactions and implementing a robust signing and verification process through Intel's Root of Trust. These advancements not only harden silicon initialization but also enable standalone Intel® FSP updates in-field, offering a more streamlined approach to firmware development and management. In this talk, we will explore the motivations behind Intel's Signed FSP approach and the benefits it provides to Intel’s customers. Attendees will gain insights into how these changes transform the boot flow, reduce integration efforts and help to reassign valuable engineering resources from FSP integration and validation to firmware development. osfc-2025-74545-intel-r-signed-fsp-and-verified-boot Ravi RangarajanSai ChagantyChristian Albrecht en false Intel_Signed_FSP_OSFC2025 https://talks.osfc.io/osfc-2025/talk/XL73DH/ https://talks.osfc.io/osfc-2025/talk/XL73DH/feedback/ Main Talk 2025-10-08T10:15:00-07:00 10:15 00:30 OCP L.O.C.K. (Layered Open-source Cryptographic Key Management) is a multi-pronged effort to strengthen the data confidentiality guarantees of storage devices. The program is centered around the development of an open-source integrated hardware root of trust, built on top of Caliptra, tailored for storage security use-cases. In this talk we present an update on the program, including progress towards a 1.0 release. osfc-2025-72053-ocp-l-o-c-k Jeff Andersen en false OCP L.O.C.K. (OSFC 2025) - Slides https://talks.osfc.io/osfc-2025/talk/APKCKF/ https://talks.osfc.io/osfc-2025/talk/APKCKF/feedback/ Main Talk 2025-10-08T11:15:00-07:00 11:15 00:30 Many people are unaware that open-source firmware is being used in embedded systems for the United States Department of Defense (DoD). For obvious reasons, details about this kind of work cannot be discussed publicly, which is why you don't hear much about it. For the past 8 years SysPro Consulting has been developing boot firmware solutions for Intel-based embedded hardware that has been integrated into various kinds of DoD military equipment, ranging from aircraft to ground vehicles to naval vessels, and more. These boot firmware solutions have been based on open-source projects such as coreboot and Slim Bootloader integrated with Intel's Firmware Support Package (FSP). Working on boot firmware for DoD programs as a supplier within the U.S. Defense Industrial Base (DIB) comes with many unique challenges and requirements compared to working on boot firmware for commercial products. These firmware solutions commonly include unique / out-of-the-box features and requirements that present complex engineering challenges to implement and support. This talk will present many of the differences that come with developing boot firmware solutions for embedded military applications, both from an engineering perspective as well as a business perspective. osfc-2025-72590-using-open-source-firmware-for-embedded-military-applications Jay Talbott en false Slides https://talks.osfc.io/osfc-2025/talk/NSN8YT/ https://talks.osfc.io/osfc-2025/talk/NSN8YT/feedback/ Main Talk 2025-10-08T12:00:00-07:00 12:00 00:30 The European CRA was signed off in December 2024 and will be in full effect in December 2027. The CRA brings in challenges and opportunities for the open-source firmware ecosystem that we want to discuss. First we will give an overview about the timeline of the European CRA - the CRA itself comes into effect into three phases. Each phase brings certain responsibilities that also open-source projects should follow. The CRA also introduces specific terms i.e. open-source stewards. We will dive into the responsibilities of those. In the second half of the talk we will look into the opportunities that the CRA brings. CRA could fuel open-source adoption if handled correctly. We will also lay out where the Open-Source Firmware Foundation can support open-source firmware projects to achieve compliance. osfc-2025-74256-open-source-firmware-under-the-european-cra Christian Walter en false Slides https://talks.osfc.io/osfc-2025/talk/YZMMKG/ https://talks.osfc.io/osfc-2025/talk/YZMMKG/feedback/ Main Talk 2025-10-08T14:15:00-07:00 14:15 00:30 Keyboards are more than mere tools—they’re gateways to productivity and creativity for digital denizens. This talk delves into the world of DIY open source keyboards and the open source firmware that brings them to life. Attendees will explore how building a customized keyboard not only improves ergonomics and efficiency but also showcases the power of open source collaboration. Whether you're building your own keyboard or contributing to firmware codebases, this talk will highlight what’s possible when users take control of the firmware behind the keys. osfc-2025-75173-open-source-keyboards-and-how-to-build-them Henry Lie en false Slides for the talk "Open Source Keyboards and How to Build Them" - OSFC 2025 - Henry Lie https://talks.osfc.io/osfc-2025/talk/7ZADQ9/ https://talks.osfc.io/osfc-2025/talk/7ZADQ9/feedback/ Main Talk 2025-10-08T15:00:00-07:00 15:00 00:30 TamaGo is a framework that enables compilation and execution of unencumbered Go applications on bare metal. This talk covers recent updates of the TamaGo framework which greatly expands its scope and reach, allowing unikernel firmware deployment not only on embedded systems, but also on x86_64 bootloaders and under KVMs. osfc-2025-72824-the-state-of-tamago Andrea Barisani en In recent months the TamaGo framework expanded its support to new targets. This talk explores the TamaGo runtime evolution towards ta "Rosetta Stone" for integration of freestanding Go runtimes within arbitrary environment, whether bare metal or OS supported, such evolution is playing an important role in the upstreaming efforts of TamaGo runtime changes towards the vanilla Go distribution. We will also explore the recently developed support of AMD64 architectures and its applications for unikernel execution under a variety of Linux KVM frameworks as well as under the Unified Extensible Firmware Interface (UEFI). We will cover the tooling, API and expanded deployment scenarios resulting from the AMD64 support, as well as the resulting unified AMD64/ARM/RISC-V runtime API and its advantages in the role of code development cross-firmware and cross-cloud deployments. Finally we discuss the interactions with the u-root project, used to create the go-boot project and the future roadmap to a potential support for a bare metal u-root integration. false TamaGo presentation https://talks.osfc.io/osfc-2025/talk/TZSQVZ/ https://talks.osfc.io/osfc-2025/talk/TZSQVZ/feedback/ Main Talk 2025-10-08T16:00:00-07:00 16:00 00:30 Building on our previous discourse on CSP server firmware requirements at OSFC 2024 in Bochum, Germany, this talk presents a transformative vision for cloud system firmware frameworks and efficiency. With cloud servers functioning as specialized embedded systems in controlled data center environments, we're witnessing a paradigm shift in firmware architecture priorities – where security and operational efficiency supersede traditional expandability concerns. The successful deployment of an open source firmware solution in a major CSP environment in 2024 has validated the possibility of pursuing a smaller and simpler codebase for CSP servers. Combined with technologies like Intel FSP and AMD OpenSIL, we're entering an era of unprecedented flexibility in firmware framework choices. Drawing from AWS's extensive experience, we are exploring an architecture that effectively segregates silicon vendor, ODM, and CSP components while maintaining robust security boundaries. We'll present a novel vision to creating a hardware-agnostic firmware stack that enhances security, maintainability, and enables differentiated cloud services. Additionally, we'll examine the emerging role of AI in accelerating firmware development and validation – a potential game-changer for the industry. This forward-looking session will conclude by setting the stage for next year's deeper exploration of AI-driven firmware innovation, inviting the community to collaborate in shaping the future of cloud infrastructure firmware. osfc-2025-74002-deep-dive-into-the-system-firmware-vision-of-a-csp Jiming SunNandagopal Sathyanarayanan en false https://talks.osfc.io/osfc-2025/talk/3NBSKP/ https://talks.osfc.io/osfc-2025/talk/3NBSKP/feedback/ Main Talk 2025-10-08T16:45:00-07:00 16:45 00:30 Debugging is a crucial aspect of firmware development, particularly when bringing up a new platform or when developing a new feature. However, debugging firmware is challenging because of lack of rich debugging environments typically found in operating system-based systems. Effective debugging not only aids in identifying and rectifying errors but also enhances the overall quality, reliability, and performance of the system. Slim Bootloader supports various debugging techniques and this presentation will delve into a suite of advanced debugging methodologies tailored for SBL, providing developers with a comprehensive toolkit to address and resolve issues during the development phase. We will explore the following techniques: 1. Tracing/Debug Logging: Enabling detailed logging mechanisms to capture and analyze system behavior, facilitating the identification of anomalies and errors. 2. Post Code via Port 80 LED Display: Utilizing hardware indicators to convey system status and error codes, offering a straightforward method for real-time monitoring and diagnostics. 3. Bootloader Shell Interface Utilization: Leveraging command-line interfaces to interact with the system, enabling direct manipulation and examination of system registers, memory and configurations. 4. Source-Level Debugging with Hardware and Software Tools: Employing sophisticated debugging tools to inspect and modify source code, providing deep insights into system operations and facilitating precise error correction. 5. Python-Based Automated Debugging and Triage Tool: Introducing a Python-driven solution designed to automatically diagnose and identify the location in code causing specific issues, streamlining the debugging process and enhancing efficiency. Depending on the complexity and nature of the encountered issue, developers can opt for one or a combination of these methods to effectively debug and resolve problems. This presentation aims to equip participants with the knowledge and skills necessary to leverage these techniques, ultimately fostering a more robust and reliable Slim Bootloader development environment. osfc-2025-75243-debugging-techniques-using-slim-bootloader Ravi RangarajanSachin Kamat en false https://talks.osfc.io/osfc-2025/talk/RDPS8G/ https://talks.osfc.io/osfc-2025/talk/RDPS8G/feedback/ Main UEFI DevCon 2025-10-09T10:15:00-07:00 10:15 00:30 Presenter: Felix Polyudov, AMI UEFI is successfully standardizing OS to firmware interfaces. However, the ever-increasing complexity and diversity of modern platforms introduces new challenges in the firmware space. One of the efforts aimed at addressing some of these issues is spearheaded by the OCP Open Platform Firmware project. The presentation will cover Open Silicon Initialization Interface and Unified Platform Configuration Interface OPF efforts and discuss their effect on the UEFI ecosystem. osfc-2025-79403-uefi-devcon-next-frontiers-in-firmware-standardization-ocp-opf-efforts-and-their-effect-on-uefi en false OPF and UEFI - AMI - Polyudov - Slides https://talks.osfc.io/osfc-2025/talk/7VJKDV/ https://talks.osfc.io/osfc-2025/talk/7VJKDV/feedback/ Main UEFI DevCon 2025-10-09T10:45:00-07:00 10:45 00:30 Presenter: Nnamdi Ajah, Cloudflare At web-scale, managing UEFI configurations across thousands of globally distributed servers from multiple vendors is operationally complex. Inconsistent interfaces, undocumented settings, and different tooling from different vendors lead to inefficiencies and toil. Additionally, Redfish support is often inconsistent across many UEFI firmware implementations. To address these issues, a vendor-neutral tool was developed that can run in either EFI or iPXE shells and integrates with existing configuration management systems like Salt, thus enabling standardized, seamless, large-scale UEFI configuration. This approach improves fleet-wide consistency, reduces human error, removes the need for vendor turnaround to implement settings, and eliminates the need for vendor-specific knowledge—allowing teams to manage firmware settings reliably and efficiently across diverse hardware, from a single interface. osfc-2025-79404-uefi-devcon-web-scale-uefi-configuration-management-for-heterogeneous-infrastructure Nnamdi Ajah en false Web-Scale UEFI Configuration - Cloudflare - Ajah - Slides https://talks.osfc.io/osfc-2025/talk/MAQBK3/ https://talks.osfc.io/osfc-2025/talk/MAQBK3/feedback/ Main UEFI DevCon 2025-10-09T11:15:00-07:00 11:15 00:30 Presenter: Aaron Rossetto, Cirrus Logic What can you do when a customer requirement calls for a DXE driver, but you lack the ability to build a custom platform BIOS to test your driver? You could test the driver from the UEFI Shell, but that doesn’t represent a realistic customer deployment scenario, thus leaving a significant gap in your testing coverage. Using virtualization techniques such as PCI passthrough in conjunction with open source technologies like QEMU (Quick Emulator) and OVMF (the Open Virtual Machine Framework) can facilitate the testing and deployment of a DXE driver in a platform that mimics a customer's system, providing valuable insight into the driver deployment process and a high level of confidence in the quality and stability of the solution. osfc-2025-79405-uefi-devcon-virtualization-for-uefi-dxe-driver-testing-and-deployment-validation Aaron Rossetto en false Virtualization for UEFI DXE - Cirrus Logic - Rossetto - Slides https://talks.osfc.io/osfc-2025/talk/GRGW8S/ https://talks.osfc.io/osfc-2025/talk/GRGW8S/feedback/ Main UEFI DevCon 2025-10-09T11:45:00-07:00 11:45 00:30 Presenter: Alex Matrosov, Binarly & Fabio Pagani, Binarly Bring Your Own Vulnerable Driver (BYOVD) is an attack technique where adversaries install legitimate but vulnerable drivers to bypass security mechanisms, execute arbitrary code, and maintain persistent control over compromised systems. Historically, most attention in this area has been focused on Windows drivers but can this concept be adapted to apply elsewhere? This talk explores BYOVD attacks within the UEFI ecosystem, focusing on their implications for Secure Boot. This defense represents a critical component of boot security as it is designed to maintain the Chain of Trust connecting the firmware to the operating system. Compromising Secure Boot breaks this chain, with significant consequences in terms of security. Our talk presents the first large-scale census of signed UEFI modules drawn from public threat intel feeds and private telemetry. We classify tens of thousands of binaries, build a taxonomy of their privilege boundaries, and map out the dark corners where over-privileged, under scrutinized code lives. In the process we uncover dozens of previously unreported Secure Boot bypasses. We will walk the audience through a real bypass chain, demonstrate live exploitation against a fully patched machine, and show how EDR technologies can be blinded long before their kernel driver loads. We will outline a practical hardening roadmap for firmware vendors, OEMs, and defenders, so that the problems identified during this research can be mitigated and avoided in the future. Finally, we will present insights from recent research on mitigations in UEFI. This research underscores both achievements and challenges, emphasizing the need for wider adoption of mitigations in the UEFI ecosystem. osfc-2025-79406-uefi-devcon-signed-and-dangerous-byovd-attacks-on-secure-boot en false Signed and Dangerous - Binarly - Matrosov and Pagani - Slides https://talks.osfc.io/osfc-2025/talk/R9T8UY/ https://talks.osfc.io/osfc-2025/talk/R9T8UY/feedback/ Main UEFI DevCon 2025-10-09T12:15:00-07:00 12:15 00:30 Presenter: Michael Kubacki, Microsoft A new open-source project called Patina is transforming UEFI firmware from the core up! This session will present how Patina is enhancing firmware safety and reliability starting with a DXE Core written in Pure Rust for ARM64 and X64. We’ll explore Patina's architecture, legacy debt solutions, and status. Looking forward, we’ll examine the roadmap and platform integration details. We aim to inspire you to use Rust and modern tools so we can build the next generation of firmware together. osfc-2025-79407-uefi-devcon-the-patina-uefi-revolution-a-rust-based-approach Michael Kubacki en false Patina UEFI Rust - Microsoft - Kubacki - Slides https://talks.osfc.io/osfc-2025/talk/7JLBKL/ https://talks.osfc.io/osfc-2025/talk/7JLBKL/feedback/ Main UEFI DevCon 2025-10-09T12:45:00-07:00 12:45 00:30 Presenter: Mohamad Saleh, Insyde & Sean Loe, Insyde As firmware becomes an increasingly targeted layer in modern systems, Firmware Capsule Updates are emerging as a critical mechanism for maintaining platform integrity. Firmware Capsule Updates provide a secure, standardized mechanism for delivering critical updates across diverse platform components—from BIOS/UEFI and CPU Microcode to TPMs, storage devices, and advanced security technologies like Intel TDX and AMD SEV. The presentation will highlight how capsule updates provide secure, authenticated, and rollback-protected delivery of firmware updates across diverse hardware, as well as how it is an essential firmware-level component for new technologies such as DMR (Dynamic Microcode Replacement). Attendees will gain insight into how capsule-based delivery simplifies platform maintenance and lifecycle management, enhances security posture, and integrates seamlessly with OS-level interfaces to support scalable and resilient infrastructure. osfc-2025-79408-uefi-devcon-secure-and-scalable-firmware-updates-via-capsules Sean LoeMohamad Saleh en false Secure and Scalable Firmware - Insyde - Saleh and Loe - Slides https://talks.osfc.io/osfc-2025/talk/WTJVWM/ https://talks.osfc.io/osfc-2025/talk/WTJVWM/feedback/ SR1 Lightning Talk 2025-10-09T10:15:00-07:00 10:15 00:15 In a world where trust is built byte by byte, measured boot is fast becoming the foundation of trust in modern systems. But realizing it across a layered, multi-vendor firmware stack is anything but trivial. We’ll take a tour through how Arm is enabling a new level of transparency and integrity weaving together diverse open-source boot-stage components, Trusted Firmware-A (TF-A), EDK2, and Linux, into a cohesive measured boot pipeline. At the heart of this effort is the Firmware Handoff specification, acting as the stitching thread, passing cryptographic measurements, metadata, and control between stages. We’ll trace the flow of measurements from secure world to UEFI to kernel, and explore how Arm’s platform architecture, tooling, and upstream contributions are making this not just possible, but practical. Along the way, we’ll connect the dots to TPM-backed attestation, event logging, and remote verification. Whether you're a firmware developer, security architect, or just a fan of elegant handoffs, join us to see how open firmware is chatting. osfc-2025-75816-stitching-trust-measured-boot-across-open-source-firmware-with-firmware-handoff Prachotan Reddy Bathi en We'll explore how the Firmware Handoff (as defined in the Arm Firmware Handoff Specification https://firmwarehandoff.github.io/firmware_handoff/main/index.html) provides a standardized data structure for passing information between firmware stages operating across different exception levels and execution environments. This talk further dives into how Arm is leveraging the Firmware Handoff Specification to connect key open-source boot components to enable a consistent, end-to-end measured boot flow. The session will include implementation insights from real-world prototypes, discussions on upstream engagement, and how this work integrates with TPM-backed attestation, event logs, and remote attestation. Open source components in focus include the Trusted Firmware-A (TF-A), EDK2, Linux, other standalone libraries and standards that enable this flow. This is a practical talk for those interested in measured boot, firmware architecture, open-source firmware handoff and building measurable trust from the first instruction to the final init. false https://talks.osfc.io/osfc-2025/talk/AU9PHG/ https://talks.osfc.io/osfc-2025/talk/AU9PHG/feedback/ SR1 Lightning Talk 2025-10-09T10:35:00-07:00 10:35 00:15 The Universal Payload Specification (UPL) defines a standardized interface between the Platform Initialization (bootloader) phase—which sets up system hardware—and the Payload phase. In the context of boot firmware, the Payload is the component responsible for initializing the boot media and launching the operating system. The Universal Payload is designed to be both platform-independent and bootloader-independent, enabling a single payload implementation to work across diverse hardware and firmware environments. UPL specifies how to format and pass parameters to the Payload, ensuring interoperability between spec-compliant bootloader and Payload stages. This approach allows Payloads to be distributed independently of board firmware, and by formalizing these interfaces, UPL aims to accelerate board bring-up and simplify the integration of open-source firmware components. This paper will: - Highlight the need for a universal contract, illustrated with real-world examples from ARM, x86, and RISC-V devices. - Detail UPL’s table-driven boot flow and its compatibility with existing device tree and FIT tooling. - Present implementation experience reports for RISC-V platforms using Tianocore as a payload, as well as x86 platforms with SBL and Tianocore. We conclude that: The Universal Payload Specification has the potential to become a foundational element for a fully open, reusable, and verifiable firmware ecosystem, and we outline the remaining challenges and future milestones on this path. Link to the spec: https://universalpayload.github.io/spec/ Upstreamed patches for reference: https://github.com/tianocore/edk2/tree/master/UefiPayloadPkg osfc-2025-75412-an-introduction-and-update-on-universal-payload-specification Guo DongDhaval Sharma en false https://talks.osfc.io/osfc-2025/talk/JD997Z/ https://talks.osfc.io/osfc-2025/talk/JD997Z/feedback/ SR1 Lightning Talk 2025-10-09T10:55:00-07:00 10:55 00:15 Provides insights into complex server setups and discusses solutions for managing them within OpenBMC. osfc-2025-78192-openbmc-more-than-a-board-in-a-box Oliver Brewka en In this lightning talk, I will discuss various server setups that a BMC might need to manage, based on my experience contributing to the OpenBMC project. Many within the industry now encounter systems that are more complex than a basic baseboard within a chassis, which impacts how management solutions are developed and implemented. In a previous talk, I covered multi-host platforms and the specific challenges associated with managing these systems. This presentation will delve further into additional server configurations that are commonly encountered in the field. Understanding these setups is beneficial for guiding feature development in OpenBMC, ensuring it meets the real-world needs of modern server environments. Additionally, I will outline solutions that OpenBMC provides for effectively describing and managing more intricate topologies. These solutions are designed to enhance management capabilities and improve operational efficiency. Attendees will gain a clearer understanding of how OpenBMC can be leveraged to address the complexities of current server systems. false https://talks.osfc.io/osfc-2025/talk/3TSXWW/ https://talks.osfc.io/osfc-2025/talk/3TSXWW/feedback/ SR1 Lightning Talk 2025-10-09T11:30:00-07:00 11:30 00:15 Firmware are everywhere into modern servers, we can easily count hundreds of them, including ROM, BMC, PCIe Endpoints, VRM. Maintaining them is a critical task to ensure security. Unfortunately update process is pretty slow, and finding supported and qualified combinations might be a tough task. We will propose during that talk an approach where firmware are automatically downloaded every time a server starts. We will explore various options and will run some demos based on HPE Proliant systems, and envision future of firmware and impact on such technologies on systems optimization for HPC applications. osfc-2025-75581-flashless-stateless-firmware-addressing-modern-security-through-fast-updates-and-firmware-less-approach Jean-Marie Verdun en false https://talks.osfc.io/osfc-2025/talk/GLT8BN/ https://talks.osfc.io/osfc-2025/talk/GLT8BN/feedback/ SR1 Lightning Talk 2025-10-09T11:50:00-07:00 11:50 00:15 u-root's versatility enables us to deploy memory-safe Go code to small places we need firmware in. But some places are tinier than others, and Go binaries are not generally known for their compactness. The solution for that might be to change your go compiler, from upstream go to tinygo: "a compiler for small places". In this talk, we will show the efforts, achievements, and pitfalls we encountered while enabling u-root builds using tinygo. Furthermore, we will provide an outlook on the near future of tinygo enablement and offer an overview of the remaining roadblocks. osfc-2025-78113-shrinking-u-root-with-tinygo David HuLeon Gross en u-root's versatility enables us to deploy memory-safe Go code to small places we need firmware in. But some places are tinier than others, and Go binaries are not generally known for their compactness. The solution for that might be to change your go compiler, from upstream go to tinygo: "a compiler for small places". In this talk, we will show the efforts, achievements, and pitfalls we encountered while enabling u-root builds using tinygo. Furthermore, we will provide an outlook on the near future of tinygo enablement and offer an overview of the remaining roadblocks. false slides https://talks.osfc.io/osfc-2025/talk/PYG399/ https://talks.osfc.io/osfc-2025/talk/PYG399/feedback/ SR1 Lightning Talk 2025-10-09T12:10:00-07:00 12:10 00:15 In the server host firmware ecosystem, a unified platform configuration format and a host firmware-agnostic configuration change method are essential for ensuring server platform interoperability. This approach aims to reduce redundant efforts required to support various configuration formats and change methods across all open-source host firmware solutions. By eliminating dependencies on traditional platform configuration tools, such as legacy BIOS setup during system boot, we can provide a consistent experience for configuring or deploying server platform configurations across different host firmware solutions." osfc-2025-78094-server-host-firmware-agnostic-platform-configuration-change-method-and-format Paul Grimes, PMTS FW Engineer – AMD Server FirmwareAbner Chang en false OSFC 2025 Oct - Server Host Firmware-Agnostic Platform Configuration Change Method and Format https://talks.osfc.io/osfc-2025/talk/U7ZSRY/ https://talks.osfc.io/osfc-2025/talk/U7ZSRY/feedback/ SR1 Talk 2025-10-09T12:45:00-07:00 12:45 00:30 TamaGo is an open source framework that enables compilation and execution of unencumbered Go applications on bare metal AMD64/ARM/RISC-V processors. The recent development of TamaGo uefi and uefi/x64 libraries allow development of unikernels running under the Unified Extensible Firmware Interface UEFI on AMD64 cores. The go-boot project implements an UEFI Shell and OS loader written purely using the Go language. This presentation explores the uses, advantages and architecture of these projects and their role in innovative UEFI applications development. osfc-2025-80868-developing-uefi-applications-in-bare-metal-go Andrea Barisani en false boot-transparency repository go-boot repository TamaGo on UEFI - OSFC 2025 presentation https://talks.osfc.io/osfc-2025/talk/RLWN7J/ https://talks.osfc.io/osfc-2025/talk/RLWN7J/feedback/ SR1 Talk 2025-10-09T14:15:00-07:00 14:15 00:30 This talk presents a Zephyr-powered OpenBMC(CorelynxV6) with LittleBMC SoC(CMU610) developed by Alibaba Cloud. CorelynxV6 is the first time for OpenBMC powered by Zephyer in the world. It is compatible with all OpenBMC applications, fully supports D-Bus communication, and seamlessly integrates with boost.asio for asynchronous operations. CMU610(Cloud Management Unit) is the first DDRless LittleBMC chip runs OpenBMC sussessfully in the world. CMU610 includes integrated flash memory and PROT support, so no external flash is required for image storage and no dedicated security chip is needed for PROT. This is the total solutions for the AI heterogeneous server, none KVM situation, especially for space‑constrained add‑in card form factors like smart NICs. It will save 80% of system cost, reduce power consumption by 70%, save 60% of system area, and double the number of I3C and ADC interfaces. It's time for us to discuss to setup a OpenBMC working group in Zephyr community and a zephyr working group in OpenBMC community. osfc-2025-81303-zephyr-powered-openbmc-with-littlebmc-soc-is-developed-by-alibaba-cloud Kuiying Wang en false OSFC 2025 - Zephyr-Based OpenBMC with LittleBMC SOC is developed by Alibaba Cloud, Kuiying Wang https://talks.osfc.io/osfc-2025/talk/KQUBPB/ https://talks.osfc.io/osfc-2025/talk/KQUBPB/feedback/ SR2 Workshop 2025-10-09T10:15:00-07:00 10:15 02:00 This hands-on workshop guides attendees through running OpenBMC on a virtual Arm server using the Neoverse FVP. Participants will explore server manageability workflows—including telemetry, RAS logging, Redfish, and IPMI—via side-band, in-band, and out-of-band interfaces. Live demonstrations include sending telemetry over MCTP/PLDM and transferring binary logs using PLDM File I/O. The session also features execution of the SBMR Architecture Compliance Suite (SBMR-ACS) to validate manageability conformance in both virtual and hybrid environments. osfc-2025-75126-hands-on-workshop-running-openbmc-and-validating-server-manageability-on-virtual-arm-servers John Chung en This 60-minute workshop provides hands-on experience with OpenBMC running in a fully virtual Arm server environment using the Neoverse Fixed Virtual Platform (FVP). Co-developed by Arm and 9elements, the platform enables firmware development and standards validation well before physical hardware is available. The session walks attendees through building and launching OpenBMC on a Base FVP (acting as the BMC) that communicates with a separate Neoverse FVP (representing the server host). The host platform includes a Manageability Control Processor (MCP), which acts as the Arm SBMR Satellite Management Controller (SatMC). These virtual systems communicate via simulated side-band and in-band channels using industry-standard interfaces. This workshop focuses on developer workflows and testing, with minimal architectural deep dive. Attendees will: - Launch OpenBMC in a dual-FVP environment - Explore telemetry and RAS logging over MCTP/PLDM - Send live telemetry data to a Redfish client - Use PLDM File I/O to transfer binary crash logs - Exercise Redfish and IPMI interfaces from Linux and UEFI - Run the SBMR-ACS to verify manageability compliance Participants will leave with instructions and open source tools from gitlab.arm.com/server_management/PoCs/fvp-poc and github.com/ARM-software/sbmr-acs, ready to apply them in CI, bring-up, or testing pipelines. If participants would like to run the demonstration independently, participants should either prepare a standard / high-performance Linux laptop, or remotely access their own powerful workstation. The recommended laptop configuration is provided below. Pre-built Image available : https://github.com/gtossk2/2025_osfc_workshop Operating System: Ubuntu 22.04 / 24.02 Processor: Intel i5 / AMD Ryzen 5 (with H-series suffix) Memory (RAM): 32 GB false https://talks.osfc.io/osfc-2025/talk/ENXBAW/ https://talks.osfc.io/osfc-2025/talk/ENXBAW/feedback/ SR2 Workshop 2025-10-09T14:15:00-07:00 14:15 02:00 In the first 30-45 minutes, we will provide an overview of the evolution and current status of the Arm UEFI/ACPI firmware ecosystem and the Arm SystemReady compliance program (a foundation for enabling the installation and boot of generic off-the-shelf operating systems on Arm systems). We will focus on the adoption of Arm system architecture specifications such as BSA, SBSA, and SBBR (UEFI, ACPI, SMBIOS), and examine their roles in enabling the installation and boot of generic operating systems. We will also highlight open platforms and firmware implementations available for development or reference, including support through open-source repositories from Arm and its partners. Following the overview, we will move to a hands-on workshop session that guides participants through the process of validating Arm-based platforms for SystemReady Band compliance. Attendees will learn how to set up test environments, run open-source compliance test suites (ACS), and interpret results aligned with standards such as BSA, SBSA, and SBBR. The session will use an open platform (RPi4, Radxa Orion O6, or Arm Infrastructure FVP) and open-source firmware to demonstrate real-world scenarios, common issues, and best practices. Participants will gain practical knowledge to integrate compliance testing into their development workflows and prepare their platforms for SystemReady band compliance. Equipment (Choose one of the following setups for hands-on activities) 1. An Arm device, a USB stick, a USB serial cable, and a laptop - Participants can bring their own Arm device that uses ACPI/UEFI firmware to follow along with the hands-on activities led by the speaker. - Recommended devices are SystemReady SR/ES certified devices, such as Radxa Orion O6, RPi4, and so on. For a full list, see https://www.arm.com/architecture/system-architectures/systemready-compliance-program/systemready-past-certifications. - The laptop USB port must be unblocked, so we can write the test suite image to the USB stick. 2. A laptop that can run FVP locally or remotely - Participants who prefer to use Infrastructure FVP (emulator) can follow the setup instructions https://developer.arm.com/documentation/102677/0500/Set-up-the-RD-N2-FVP/Set-up-the-host-machine-and-download-the-software-stack?lang=en to set up the FVP on a Linux-based system that can be accessed during the workshop. osfc-2025-74830-arm-systemready-band-compliance-a-hands-on-workshop Sunny Wang en false https://talks.osfc.io/osfc-2025/talk/U97PQH/ https://talks.osfc.io/osfc-2025/talk/U97PQH/feedback/