Zephyr RTOS Bulletin | November 6, 2025

Hello everyone, welcome to this issue of the Zephyr RTOS Bulletin.

🚀 Top Story

[ 👆 Replace with Elektor conference screenshot.png ]

Zephyr’s “Global Coverage Day” concluded yesterday, with Rust emerging as the biggest winner!

Yesterday (November 5), Zephyr held two major summits simultaneously online and in North America. According to leaked conference agendas and unofficial summaries, the hot topics were highly concentrated:

1. Online (Elektor Conference): The focal point was Rust. The talk by Mohammed Billoo on “How to Write Zephyr Applications in Rust” became the most discussed topic, while TinyML and security practices also occupied a significant portion.

2. Offline (North America Meetup): The vendor ecosystem exploded. NXP demonstrated Zephyr’s support for “Classic Bluetooth Audio” (entering automotive/speaker markets), Qt Group showcased a stunning GUI, and Antmicro demonstrated AI development on Zephyr (AutoML).

Core Storm:

The combination of “Rust + AI” (online technical depth) and “NXP + Qt” (offline commercial ecosystem) clearly indicates that Zephyr is evolving from an RTOS into a “platform”.

🛠️ Hardcore Updates

Victory! The critical CAN bus bug (PR #98712) has been merged!

[Status]: Merged!

Just before the closure of the 4.3.0 RC3 (hard freeze) window (tomorrow, November 7), the community and CI system completed intensive testing and validation of the CAN driver reentrancy bug (PR #98712) within the past 24 hours.

[Bulletin Interpretation]:

This was a “textbook” open-source rescue.

1. Timely Discovery: This critical bug was found during the RC phase (stabilization period).

2. Public Fix: Open discussions on the PR, and accepted the scrutiny from CI (and our bulletin).

3. Last-Minute Merge: Merged into the main branch just before the “hard freeze”.

Conclusion: The CAN bus in Zephyr version 4.3.0 (expected release on November 14) will be safe. This process demonstrates the effectiveness of the Zephyr TQC (Technical Quality Committee) process.

📊 GitHub Activity (24h)

Data Dashboard (Past 24h):

• zephyrproject-rtos/zephyr (main branch)

  • Total Commits: 51

  • New PRs: 7

  • Merged PRs: 28

• Active Subsystems:

  • drivers/: 19 commits (mainly final fixes for can, gpio, i2c)

  • tests/: 11 commits (intensive addition of test cases alongside driver fixes)

  • doc/: 8 commits

  • kernel/: 1 commit

• Active HAL Repositories:

  • hal_stm32: (Updated 9 hours ago)

  • hal_renesas: (Updated 14 hours ago)

[Bulletin Interpretation]:

The data is very “extreme”. The “Merged PRs (28)” far outnumber the “New PRs (7)”, with drivers/ and tests/ contributing nearly 60% of the commit volume, while kernel/ saw almost no changes.

This indicates that the final sprint before the “hard freeze” (RC3) has begun. The community is doing everything possible to “eliminate” the bug list, close PRs, and ensure the stability of 4.3.0.

💬 Comments Section Reveals Truth

Have you (or your team) started experimenting with Rust in your projects?

(Feel free to share your thoughts on the “Rust + Zephyr” combination in the comments section.)