#zephyr

Michał Fitamichalfita
2025-12-17

Does anyone knows good way to find opportunity for software dev? I'd like to avoid pitfalls of well known platforms. I can do:
- CLI/Dev tools, APIs
- code (, , including some or )
- C++ code
- or scripts, tools
- workflows (GitHub, GitLab)
- layers
- packaging +

Anyone has experience in getting hands on small projects?

Edit: I can / Rust or C++.

marble 弹珠 (39C3☎️: 01999-6725)marble@chaos.social
2025-12-16

Any #zephyr experts™️ looking for a #job in germany?

2025-12-14
2025-12-13

@octoate Zigbee hatte ich lediglich Mal mit den ESP32 s ausprobiert, würde ich aber nicht für Batteriebetrieb empfehlen. Wenn von Nordic, dann entweder 'alten' #nRF52840, damit Du altes nRF Connect SDK nutzen kannst oder neuen #nRF54L15 dann mit #Zephyr. Zigbee samples share.google/aHb4LxuU7vJ4xJwX3
Beide gibt's von Seeedstudio in der Xiao-Serie

2025-11-21

@gunter #Zephyr Light, PlatformIO,… oder was wäre das?

Till Kamppetertill@ubuntu.social
2025-11-20

The Google Summer of Code 2025 has ended for us at OpenPrinting, and it was the most successful one!

11 contributors did amazing work, and all of them successfully. Nobody failed this time.

And not only we liked the outcome, also our contributors loved working with us and most praised me and their mentors.

And we already have 17 candidates for next year ...

openprinting.github.io/OpenPri

#OpenPrinting #GSoC #GSoC2025 #GSoC2026 #Zephyr #GNOME #KDE #CUPS #PDF #Rust #Python

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
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

Christoph :verified_flashing:cv@hachyderm.io
2025-11-05

Oh man, I wish I saw this talk by @carles before I started digging into #Zephyr and its build tooling.

youtube.com/watch?v=cfVMg07bGFA

#zephyrRTOS #diy #foss #OSSSummitEU

Cosmic Meow Backgroundcmb@cathode.church
2025-11-04

oh look, a new lab note: eisendle.ee/posts/zephyr-in-a-

this is the distillation of what took me a few days to figure out when first learning about #zephyr

i hope this helps someone who's in a rush, because, gosh, i would've needed this.

Michał Fitamichalfita
2025-10-27

@bram Ever done on ?

Detlev Zundel [Team Human]dzu@hostsharing.coop
2025-10-24

Hey #zephyr Nerds - if you are around Copenhagen next Tuesday, there is really no excuse not to join the Zephyr Meetup at Mjølner Informatics and say hi!

See you there!

mjolner.dk/zephyr-meet-up-hos-

Stuart Longland (VK4MSL)stuartl@longlandclan.id.au
2025-10-22

The last few days I spent a fair chunk of my day arguing with the nRF Connect SDK and its Partition Manager…

The goal: trying to get NSIB and mcuboot to behave with the secondary image on external (QSPI) flash.

Took the better part of yesterday and today just getting a `pm_static.yml` together… only for it to compile an image, and `west flash` to barf because the image file embedded both on-chip flash data *and* a copy of the bootloader for the QSPI flash.

In the end, I came to the following conclusions:

1. Partition manager is over-engineered and fails at its prime objective of making partition layout easier (they tell you to skip dynamic layout and use `pm_static.yml` when doing DFU… enough said!)
2. NSIB is a no-go if external flash is involved because it *insists* on making a composite image that won't actually load.

Tomorrow, I'll see if I can bend `mcuboot` to my will. Primarily I want to see if I can move the public keys it uses for authenticity checks into a separate partition so I can update those without flashing a whole new bootloader.

#mcuboot #nrfconnect #nsib #nrf52840 #zephyr #openthread

Stuart Longland (VK4MSL)stuartl@longlandclan.id.au
2025-10-19

More work on the #SolarCluster tonight. Using #Zephyr to bridge between #collectd and some INA219 current shunt monitors.

The code runs on a Raspberry Pi Pico, and enumerates two USB CDC-ACM UART devices. One is a console, the other is a Modbus/RTU slave.

Two things I learned:

1. Your first CDC-ACM UART is easy, but a second one is a royal PITA.
2. Zephyr's Modbus stack assumes you have dedicated callback functions for each and every Modbus unit you create, with no concept of passing a user pointer or a unit ID to the callback function.

I had thought of a scheme where I had 3 units, the unit ID being equal to the I²C address of the slave, and just registers for voltage, current and power (Vshunt is not exposed by the Zephyr driver).

Nope, I've had to use one unit ID, and just offset the register numbers. But, whatever… I have a bridge now. I'll put in some settings interface so I can adjust scaling (the Zephyr driver assumes a shunt with a resistance in whole milliohms, mine is 500µohms) and we should be in business.

Code is a work-in-progress, but you can see it here: codeberg.org/sjlongland/modbus

2025-10-18

Sehr schön: #Zephyr Console des #nRF54L15 hat das Licht der Welt erblickt

Screenshot Konsolenausgabe 'hello world'
2025-10-15

yippie-kee-yay! just added teensy4.0 support to #klutshnik #zephyr - the 4.0 is smaller and cheaper than the 4.1 but comes with the same powerful cortex-m7 mcu. with this change klutshnik now runs on 4 different embedded systems: xiao_esp32s3, rpi pico2 (w) and the teensy4.1 and teensy4.0. \o/

also rewrote the provisioning interface which is now a proper shell on usb cdc-acm.

check it out on #radicle
rad:z2EBBi4vui98QV8Mk8DT3c25yZbJ4

or on the ms-trap: github.com/stef/klutshnik-zeph

Stuart Longland (VK4MSL)stuartl@longlandclan.id.au
2025-10-12

I can poll the INA219s via the Zephyr shell using the `sensor` command (if compiled in), so that all works.

Me: Fantastic, let's add a second CDC-ACM UART channel and set up Modbus on that…
Zephyr: Yeah… nah!

github.com/zephyrproject-rtos/

I can verify what I want to do is possible in TinyUSB, so the device _can_ do it, just Zephyr is being difficult.

Could I skip Zephyr and write it in plain C with TinyUSB? Sure, I could. I'd have to write my own Modbus/RTU code, but I've done that before and it's not exactly rocket science. But that's not what I'd like to do: I should be able to do it in Zephyr.

#Zephyr #USB_CDC_ACM #USB #RaspberryPiPico #RP2040

Henrik Brix Andersenbrixmeister@fosstodon.org
2025-10-08

I’ll be presenting #CANnectivity, an open source USB to CAN adapter firmware based on #ZephyrRTOS, at the #Zephyr meet-up in #Copenhagen on October 28.

The meet-up is hosted by Mjølner Informatics and @zephyr - agenda and sign up available here: mjolner.dk/zephyr-meet-up-hos-

github.com/CANnectivity/cannec

An image saying “Zephyr Meet-up, 28th October, Copenhagen, Hosted by Mjolner” and featuring a purple and blue kite, the logo of the Zephyr RTOS project.
2025-10-08

If you've been working in the #Arduino ecosystem, it's probably time to check out #Zephyr OS. Under the banner of the Linux foundation, Zephyr is a free platform that won't be bought out from underneath you. (It's so good, that even Arduino announced they were adopting it, after their previous high-end-device platform choice died of Capitalism).

HMU if you want some pointers, Here's me a few years back talking about Zephyr: youtube.com/watch?v=TxsLPh5dF_s

Client Info

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