#RTOS

The Linux Foundationlinuxfoundation@social.lfx.dev
2025-12-10

⏳ Survey Closing Soon

As we celebrate a decade of innovation, we want to hear from you. How has Zephyr or your RTOS of choice shaped your work, products, and community experience?

Your insights will help guide the next decade of open innovation.

Take the survey: research.net/r/BRZXQGQ

#ZephyrProject #OpenSource #RTOS #Innovation #Survey

Video Processing WikiPythonLinks
2025-11-20

Libmpix on Zephyr OS is an open source pipeline for image processing. and support are in progress.

libmpix.org/


Via:
wiki.pythonlinks.info/libmpix

LibMpix Logo
The Linux Foundationlinuxfoundation@social.lfx.dev
2025-11-17

For 10 years, Zephyr has powered innovation in embedded systems—helping engineers build smarter, more connected solutions. But the story isn’t over yet.

Share how Zephyr has shaped your work and where you see RTOS tech heading next. Your feedback will help guide its future.

Take the survey 👉 research.net/r/BRZXQGQ

#ZephyrProject #RTOS #OpenSource #TechCommunity #Survey

Did you see our recent blog post on externally verifying #Linux deadline scheduling with reproducible embedded #Rust?

We explore how Codethink used embedded Rust to measure Linux’s scheduling performance with an external clock, while maintaining bit-for-bit reproducibility of the testing firmware.

Read the blog post in full: codethink.co.uk/articles/exter

#Linux #RaspberryPi #Scheduling #CTRLOS #RTOS

Blog post:
'Externally verifying Linux deadline scheduling with reproducible
embedded Rust'
By Theodore Tucker, Lawrence Hunter
David Chisnall (*Now with 50% more sarcasm!*)david_chisnall@infosec.exchange
2025-11-09

One think has really struck me in most pictures of #RTOS designs that I’ve seen recently: they all have a HAL or device driver layer at the bottom. The bottom layer is your trusted computing base (TCB): the bits that have to be correct for any of your security guarantees to hold. But device drivers talk to the outside world. Ethernet, SPI, I2C, UARTs, and so on are all parts of your attack surface: the place where an attacker is most likely to start attacking your system.

By combining your external attack surface with your TCB, you guarantee that an attacker who mounts a successful exploit has complete control over the system.

This is why #CHERIoT RTOS makes it trivial to delegate devices to the least-trusted portion of a firmware image. A compartment with exclusive access to a device doesn’t get any privileges other than a CHERI capability (hardware-enforced pointer) authorising access to that device’s MMIO region. If an attacker compromises it, they get access to that device, and maybe a way of trying to attack the next compartment, but it’s just the first step towards device compromise, not the end. Device drivers for single-user devices are just a software engineering abstraction, not a security boundary: they let you avoid thinking about device-specific details. Device drivers that handle multiplexing have no special privileges other than access to the device. At worst, compromising one allows you to break the isolation that the multiplexing provided.

Kevin Karhan :verified:kkarhan@infosec.space
2025-11-09

@nixCraft this makes total sense for #CriticalInfrastructure control systems as well as #aerospace applications.

  • Which is good because there needs to be more competition to the likes of #VxWorks!

#RTOS #Realtime #OS #OperatingSystem #FLOSS #Irobclad #IroncladOS

2025-11-06

Virtualization on ARMv8-M with the CROSSCON hypervisor running Zephyr RTOS and a TLS client.
The demo on LPCXpresso55S69 showcases a secure TLS application setup ready for 2FA integration.

Watch here 👉 youtu.be/GpKOEpA1aTQ?si=3hc8Hb
#Zephyr #ARMv8M #TLS #RTOS #EmbeddedSecurity #CROSSCON

The Linux Foundationlinuxfoundation@social.lfx.dev
2025-10-31

🎉 Zephyr is turning 10!
As we celebrate a decade of innovation, we want to hear from you. How has Zephyr or your RTOS of choice shaped your work, products, and community experience?

Your insights will help guide the next decade of open innovation.
Take the survey:research.net/r/BRZXQGQ

#ZephyrProject #OpenSource #RTOS #Innovation #Survey

New blog post!

Our latest article explores how Codethink used embedded #Rust to accurately measure Linux’s real-time scheduling performance with an external clock, while maintaining bit-for-bit reproducibility of the testing firmware.

Read the article in full: codethink.co.uk/articles/exter

#Linux #RaspberryPi #Scheduling #CTRLOS #RTOS

Graphics showing the blog post title: 'Externally verifying Linux deadline scheduling with reproducible embedded Rust'.
GripNewsGripNews
2025-09-30

🌘 在 ARM Cortex-M 架構上實現可搶佔式多工
➤ 使用 Rust 在 ARM Cortex-M 上從零打造一個可搶佔式即時作業系統
thejpster.org.uk/blog/blog-202
本文深入探討如何在 ARM Cortex-M 微控制器上,使用 Rust 語言建構一個具備可搶佔式多工(Pre-emptive Multi-Tasking)功能的即時作業系統(RTOS)。作者從現有 C 語言和 Rust 語言 RTOS 的生態系出發,解釋 RTOS 的核心概念與 ARM Cortex-M 架構的特性,並逐步闡述如何代表、堆疊任務、進行排程器調度以及實際切換任務的技術細節。文章旨在說明透過對 CPU 狀態(暫存器、堆疊指標、程式計數器等)的妥善儲存與恢復,即可在例外事件(如中斷)發生時,實現任務之間的無縫切換,讓程式彷彿同時執行多個獨立任務。
+ 這篇文章太棒了!深入淺出地解釋了 RTOS 的核心原理,特別是在 ARM Cortex-M 架構下如何利用其硬
Cortex-M

Michael T. Richterqqmrichter@mastodon.world
2025-09-26

And that covers the basics of #COROS and already, in my opinion, provides a better platform than most #RTOS implementations for small to mid-sized systems.

Then there's the advanced stuff. Note that events can pass *any* data type. And that an #EventQueue is a first-class data type. This means you can pass event queues around, π-calculus style, making it possible to provide subscribe/publish-style component connections, proxies, and other such systems with relative ease.

🧵 (5/n)

Michael T. Richterqqmrichter@mastodon.world
2025-09-26

So what does #COROS bring to the table that any other #RTOS among millions doesn't?

For starters it's based on #coroutines for concurrency, not pre-emptive threads. Coroutines fit better for small- to mid-sized MCU projects, in my experience, than do pre-emptive kernels. They're smaller, faster, time-deterministic, and as such far easier to reason about.

COROS lets you use coroutines raw, but that is not the overall system's approach.

🧵 (2/n)

Michael T. Richterqqmrichter@mastodon.world
2025-09-26

Most of the #embedded systems I've worked with over the last few years have been based on an #RTOS, #COROS, of my own design that I started working on ages ago, persuaded my boss to use, and then kind of lapsed on making my personal version public.

This week I started a huge push on releasing my personal version of COROS out to the public and it is ready for release, minus a few issues (like documentation being an aspirational WIP).

gitee.com/ACleverDisguise/coros

🧵 (1/n)

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst