The Zephyr Project

We did it! 🎉 🎉🎉 Congratulations to the The Zephyr Project community on reaching 100,000 commits! The Linux Foundation #ZephyrRTOS #opensource Kate Stewart Benjamin Cabé Maemalynn Nokdhes Meanor Tracey Cramer Li Anas Nashif Amy Occhialino Susan Remmert

Weekend Learning Spot Just checked off a new item in my The Zephyr Project #learning roadmap: ✅ Use #userspace / #privileged mode to improve the #safety of the application. To see how it works simply pull, launch the "West Build" Task, then flash the image from "build-slot0" target path and watch signals on PC_6 and PC_8 pins using a #LogicAnalyzer. PC_6, referenced by DBG_GPIO0, is toggling from main task with 2s period. PC_8, referenced by DBG_GPIO1, is toggling from user mode task with 1s period. In addition to the GPIO, there is a memory #partition reserved to the user mode task with 2 variable inside: foo and bar. Uncomment the define FORCE_TEST_USERSPACE_GPIO_ACCESS to disable the grant access to gpio port to the user mode thread, resulting in hard-fault when it tries to toggle him. Uncomment the define FORCE_TEST_USERSPACE_MEM_ACCESS to place the variable bar outside the user space memory domain, resulting in hard-fault when the user mode thread tries to write on it. https://lnkd.in/d2QtqXcr #weekendlearning #continuousimprovement

ICYMI: I wrote about inter-processor communication between Arm and RISC-V International cores on the new Nordic Semiconductor nRF54H20 SoC using The Zephyr Project IPC service.

My first pull request to The Zephyr Project! https://lnkd.in/dpax5J-f The PWM API in Zephyr currently allows for setting the period and pulse width of a PWM signal. The API abstracts away the details of getting the hardware to generate the desired signal, but in most cases it involves setting an output compare channel of a hardware timer to a certain value depending on the frequency of the timer clock. With the current API, this frequency remains constant, and is determined by the chosen clock source along with any prescaler within the timer, both of which are usually set in the device tree and remain static. In most applications where timers are used to generate pulse width modulation signals, the pulse width is varied while the frequency generally remains constant (hence the name) and this becomes a non-issue. However, when the aim is to generate a pulse wave with varying frequency, the current PWM API severely limits the possible frequency range and accuracy achievable, especially on lower resolution timers. Take the STM32F401 MCU for example. It has several 16-bit and 32-bit timers with multiple output compare channels. These timers have prescalers that can divide their input clock signal by anything from 1 to 65536. Say you want to use them to play music with pulse waves. With the current fixed prescaler constraint of the Zephyr PWM API, you'll find that the 32-bit timers are able to span just a bit over 6 octaves, while the 16-bit timers manage 4 at best. Not only that, but both timers struggle to maintain accuracy at the edges of their ranges resuling in sounds that are highly out-of-tune in all but 1-2 octaves. The solution? Let the PWM driver calculate an optimal prescaler value for the requested wave period and apply it when changing the PWM configuration, resulting in a much larger dynamically achievable frequency range and pitch-perfect tones.

To kick off #2025, I am offering the following #free #webinar I ran with Jacob Beningo. In this webinar, we show some best practices for adding custom hardware to an application using The Zephyr Project RTOS. Sign up for free here! https://lnkd.in/efjHzxkv #embeddedsoftware #embeddedsystems #mcu

Everyone is using #ZephyrRtos these days, what about you?

Zephyr provides a large set of modules, but not every module is necessary for your project. Knowing which specific modules to include in your manifest allow list can save time and reduce unnecessary file cloning. While Zephyr’s west meta-tool and its package management system allow manifest files to inherit from other files, this can result in the cloning of unused packages. Mike Szczys (Golioth) explains the process of checking your build directory to identify necessary modules, using a trial-and-error approach to fine-tune your manifest allow list. Read the blog here: https://hubs.la/Q030Pg700

#ZephyrRTOS in the wild 🔥🔥 Ryan Erickson from Ezurio shares how to build wireless products faster with Zephyr and MicroPhython; Saravanan Sekar from Linumiz presents Zephyr as Electric Vehicle Supply Equipment; Jordan Yates from CSIRO discusses ultra-low pwoer algorithms on cattle; Julien Vermillard from tado° shares how to connect Zephyr devices at scale using open source solutions; Iuliana Prodan from NXP Semiconductors presents how to integrate your proprietary code in Zephyr & Jason Murphy from Analog Devices talks about how to enable real-time secure connectivity to the industry edge with a single-pair ethernet. Learn more by watching these #ZephyrDevSummit videos here: https://hubs.la/Q030NGGH0 The Zephyr Project The Linux Foundation #EmbeddedOSSummit #opensource #RTOS

Missed the insightful session at #ossummit Japan with Kate Stewart from The Linux Foundation? Watch "Lessons Learned on Following Security Best Practices in Zephyr" to discover how The Zephyr Project has tackled security over the past 8 years. From becoming a CVE Numbering Authority to forming a dedicated PSIRT team of volunteers, this talk shares how Zephyr has navigated bulk vulnerability reports, embargo windows, and community vulnerabilities. It’s an essential watch for any #opensource project looking to leverage tried-and-true security best practices. Watch here: https://hubs.la/Q030NNZd0 #ZephyrRTOS

Storing and retrieving data from the cloud is the foundational concept of the Internet of Things. When two machines talk to one another they need to settle on a data format. Here at Golioth that means your microcontroller of choice is going to be sending and receiving JSON. Learn More about parsing JSON data in The Zephyr Project: https://glth.io/3W7B6BF