The Zephyr Developer Summit, hosted under the first-ever Embedded Open Source Summit in Prague, Czech Republic, on June 27-30 included presentations, BoFs, and training designed for real time problem solving and deep discussions. More than 1,300 people registered for the EOSS conference – representing 375 organizations across 56 countries around the globe. Zephyr had 75+ technical sessions (in-person and on-demand) for 3 tracks focused on users of Zephyr, developers contributing upstream, and maintainer-specific topics.
All of the videos from the Zephyr Developer Summit can be found on the Zephyr Youtube Channel. Each week, we’ll highlight a few videos in a blog for easy access. Today, we’re featuring a few sessions focused on dev and architecture best practices including, “A Bridle for Your Kite – Best Practices for Downstream Development with Zephyr,” “Practical Tips to Boost Your Productivity When Using Zephyr,” “How I Fell in Love with Zephyr – a System Architect’s Tale,” “Manifests: Project Sanity in the Ever-Changing Zephyr World,” and “Tutorial: Time-to-Market With Zephyr and Pigweed.”
A Bridle for Your Kite – Best Practices for Downstream Development with Zephyr – Stephan Linz, Senior Embedded Software Engineer at Navimatix GmbH & Tobias Kästner, Staff Engineer at UL Method Park GmbH
With west and the CMake build system Zephyr already offers a lot to address many of the challenges of embedded software development. Rooted in the Open/Closed principle, many of these tools and subsystems can be extended to increase productivity. The Bridle open source project aims to serve as a comprehensive blueprint for the development of embedded software. Teams can use it as a scaffold to implement product specific applications, subsystems and test suites as well as hardware descriptions and documentation. Making use of the available extension points Bridle implements strategies to efficiently migrate to newer upstream versions, prepare contributions for upstream while making sure that those parts meant to be kept private remain so during the entire product lifecycle. Using examples from the Bridle project, the video will explain how to add useful west commands for downstream tasks and how to extend to tailor document generation for downstream needs. The video will also show how to extend Zephyr’s CMake system with downstream modules and how even a project specific package can be created. In the last section the presented possibilities will be compared to typical project requirements encountered in regulated environments such as the medical industry.
[embedyt] https://www.youtube.com/watch?v=dN3-nK18pMY[/embedyt]
Practical Tips to Boost Your Productivity When Using Zephyr – Benjamin Cabé, Developer Advocate for the Zephyr Project, The Linux Foundation
[embedyt] https://www.youtube.com/watch?v=azoP3xsZAlE[/embedyt]
How I Fell in Love with Zephyr – a System Architect’s Tale – Tobias Kästner, Staff Engineer at UL Method Park & Stephan Linz, Senior Embedded Software Engineer at Navimatix GmbH
Tobias Kästner designs system and software architectures for medical devices for more than ten years. In this time he has seen and suffered through a lot of woes and problems, stemming from decades-old development procedures and ineffective communications within product development teams. Worse yet, many persistent beliefs about how projects ought to be run have become completely inappropriate for today’s connected and ever faster moving world. Having followed Zephyr ever since its 1.10 release, the speaker has been using it in numerous projects collecting a considerable amount of experience to share. In his talk he will explain what profound impact technologies such as Kconfig or the Device tree have on the collaboration of hardware and software developers alike. Being also an advocate of model based systems engineering Tobias will use examples from his real-world projects to show how system models can inform downstream engineering activities. Thanks to Zephyr’s many clever design decisions, collaboration can be made more effective and the risks of costly misunderstandings can be significantly reduced. The talk concludes with some ideas what the future might hold and what still needs to be done for the Zephyr project to succeed in the medical device and similar industries.
For more information about the 2024 event, stay tuned by subscribing to the Zephyr quarterly newsletter or connect with us on @ZephyrIoT, Zephyr Project LinkedIn or the Zephyr Discord Channel to talk with community and TSC members.