0.16 osfc-2024 2024-09-03 2024-09-05 3 00:05 https://talks.osfc.io https://talks.osfc.io/media/osfc-2024/img/oscar_standing_w_b6TdCIH.png Europe/Berlin Main Room Event Info 2024-09-03T09:30:00+02:00 09:30 00:15 OSFC 2024 Opening Event + Open-Source Firmware Foundation Yearly Update osfc-2024-52560-opening-osfc-2024 en false https://talks.osfc.io/osfc-2024/talk/3C98PM/ https://talks.osfc.io/osfc-2024/talk/3C98PM/feedback/ Main Room Lightning Talk 2024-09-03T09:45:00+02:00 09:45 00:15 This talk gives a status update on the current activities of the Open Source Firmware Foundation. osfc-2024-56571-open-source-firmware-foundation-status-update en false Slides https://talks.osfc.io/osfc-2024/talk/YDNVKP/ https://talks.osfc.io/osfc-2024/talk/YDNVKP/feedback/ Main Room Talk 2024-09-03T10:00:00+02:00 10:00 00:30 Discrete TPMs are tamper resistant physical devices containing a cryptographic coprocessor with on-chip secret storage and system state attestation functionality. While making the direct extraction of root key material using physical and electrical means rather difficult, when integrated into systems to provide secret storage, their nature of being external to the main processor opens up these systems to a different class of practical attacks. Most well-known attacks against such systems target the bus between the processor and the TPM using passive sniffing and active interposer techniques (e.g. TPMGenie). In addition to discussing the continued effectiveness of well-known attacks, this talk will highlight a series of less well-known, but still highly practical attacks that focus on subverting the TPM’s knowledge of system state, either via physical means or by taking advantage of software mistakes. These attacks include the recently disclosed “TPM GPIO fail” vulnerability that subverts the TPM’s knowledge of system state purely from software, allowing a software attacker in control of a system in any state to extract secrets sealed by “trusted” operating systems. osfc-2024-52091-practical-pcr-forgery-aka-how-i-will-decrypt-your-laptop Mate Kukri en false Slides https://talks.osfc.io/osfc-2024/talk/NN9H8A/ https://talks.osfc.io/osfc-2024/talk/NN9H8A/feedback/ Main Room Talk 2024-09-03T10:45:00+02:00 10:45 00:30 Learn about the cutting edge work that is happening in verifying isolation guarantees and timer correctness in [Tock OS](https://github.com/tock/tock). Tock is an operating system written in Rust for low-power microcontrollers. You will learn about our progress proving that isolation guarantees are met by the system using formal methods. osfc-2024-51206-provable-security-in-embedded-systems-verification-work-in-tock-os Samir Rashid en I am a graduate student at UC San Diego working on verifying Tock OS, an OS for embedded systems written in Rust. Tock OS is widely used for root-of-trusts. Tock supports process isolation. Verification allows a path to eliminating million dollar bugs and make sure your system behaves the way you expect. Formal methods are going to make sure that we can trust systems. We show that verifying your software is possible with low line-of-code overhead. Testing code such as timers/alarms is very error prone and requires invasive instrumentation or imagining every possible edge case. I will show how you can statically analyze your code with formal methods. At compile time, you know your code does not violate any properties and works correct in every possible execution. I will show you some crazy bugs I have discovered in timing code that can be completely eliminated. Content of the talk: - What is Tock OS - OS for resource contrained systems (microcontrollers) written in a high level language - used in industry by [Google](https://security.googleblog.com/2020/01/say-hello-to-opensk-fully-open-source.html), HP, WD - Software Verification is here - Now is the time for verifying our systems are safe. We are using [Verus](https://github.com/verus-lang/verus) and [Flux](https://github.com/flux-rs/flux) to *prove* that system guarantees of isolation and correctness are met. - Verifying properties of our Rust OS has low overhead and does not require reimplementing the whole system. Rust+verification eliminates memory errors and logic errors for critical systems such as the root-of-trust use case. - Our Approach - Examples of bugs caught - Developers have more confidence in implementing optimizations and accepting code changes in PRs. - I have found bugs that are virtually impossible to find by reading the code. We will take a look at previous security bugs in Tock, how we came up with system properties to verify, and show how these problems are now impossible produce. - Some technical explanation on how verification works and the methods we have used. - Verification - Formal methods have been coming for a long time, and they are here to stay. With our work, I hope to show that proving system properties is doable for a microkernel. I will show our future work and paths for current software to become more safe and more understable via formal methods. - Tock is open source! Freely use it for whatever you want. false View slides on the web OSFC 2024 - Compile time techniques for safer firmware by Samir Rashid.pdf https://talks.osfc.io/osfc-2024/talk/WGG9AH/ https://talks.osfc.io/osfc-2024/talk/WGG9AH/feedback/ Main Room Talk 2024-09-03T11:45:00+02:00 11:45 00:30 The concept of virtualization is almost as old as computer science itself, with a rich history of intertwined software and hardware evolution. Today virtualization is ubiquitous, and serves as the building block of software deployment and isolation. This talk explores a wild idea: what if we tried to virtualize the firmware? Is it possible? What does virtualizing the firmware even mean? How can it be useful? While we walk down the memory lane answering those questions, we will rediscover old theorems, clever software tricks, and the limitations of hardware. We will explore the virtualization of M-mode firmware on RISC-V, and present the design of Miralis, a security monitor that virtualizes RISC-V firmware. osfc-2024-50083-everything-old-is-new-again-virtualizing-firmware-on-risc-v Charly Castes en This talk explores the idea of virtualizing firmware: running firmware in a less privileged, sandboxed environment. While virtualization is now a well understood concept, it is still restricted to higher privilege modes. In this talk we explain how we leveraged insight from the past to build, test, and partially verify Miralis, a security monitor that virtualizes RISC-V firmware. Starting with Popek and Goldberg’s requirement for virtualization, we define the three properties of virtual machines: equivalence, isolation, and efficiency. We explain the hardware requirements to support simple and efficient virtualization through trap & emulate, the consequences of violating those requirements, and how it relates to firmware executing on modern architectures. We then describe Miralis, our prototype security monitor that virtualizes M-mode on RISC-V platforms. We give insights into our ongoing attempt to (partially) verify the equivalence and isolation properties by leveraging the executable RISC-V specification and symbolic execution. Finally, we conclude with use cases for which firmware virtualization could be useful, such security, debugging, and consolidation. false https://talks.osfc.io/osfc-2024/talk/WXURD7/ https://talks.osfc.io/osfc-2024/talk/WXURD7/feedback/ Main Room Talk 2024-09-03T13:30:00+02:00 13:30 00:30 Despite being a vital component of every computing stack, system firmware has been mostly obscure and inaccessible to academic researchers for several decades. With the advent of open-source firmware implementations for major platforms in the consumer and datacenter spaces, new possibilities for researchers arise. Crucially, most works so far focused on security aspects, as vulnerabilities and supply chain attacks at the firmware level can have devastating implications for users and businesses alike. In this talk, I want to shed light on how other areas of systems research can benefit from open-source firmware by sharing some of the the work-in-progress efforts being done at our operating systems research lab at Karlsruhe Institute of Technology (KIT). I will begin with insights and experiences from our own homegrown port of coreboot to an off-the-shelf mainboard based on Intel's current-gen server platform. Then, I will present how we leverage this implementation to explore and implement novel ideas around system suspend and Compute Express Link (CXL) that would be impossible to build without firmware modifications. osfc-2024-51195-how-open-source-firmware-enables-new-opportunities-in-systems-research Yussuf Khalil en false Slides https://talks.osfc.io/osfc-2024/talk/ZUYFLB/ https://talks.osfc.io/osfc-2024/talk/ZUYFLB/feedback/ Main Room Talk 2024-09-03T14:15:00+02:00 14:15 00:30 Historically BMC firmware always needed special care by DevOps and SREs but does that have to be the case? In this talk we will explore a way to turn your data centers BMCs into yet another software component and demystify the whole management stack of modern server hardware. osfc-2024-51046-leveraging-nats-and-opentelemetry-in-u-bmc-for-enhanced-data-center-operations Marvin Drees en This talk will cover new design decisions made in u-bmc which aim to cover common shortcomings looking at server management not from an OxM or manufacturer perspective but rather from an end users of such stacks which often are data center DevOps and SREs. We will cover the development that happened in u-bmc since the last talk at OSFC 2022 and how NATS and OpenTelemetry, two technologies alien to average embedded systems, can play a role in current and futures data center management and monitoring at scale. While NATS is more known from high speed trading systems, deployed in Nascar telemetry systems or used by the Matrix chat servers, it showed properties that made it an ideal choice for connecting embedded systems like BMCs inside a larger installation. And while Redfish is a great standard to cover hardware management capabilities it feels very different from how regular cloud workloads are monitored. By adding OpenTelemetry monitoring capabilities into the BMC firmware it turns the BMC and therefore the servers hardware into yet another service to monitor from an SREs point of view. false https://talks.osfc.io/osfc-2024/talk/9WKR7E/ https://talks.osfc.io/osfc-2024/talk/9WKR7E/feedback/ Main Room Talk 2024-09-03T15:30:00+02:00 15:30 00:30 How do you write maintainable firmware for rapidly evolving open source silicon designs? This is the challenge developers contributing to the OpenTitan project have faced as the open source silicon root of trust has reached maturity. In this talk we'll cover some of the obstacles we have overcome as the project has progressed — including some challenges that are unique to open source silicon projects. osfc-2024-51400-open-source-all-the-way-down-developing-firmware-in-parallel-with-open-silicon James Wainwright en OpenTitan is an open source silicon root of trust project that includes silicon designs, verification, firmware, and integration tests. We have been developing OpenTitan's firmware in parallel with its silicon designs and have encountered several challenges that come from building execution environments to approximate how the real silicon will behave. Simulations, FPGAs, and now engineering sample silicon, are each used for different kinds of tests and each have their own trade-offs. In order to test the firmware in CI against these platforms in the open, we have had to solve problems around resource-demanding jobs, proprietary tooling, and using specific and sometimes bespoke hardware. This talk will cover some of the issues we have faced testing OpenTitan's firmware, our current solutions to these problems, and where we would like to see progress in the future based on what we've learned. We hope that sharing our knowledge will contribute toward an ecosystem of open silicon projects. false Slides https://talks.osfc.io/osfc-2024/talk/XJBD9Y/ https://talks.osfc.io/osfc-2024/talk/XJBD9Y/feedback/ Main Room Orga 2024-09-03T16:15:00+02:00 16:15 00:10 Bochum has emerged as the "place to be" for IT security due to its unique combination of top-tier research, innovative companies, and a vibrant start-up scene. The city is home to the Horst Görtz Institute for IT Security at Ruhr University Bochum, one of Europe's leading research centers in this field. This academic excellence attracts top talent and fosters strong collaboration between academia and industry. Additionally, Bochum actively supports both startups and established companies in the cybersecurity sector, making the city a key hub for IT security in Germany. This talk highlights the top-tier research opportunities within Bochum and show-cases the ecosystems the companies within the region built together making in 'the place to be' for Firmware Security Research and Development. osfc-2024-55342-bochum-the-hub-of-firmware-security-innovation-and-collaboration Thomas Wollinger en false https://talks.osfc.io/osfc-2024/talk/ZZRY8T/ https://talks.osfc.io/osfc-2024/talk/ZZRY8T/feedback/ Main Room Talk 2024-09-03T16:25:00+02:00 16:25 00:30 The cost of taping out a System on Chip (SoC) typically can range from $2 to $3 million and varies depending on the process node, size, complexity and the services required. All the SOC design companies aim for timely tape out with Zero silicon bugs however in reality most of the chips required multiple iterations before final delivery to customers. Program failure can have a severe impact on a company. It can lead to financial losses, and customer dissatisfaction, and can even damage the company's reputation. It can lead to a lack of trust in the company's products or services. In addition to design issues, if the software that runs on the SoC, is not developed with the mindset that it should run on the SoC on the first day the chip is taped out, the probability of program failure and overall cost increases. Having worked with several ARM based Silicon vendors and on different Silicon bringup strategies - which includes running bootloaders, secure firmware, rich OS like Linux, or RTOS like FreeRTOS, I can share some success stories using solid strategies to get software setup before the actual Silicon is ready. Open source software and firmware plays a critical role in getting such pre-silicon software ready - as one can reuse existing code, try it on pre-silicon emulation or simulation platforms and even upstream the early boot-up code. I will share an example of how I worked on enabling Freescale based silicon bringup code for a 0-day bringup, which included running das u-boot bootloader, secure firmware (ARM trusted firmware), Linux and a simple networking user-space application on the very first day the Silicon was taped out from fab. I will also share how simulator based early software development was done for the same (e.g. <https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/freescale/fsl-ls2080a-simu.dts#L7>). Contributing support for a new upcoming Silicon platform back to upstream allows us to use open-source software directly during Silicon + board bringup, thus de-coupling the requirement of the actual bringup site being co-located with the geography where the fab is located (for 0-day bringup). I will also share the challenges normally faced while doing the same and how we can possibly leverage open-source software advocacy for working around these. I will also share some best practices one can employ while choosing the right simulator or emulator model(s) for pre-silicon testing of boot software, especially if we want to boot all the way upto linux / android userland. osfc-2024-50288-getting-your-open-source-software-ready-for-0-day-soc-bringup-success-stories-and-strategies Bhupesh Sharma en false https://talks.osfc.io/osfc-2024/talk/RTZFTM/ https://talks.osfc.io/osfc-2024/talk/RTZFTM/feedback/ Main Room Talk 2024-09-03T17:10:00+02:00 17:10 00:30 System Firmware - the most undervalued software component of any hardware, is always left behind in the pursue of free and open source software solution that enable us all. Open source firmware made some significant momentum starting with coreboot and U-Boot about 25 years ago. In the field of host firmware, one of monumental changes came when Chromebook started adopting coreboot as its host firmware, bringing a more secured, lightweight, resilient yet open host firmware to 100 millions of devices over the world; yet - almost rest of consumer laptops are plagued with locked-down and highly restricted of host firmware in their users hand. In comparison to other software community such as Linux, open source firmware community is significantly much smaller, yet highly fragmented into different community projects which rare interactions with each others, while all sharing the same goal - to promote a healthy open source firmware ecosystem. In this talk, we will explore the nature of open source firmware community - its ugliness and beauties, the conflicts and compromises. In the mist of all these, there are many unsung heroes that made huge sacrifices for the greatness of open source firmware community. We will share some behind-the-scene stories, some cross-communities and collaboration efforts hoping to share knowledge and experience to drive a better open source firmware community ahead. In reflecting the past and present mistakes and progress made, hopefully, the time has come for us to usher into a much better open source firmware era - for a more sustainable and transparent firmware for all. osfc-2024-52255-it-takes-time-building-bridges-and-symphony-among-fragmented-open-source-firmware-community Lean Sheng Tan en false https://talks.osfc.io/osfc-2024/talk/H8KMQT/ https://talks.osfc.io/osfc-2024/talk/H8KMQT/feedback/ Main Room Event Info 2024-09-03T17:55:00+02:00 17:55 00:05 . osfc-2024-55441-wrapping-up-tuesday en false https://talks.osfc.io/osfc-2024/talk/KYBNAY/ https://talks.osfc.io/osfc-2024/talk/KYBNAY/feedback/ Main Room Event Info 2024-09-04T09:20:00+02:00 09:20 00:10 . osfc-2024-55624-opening-2nd-day en false https://talks.osfc.io/osfc-2024/talk/FWT7WC/ https://talks.osfc.io/osfc-2024/talk/FWT7WC/feedback/ Main Room Talk 2024-09-04T09:30:00+02:00 09:30 00:30 Talk about adding new platform, SoC, architecture and endianess to coreboot with all its challenges. osfc-2024-51219-enabling-coreboot-on-talos-ii-platform Krystian Hebel en In a world when it gets harder and harder to even start executing instructions on main CPU without some kind of blob, OpenPOWER gives hope for open-source enthusiasts. Talos II is an example of OpenPOWER platform, stuck somewhere between server and PC. While it already has open-source firmware, that didn't stop us from adding support for it to coreboot. This subject was already presented on numerous occasions (OSFC 2020, OpenPOWER Summit 2020 and OpenPOWER Summit 2021), but this time it is done by someone who spent significant amount of time working on that code, so the talk will be depicted from more technical point of view. This presentation will compare existing open firmware stack with coreboot. Some parts of the existing firmware (code that runs on on-chip microcontrollers, because SoC is much more than just the main, OS-visible cores) are reused by coreboot. Those will be briefly described, along with how coreboot interacts with them and what debugging options are available. Obstacles (not always technical) encountered along the way and how we dealt with them will also be discussed. To sum things up, current status of upstreaming process will be presented. false Slides https://talks.osfc.io/osfc-2024/talk/FP7XRR/ https://talks.osfc.io/osfc-2024/talk/FP7XRR/feedback/ Main Room Talk 2024-09-04T10:15:00+02:00 10:15 00:30 Unlike the traditional BIOS that operates in 32-bit mode, LinuxBios (now known as coreboot) switches to 32-bit mode almost immediately. It was previously considered progressive to write firmware in 32-bit protected mode using C. However, even though AMD released the AMD64 extension in 2003, introducing 64-bit or long mode, coreboot remained in 32-bit mode. This was adequate for coreboot's responsibility for limited hardware initialization. Nevertheless, it now shows signs of confinement, and adapting to long mode should be considered, especially as Intel plans to phase out 32-bit mode with X86S. This presentation will outline the key achievements in enabling long mode on coreboot, challenges encountered, and made design decisions. It will conclude with some metric analysis and a glimpse into future silicon plans. osfc-2024-50783-x86-coreboot-with-long-mode-where-are-we-at-and-where-are-we-going Arthur HeymansPatrick Rudolph en false https://talks.osfc.io/osfc-2024/talk/DRMM3E/ https://talks.osfc.io/osfc-2024/talk/DRMM3E/feedback/ Main Room Talk 2024-09-04T11:30:00+02:00 11:30 00:30 TamaGo is an Open Source operating environment framework which aims to allow deployment of firmware for embedded ARM/RISC-V devices by using 0% C and 100% Go code. The goal is to dramatically reduce the attack surface posed by complex OSes while allowing unencumbered Go applications. TamaGo is a compiler modification and driver set for ARM/RISC-V SoCs, which allows bare metal drivers and applications to be executed with pure Go code and minimal deviations from the standard Go runtime. The presentation explores the inspiration and implementation of TamaGo as well as providing real world applications that benefit from a pure Go bare metal environment. TamaGo allows a considerable reduction of embedded firmware attack surface, while maintaining the strength of Go runtime standard (and external) libraries. This enables the creation of HSMs, cryptocurrency stacks and many more applications without the requirement for complex OSes and libraries as dependencies. osfc-2024-48331-tamago-bare-metal-go-for-arm-risc-v-socs Andrea Barisani en false Slides https://talks.osfc.io/osfc-2024/talk/TFNAJZ/ https://talks.osfc.io/osfc-2024/talk/TFNAJZ/feedback/ Main Room Talk 2024-09-04T12:15:00+02:00 12:15 00:30 Rust is becoming one of the most popular languages for firmware development as an alternative to C. Its primary advantage is the compiler's ability to enforce memory safety at compile time, significantly reducing memory corruption bugs that can lead to critical vulnerabilities. In addition, Rust allows unsafe operations, balancing safety with flexibility. However, ensuring safety in complex code, especially when handling memory operations from devices such as MMIO, remains a challenge. Furthermore, the Rust compiler cannot verify the correctness of code logic, leaving developers responsible for writing correct code. While unit and integration testing can help identify bugs, they do not guarantee correctness. In this talk, I will explore existing methods for addressing these challenges, particularly in the context of firmware development. I will demonstrate their application not only through simple examples but also by applying them to a practical project: the Rust Hypervisor Firmware. This firmware, written in Rust, aims to boot a guest OS using a Linux boot loader specification or a UEFI-compatible layer in a virtual machine. By examining this real-world example, the talk will provide practical insights into effectively using Rust for firmware development. osfc-2024-52239-firmware-in-rust-more-than-just-rewrite-it-in-rust Akira Moroo en false Slides https://talks.osfc.io/osfc-2024/talk/YUHZNA/ https://talks.osfc.io/osfc-2024/talk/YUHZNA/feedback/ Main Room Talk 2024-09-04T14:00:00+02:00 14:00 00:30 Since the creation of LinuxBIOS in 1999, open-source firmware (OSF) solutions have increased its footprint first in HPC and Linux-based mission-critical applications, to now many general-purpose compute platforms, such as networking servers, industrial embedded controllers, to client devices. Notably, Chromebook and a few Cloud-based servers, are quite successful products today. Despite its success, Cloud Service Providers (CSP) are mostly on the sideline even though they have the best usage cases for OSF solutions. Why is OSF good for CSP? For one reason, these hosts are more like embedded systems than traditional servers because once they enter data centers, the servers are not open for expansion of modification. As there is no expansion possibility, there is no need for plug-and-play capability, no driver dependency algorithm needed, some even disable USB and any external ports, and there is no need to upgrade memory, PCI devices, or CPUs beyond typical repairing jobs. Since security is the number one focus of CSP, the smaller the size of the source code, the more secured it is. Over the years, many enthusiastic developers are watching the development of OSF, but they see the community lacking of focus on the right things for CSP. In this talk, the speaker is going to go over these areas and share what the optimal OSF features are for CSP. osfc-2024-54679-what-csp-servers-need-from-open-source-firmware-solutions Jiming Sun en There have been a couple significant firmware evolutions in x86 PC/server spaces from assembly language to C, from monolithic thread to a dependency-based driver loading algorithm, and AGESA, FSP to aid the developers who do not have access to privileged information. Amazon AWS firmware teams have been paying attention to and experimenting these ideas since its formation in 2016. AWS did a few pathfinding projects, and some of them were shared with OSF community in the past events, such as using SeaBIOS as CSM on real hardware (with contribution back to the community), and a TinyLinux in BIOS leveraging LinuxBoot initiative. We have successfully booted to OS on several internal platforms, but we did not deploy the solution. Why? In this talk, we are going to discuss some of the reasons, and we like to collaborate with the OSF community to advance CSP-focused system firmware solutions with simplicity, modularity, and security in mind. false https://talks.osfc.io/osfc-2024/talk/G8RDEX/ https://talks.osfc.io/osfc-2024/talk/G8RDEX/feedback/ Main Room Talk 2024-09-04T14:45:00+02:00 14:45 00:30 We will cover in that talk various ways to start an HPE ProLiant server in a flash less mode (aka boot from the network at the BMC level and gathering everything from the network) with OpenSource Firmware osfc-2024-50223-building-a-flash-less-firmware-infrastructure Jean-Marie Verdun en We will demonstrate how we could consider the BMC firmware as being an O/S and use the associated relevant tools to manage that initial firmware stack through network booting, in the intent to expand supply chain security. We will emphasis on OpenBMC implementation, and how we changed the bootflow to successfully boot the BMC by using a full network block storage device, and provide continuous updates capabilities to lower downtime and enhance security by easing deployment process. We will focus on the security aspect by leveraging SiROT and linux LUKS technologies. We will also open the door to hardware modification as to reach a total flash less system design based on OpenSource firmware. That talk is going to be technical and requires a good knowledge of the linux stack. It is a common talk with OVHCloud an openbmc community member. A live demo will be run during the presentation as to demonstrate the full stack. false Slides https://talks.osfc.io/osfc-2024/talk/9ZZZGT/ https://talks.osfc.io/osfc-2024/talk/9ZZZGT/feedback/ Main Room Talk 2024-09-04T16:00:00+02:00 16:00 00:30 AMD has an enduring commitment to advance the state of the art through contributions to open-source firmware and software. As such, this presentation aims to provide an in-depth look at AMD's long-term open source firmware strategy, focusing on the evolution of the AMD openSIL project, a high level overview of validation and quality assurance processes, and the expansion of AMD’s presence in Tianocore. We will discuss: the addition of AMD openSIL features in the AMD EPYC™ Genoa and Turin POC and early POR project phases; the effort of validating and upstreaming AMD openSIL and its supporting Host FW; and how this fits into AMD's overall strategy for releasing firmware in the future. By providing insight into AMD’s long-term commitment and plans for open source firmware, we aim to foster understanding and collaboration within the open source firmware community. osfc-2024-51111-amd-s-long-term-strategy-for-open-source-firmware-from-concept-to-implementation Paul Grimes, PMTS FW Engineer – AMD Server Firmware en false AMD's Long-Term Strategy for Open Source Firmware: Slides https://talks.osfc.io/osfc-2024/talk/KXJ9SN/ https://talks.osfc.io/osfc-2024/talk/KXJ9SN/feedback/ Main Room Talk 2024-09-04T16:45:00+02:00 16:45 00:30 The Management Controller Transport Protocol (MCTP) defines a mostly-hardware-neutral way of messaging between components of an embedded platform. There has been a lot happening in MCTP support for Linux recently, as well as infrastructure and libraries for use in non-Linux embedded systems too. This talk covers the current status of MCTP support in the upstream Linux kernel, what hardware transport options are available, plus other facilities useful for incorporating MCTP into an open source firmware stack. osfc-2024-51320-open-source-platform-communication-with-mctp Jeremy Kerr en MCTP gives us a fairly lightweight protocol definition, which can be abstracted to a range of different hardware packet transports. This gives us a convenient way to implement message-based communication between components of an embedded system, handling endpoint addressing, message fragmentation and reassembly, request-to-response correlation and multiplexing different upper-layer protocols. While this is mainly targeted for "management controller" platforms - typically a Baseboard Management Controller (BMC) and the devices it manages - the lower-layer protocol is suitable for carrying messages of any type. This could be handy for all sorts of embedded communication mechanisms! Linux kernel support for MCTP landed in v5.15, providing a simple sockets-based interface to MCTP messaging with platform devices. Since then, new features and hardware transports have been added, allowing MCTP communication over i2c, serial and i3c, with some new transports landing soon. There are also a number of other projects that provide support for MCTP - including userspace utilities for the kernel stack, upper-layer protocols that use MCTP for messaging, userspace MCTP stacks, and repositories suited for lower-level embedded MCTP implementations. This talk will provide a brief overview of MCTP, and the current status of support for MCTP in the open source ecosystem, some implementation hints, and some quirks to be aware of along the way. false Slides PDF https://talks.osfc.io/osfc-2024/talk/MUT3SC/ https://talks.osfc.io/osfc-2024/talk/MUT3SC/feedback/ Main Room Talk 2024-09-04T17:30:00+02:00 17:30 00:30 This talk will provide a brief overview of adapting OpenBMC for NVIDIA platforms, highlighting the unique challenges, learnings, and solutions. It will be an opportunity to see if this resonates with the community and can be converted into opportunities for collaboration. NVIDIA has enhanced the telemetry stack for efficient power and thermal control using alternative IPC infrastructures, such as shared memory. This enhancement enables faster responses to Redfish metric report URI requests. Standards-based out-of-band (OOB) management is a key requirement for NVIDIA platforms. NVIDIA has upstreamed and enhanced the PLDM Type 5 (T5) stack to handle non-PLDM devices, debug tokens, staged firmware updates, and more. We have also added the majority of PLDM Type 2 (T2) stack features. osfc-2024-55034-adapting-openbmc-for-nvidia-platforms-challenges-and-solutions Tom JosephDeepak Kodihalli en false Slides https://talks.osfc.io/osfc-2024/talk/KA3ZWC/ https://talks.osfc.io/osfc-2024/talk/KA3ZWC/feedback/ Main Room Event Info 2024-09-04T18:15:00+02:00 18:15 00:15 . osfc-2024-55442-wrapping-up-wednesday en false https://talks.osfc.io/osfc-2024/talk/9RTPHB/ https://talks.osfc.io/osfc-2024/talk/9RTPHB/feedback/ Main Room Lightning Talk 2024-09-05T10:30:00+02:00 10:30 00:15 In this lightning talk we will introduce you about the Open Compute Project Community in Europe activities and about the Open Platform Firmware state of the project, and how to get involved. osfc-2024-55284-open-compute-project-europe-and-open-source-firmware-foundation-intro-and-collaboration-opportunities Martin L RothPaul Grimes, PMTS FW Engineer – AMD Server FirmwareRaul Alvarez en The Open Compute Project (OCP) community in Europe is rapidly expanding, reflecting a growing interest in collaborative, open-source hardware and software solutions. The OCP, originally launched by Facebook, aims to redesign hardware technology to improve efficiency and sustainability. In Europe, this movement is gaining momentum as organizations and data centers adopt OCP principles to enhance sustainability, performance, reduce costs and ease up the current compliance challenges in the market. A key focus within the OCP ecosystem is Open Platform Firmware (OPF), which plays a crucial role in standardizing and improving server firmware across different platforms. OPF is designed to provide a common firmware interface that enhances compatibility, security, and manageability. The current state of the art in OPF involves advancements in firmware development tools, increased support for diverse hardware configurations, and improved security features to safeguard against emerging threats. As the OCP community continues to innovate, these advancements are set to drive further progress in open hardware and firmware solutions across Europe. false https://talks.osfc.io/osfc-2024/talk/W8DRN9/ https://talks.osfc.io/osfc-2024/talk/W8DRN9/feedback/ Main Room Lightning Talk 2024-09-05T10:45:00+02:00 10:45 00:15 Multi-host server platforms got more and more attention in recent time. Although the hardware is available for a couple of years now, the Linux Foundation OpenBMC project has just started to get compatible with multi-host platforms like for example the Yosemite platform. This lightning talk covers some of the latest progress and developments made in OpenBMC, the challenges that we are facing and the future plans. osfc-2024-52196-openbmc-the-state-of-multi-host-platform-support Oliver Brewka en false Slides https://talks.osfc.io/osfc-2024/talk/BV8RFW/ https://talks.osfc.io/osfc-2024/talk/BV8RFW/feedback/ Main Room Lightning Talk 2024-09-05T11:30:00+02:00 11:30 00:15 Operating systems prefer to run with the device-trees matching the kernel to provide an optimal user experience. Selecting the right device-tree file requires both the information about the kernel being booted and the hardware on which the image is running. - The talk provides an overview which different approaches have been implemented and why there is still a gap to solve. osfc-2024-52086-operating-system-provided-device-trees Heinrich Schuchardt en false Slides https://talks.osfc.io/osfc-2024/talk/HMNJS8/ https://talks.osfc.io/osfc-2024/talk/HMNJS8/feedback/ Main Room Lightning Talk 2024-09-05T11:45:00+02:00 11:45 00:15 In May 2024, a group of bare metal infrastructure owners created a conference named “Prem'Day”. The key principle: tech people share their vision and infra experience with peers but also with hardware vendors. This talk will be a summary of the feedback shared during the day - with no surprise, firmware and opensource are among the hot topics. During Prem'Day, the creation of an infrastructure user group was announced. This talk will also present how this entity could be useful for the open firmware community. osfc-2024-50766-prem-day-feedback-on-the-first-infra-on-prem-conference-and-creation-of-a-user-group Erwan Velu en false Slides https://talks.osfc.io/osfc-2024/talk/7GEYTT/ https://talks.osfc.io/osfc-2024/talk/7GEYTT/feedback/ Main Room Talk 2024-09-05T13:30:00+02:00 13:30 02:30 OpenMic - The stage is yours! Hand-in a talk spontaneously on site! osfc-2024-52572-open-mic en Submit your idea here: openmic.osfc.io/osfc24-open-mic/cfp false https://talks.osfc.io/osfc-2024/talk/ZFJ3XG/ https://talks.osfc.io/osfc-2024/talk/ZFJ3XG/feedback/ Main Room Event Info 2024-09-05T16:00:00+02:00 16:00 00:15 . osfc-2024-55443-wrapping-up-thursday en false https://talks.osfc.io/osfc-2024/talk/XQ77VG/ https://talks.osfc.io/osfc-2024/talk/XQ77VG/feedback/ Hacker Room Workshop 2024-09-05T10:30:00+02:00 10:30 02:00 This workshop provides an introduction to coreboot, an wildly used open-source firmware project. Join our workshop and learn coreboot - Beginner to Intermediate - Everyone's welcome! osfc-2024-52573-introduction-to-open-source-firmware-with-coreboot en The coreboot project started since 1998, and has been widely deployed as host firmware, and you can find it running on each and every Chromebook selling today. Participants will gain hands-on experience with coreboot, learning to configure, build, and install it on real hardware. The session is ideal for developers and enthusiasts interested in firmware development and customization. Whether you're an experienced developer or just starting out, there's something for everyone! So don't be shy if you're completely new, we'll be happy to give you an introduction. Still, having some basic knowledge of firmware, Linux or hardware basics will be helpful in your learning process. Objectives: - Understand the basics of coreboot and its components, e.g. booting process and file compositions Learn the process of configuring and building coreboot - Hands-on experience installing/ flashing coreboot on hardware - debugging issues and some customizations - Who Should Attend: Students, Developers, hardware enthusiasts, and anyone interested in learning about open-source firmware. false https://talks.osfc.io/osfc-2024/talk/XEQ33Q/ https://talks.osfc.io/osfc-2024/talk/XEQ33Q/feedback/ Hacker Room Workshop 2024-09-05T13:30:00+02:00 13:30 02:00 We aim to provide seasoned developers with in-depth knowledge and sophisticated skills to harness the full potential of Zephyr. osfc-2024-54346-mastering-zephyr-advanced-techniques-and-best-practices-for-experienced-developers Ritvi Mishra en This session will explore the intricate aspects of RTOS design and implementation, highlighting Zephyr's advanced features and configurations. We will explore its comprehensive support for multi-core processors, advanced scheduling techniques, and intricate memory management. Additionally, we will cover the integration of cutting-edge connectivity protocols, optimization for power efficiency, and leveraging Zephyr's security framework for high-stakes applications.The practical segment of the workshop will guide participants through complex real-world scenarios, focusing on optimizing system performance, customizing Zephyr modules, and implementing advanced debugging and profiling techniques. Attendees will engage in hands-on exercises to build sophisticated Zephyr-based applications, enabling them to tackle performance bottlenecks and ensure robust and secure deployments.Finally, we will delve into the extensive ecosystem surrounding Zephyr, discussing how to contribute to its development, stay updated with the latest advancements, and collaborate with the vibrant community of experts. Participants will gain insights into best practices for maintaining and scaling their Zephyr projects, ensuring long-term success. false https://talks.osfc.io/osfc-2024/talk/ZJSJ8N/ https://talks.osfc.io/osfc-2024/talk/ZJSJ8N/feedback/