# zephyr Published articles for zephyr. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Seeed Studio XIAO STM32C5 development board features dual CAN FD and a 6-axis IMU with programmable heating DevFeed: [Seeed Studio XIAO STM32C5 development board features dual CAN FD and a 6-axis IMU with programmable heating]() Original publisher: [Read original article]() Author: Debashis Das Published: 2026-11-09T12:00:41Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [Embedded Systems](), [seeed studio](), [Arm](), [Robotics](), [USB]() Tags: [automation](), [battery](), [can](), [can-bus](), [cortex-m33](), [development-board](), [firmware](), [flash](), [hardware](), [imu](), [industrial](), [micropython](), [motion-sensing](), [robotics](), [rtos](), [seeed-studio](), [sensors](), [stm32](), [stmicro-stm32](), [stmicroelectronics](), [usb-c](), [zephyr]() ### AI overview The XIAO STM32C5 pairs a 144 MHz STM32C5A3CG Arm Cortex-M33 with two CAN FD controllers and a 6-axis LSM6DS3TR-C IMU whose temperature can be regulated by PWM-controlled heating resistors to help reduce temperature-related motion-measurement drift. FDCAN2 connects to an onboard CAN FD transceiver and CANH/CANL pads; FDCAN1 exposes TX/RX for an external transceiver. The onboard 120 Ω termination is enabled by default and can be disconnected. The board also has 256 KB SRAM, 1 MB internal and 16 MB external flash, USB-C, battery charging, and XIAO-format expansion headers. Documentation and examples are listed for STM32CubeIDE, PlatformIO with Zephyr, and MicroPython. The text lists prices of $18.85 on AliExpress and $9.90 at Seeed Studio, or $10.90 for the pre-soldered version, before taxes and shipping. ### Source excerpt Seeed Studio XIAO STM32C5 is the company's first XIAO development board based on an STMicroelectronics MCU, namely a 144 MHz STM32C5A3CG Arm Cortex-M33 microcontroller. It features two CAN FD controllers and a 6-axis IMU with programmable heating for robotics, industrial control, and motion-sensing applications. The board also includes 16MB of external flash, a 48 MHz external crystal, a USB-C port, and battery charging circuitry. One CAN FD channel is connected to an onboard transceiver, while the second requires an external transceiver. The integrated IMU heater allows firmware to control sensor temperature and reduce measurement drift from temperature changes. XIAO STM32C5 specifications: MCU - STMicroelectronics STM32C5A3CG CPU - 144 MHz Arm Cortex-M33 with FPU and DSP instructions Memory - 256KB SRAM Storage - 1MB internal flash Storage - 16MB external flash USB - USB Type-C port with USB 2.0 Full-Speed support (12 Mbps) CAN Bus 2x CAN FD controllers (FDCAN1 and [...] The post Seeed Studio XIAO STM32C5 development board features dual CAN FD and a 6-axis IMU with programmable heating appeared first on CNX Software - Embedded Systems News. ## 111 Picoseconds Later -- Zephyr Podcast #058 DevFeed: [111 Picoseconds Later -- Zephyr Podcast #058]() Original publisher: [Read original article]() Author: Benjamin Cabé Published: 2026-11-06T14:19:47Z Content type: news Language: en Sources: [Zephyr Project]() Topics: [Zephyr RTOS](), [Embedded Systems](), [CI/CD](), [FOSDEM]() Tags: [ai](), [blog](), [fosdem](), [nordic](), [podcast](), [pull-requests](), [reviews](), [talks](), [zephyr]() ### AI overview Zephyr support for ST's STM32G5 was submitted alongside the series announcement, including clock control, GPIO, UART and RTC for the NUCLEO-G564RE; the chip's timer has 111 ps resolution. Nordic's nRF71 brings Wi-Fi 6 on chip, and an nRF7120 DK board is already supported. A proposed AI review workflow posts summaries and inline comments when a PR is labeled ai-review, but does not approve or block it; prompts and reviews are public, and it can also run locally with personal API keys. Other changes include an external heatshrink module, unlocked bitmap helpers for callers that serialize access, and an OTP GPIO strap backend that disconnects pins after reading. native_tty adds host low-latency and USB-ID lookup options. The Ethernet bridge's RSTP implementation restores a link after failure; testing on an i.MX RT1170 EVK reported failover under 300 ms. The episode also notes per-register I2C target callbacks, NXP and Seeed board support, and a FOSDEM 2027 talk deadline of 16 November. ### Source excerpt ST's STM32G5 and Nordic's nRF71 arrive with Zephyr support lined up, AI reviews are coming to pull requests, and FOSDEM talks are due 16 November. ## The missing piece: bringing up to 15 years of support to Zephyr for microcontroller-based ECUs DevFeed: [The missing piece: bringing up to 15 years of support to Zephyr for microcontroller-based ECUs]() Original publisher: [Read original article]() Author: Jaume Rafols Published: 2026-11-06T13:37:10Z Content type: article Language: en Sources: [Ubuntu blog]() Topics: [Zephyr RTOS](), [Embedded Software Dev](), [Microcontroller]() Tags: [architectures](), [audits](), [automotive](), [backdoors](), [build-tools](), [cadence](), [canonical](), [capabilities](), [distributed](), [enterprise](), [high-performance](), [lifecycle](), [lts](), [maintenance](), [microcontroller](), [security](), [software](), [support](), [vehicles](), [zephyr]() ### AI overview Zephyr 26.04 LTS extends long-term support to microcontroller-based vehicle ECUs, with Canonical offering up to 15 years of CVE monitoring, security patches and SBOM generation per LTS. The source describes this as an alternative to maintaining custom RTOS forks or managing disparate vendor distributions, which it says can burden engineering teams and complicate security and ISO/SAE 21434 compliance. Releases are planned every two years, with interim updates every six months; support covers the Zephyr kernel and West build tooling. Canonical Workshop provides a sandboxed, reproducible Ubuntu development environment through a single command, with a Zephyr SDK and build tools ready to use. The excerpt presents these capabilities as supporting lifecycle security and faster onboarding across distributed teams. ### Source excerpt We recently announced the launch of Zephyr 26.04 LTS, bringing up to 15 years of security maintenance per LTS and enterprise lifecycle management to microcontroller-grade devices. While central high-performance computer ECUs capture most of the industry spotlight in software-defined vehicle (SDV) architectures, the operational reality of modern vehicles is far more distributed. Under the chassis [...] ## The missing piece: bringing up to 15 years of support to Zephyr for microcontroller-based ECUs DevFeed: [The missing piece: bringing up to 15 years of support to Zephyr for microcontroller-based ECUs]() Original publisher: [Read original article]() Author: Jaume Rafols Published: 2026-11-06T13:37:10Z Content type: article Language: en Sources: [Canonical]() Topics: [Zephyr RTOS](), [Embedded Software Dev](), [Microcontroller]() Tags: [architectures](), [automotive](), [based](), [capture](), [central](), [computer](), [devices](), [distributed](), [enterprise](), [high-performance](), [industry](), [launch](), [lifecycle](), [lts](), [maintenance](), [management](), [microcontroller](), [modern](), [support](), [up](), [zephyr]() ### AI overview Zephyr 26.04 LTS extends long-term security maintenance to microcontroller-based vehicle ECUs, with Canonical providing CVE monitoring, security patches, and SBOM generation for up to 15 years per LTS. The text argues this can reduce the burden of maintaining custom RTOS forks and tracking compliance across fragmented toolchains. It describes LTS releases every two years, interim updates every six months, and support for both the Zephyr kernel and West build tools. Canonical Workshop offers sandboxed, reproducible Ubuntu development environments through a single command, with a Zephyr SDK intended to let teams start using the tools without complex local setup. These are the article's stated capabilities and benefits; the excerpt gives no independent evaluation. ### Source excerpt We recently announced the launch of Zephyr 26.04 LTS, bringing up to 15 years of security maintenance per LTS and enterprise lifecycle management to microcontroller-grade devices. While central high-performance computer ECUs capture most of the industry spotlight in software-defined vehicle (SDV) architectures, the operational reality of modern vehicles is far more distributed. Under the chassis [...] ## What to Expect at the Zephyr Project Meetup (November 13, 2026) - Munich, Germany DevFeed: [What to Expect at the Zephyr Project Meetup (November 13, 2026) - Munich, Germany]() Original publisher: [Read original article]() Author: Susan Remmert Published: 2026-11-06T05:00:04Z Content type: news Language: en Sources: [Zephyr Project]() Topics: [Zephyr RTOS](), [Open Source](), [tinyml](), [cyber resilience act]() Tags: [2026](), [blog](), [community](), [contributors](), [developers](), [development](), [edge](), [embedded](), [embedded-systems](), [event](), [events](), [germany](), [industry-conference](), [meetup](), [open-source](), [programming](), [software](), [software-development](), [students](), [systems](), [systems-programming](), [technology](), [zephyr]() ### AI overview The Zephyr Project meetup is scheduled for November 13, 2026, from 9 a.m. to noon at electronica 2026 in Munich. Its agenda covers practical Zephyr work: OTA updates and their integration and reliability challenges; a microcontroller snow predictor using TensorFlow Lite Micro; tradeoffs in Kconfig and Devicetree, including compile-time hardware configuration; and security and Cyber Resilience Act readiness through upstream maintenance, MCUboot, secure updates, and boot-chain protections. Registration is required through edge lab LIVE!, which manages the event; the description says admission and a one-day electronica pass are free. ### Source excerpt The Zephyr Project community is heading to Munich, Germany! Join us on Friday, November 13, 2026, from 9:00 AM-12:00 PM for an in-person Zephyr Project Meetup, co-located with edge lab LIVE! at electronica 2026. The event is open to developers, engineers, contributors, students, technology professionals, and anyone interested in open source, embedded systems programming, and software development. ## CVE-2026-87040 - Bluetooth LE Controller accepts received PDUs whose length field exceeds the configured maximum receive length, causing out-of-bounds read and write DevFeed: [CVE-2026-87040 - Bluetooth LE Controller accepts received PDUs whose length field exceeds the configured maximum receive length, causing out-of-bounds read and write]() Original publisher: [Read original article]() Author: cvefeed.io Published: 2026-11-04T06:17:06Z Content type: article Language: en Sources: [Latest High/Critical Vulnerabilitiy Feed]() Topics: [Memory Safety](), [Bluetooth LE]() Tags: [2026](), [advertising](), [authentication](), [bluetooth](), [bluetooth-le](), [buffer](), [controller](), [corruption](), [cve](), [cve-2026-87040](), [encrypted](), [hci](), [interaction](), [iso](), [link](), [out-of-bounds-write](), [radio](), [range](), [update](), [write](), [zephyr](), [zephyrproject]() ### AI overview The nRF Bluetooth LE Controller failed to check received PDU length fields against the maximum length configured for the radio, allowing malformed packets to make downstream code read or write beyond buffers. A nearby attacker could trigger this on unencrypted LE connections or from a broadcaster the device is synchronised to for CONFIG_BT_CTLR_SYNC_ISO; pairing and user interaction are not required. Reported effects include controller crashes, memory corruption, and disclosure of controller memory through host data paths. Encrypted links are normally rejected by the CCM MIC check. The fix rejects PDUs longer than the configured receive maximum. The excerpt notes that periodic advertising sync reception in lll_sync.c was not changed and lacks an equivalent bound. ### Source excerpt CVE ID :CVE-2026-87040 Published : Nov. 4, 2026, 6:17 a.m. | 3 hours, 54 minutes ago Description :The nRF link-layer receive paths of the open-source Bluetooth LE Controller did not validate the on-air LENGTH field of a received PDU against the maximum receive length that was used to program the radio. isr_rx_pdu() in subsys/bluetooth/controller/ll_sw/nordic/lll/lll_conn.c enqueued any non-empty data PDU after only the sequence-number and (for encrypted links) MIC checks, and the corresponding isr_rx() handlers in lll_central_iso.c, lll_peripheral_iso.c, lll_sync_iso.c and lll_scan_aux.c did the same for ISO and extended-advertising PDUs. The nRF radio stores the received header verbatim and truncates only the payload at PCNF1.MAXLEN, so a frame declaring more octets than were configured leaves a node buffer whose len field describes more data than the buffer holds. An attacker within radio range that can emit a hand-crafted link-layer PDU -- for a connection, any peer that establishes an unencrypted LE connection to a connectable advertiser; for CONFIG_BT_CTLR_SYNC_ISO, any broadcaster the device is synchronised to -- can set the length byte up to 255 while the controller has programmed a much smaller maximum (lll->dle.eff.max_rx_octets, which is 27 until a Data Length Update, or the negotiated cis_lll->rx.max_pdu). No pairing, authentication or user interaction is required. On encrypted links the CCM MIC check normally rejects such a frame first, so the exposure is on unencrypted traffic, which is why the added check is placed after decryption. The unchecked length reaches hci_acl_encode() in subsys/bluetooth/controller/hci/hci.c, which performs net_buf_add(buf, pdu_data->len) followed by a memcpy() of that many bytes out of the node_rx pool element. Because CONFIG_BT_CTLR_DATA_LENGTH_MAX and CONFIG_BT_BUF_ACL_RX_SIZE both default to 27, this is an out-of-bounds read of up to roughly 228 bytes past the received PDU and a corresponding out-of-bounds write past the HC ## CVE-2026-16511 - Unvalidated user pointers in RTIO syscall verifiers allow a user-mode thread to write kernel memory DevFeed: [CVE-2026-16511 - Unvalidated user pointers in RTIO syscall verifiers allow a user-mode thread to write kernel memory]() Original publisher: [Read original article]() Author: cvefeed.io Published: 2026-11-04T06:17:04Z Content type: article Language: en Sources: [Latest High/Critical Vulnerabilitiy Feed]() Topics: [Kernel]() Tags: [cve-2026-16511](), [kernel](), [memory](), [permission](), [pointers](), [syscall](), [thread](), [user](), [write](), [zephyr](), [zephyrproject]() ### AI overview On Zephyr builds with CONFIG_USERSPACE and CONFIG_RTIO, two RTIO syscall verifiers allowed user-mode threads to make the kernel write to unchecked addresses. The cancel verifier accepted an SQE pointer without validation and followed a pointer chain while setting a cancellation bit, enabling writes into kernel memory and potential privilege escalation. The copy-in handle verifier checked the context and input array but only NULL-checked its output pointer, allowing a granted caller to make the kernel store a pointer at an arbitrary address. The fixes validate the output as writable, constrain cancel handles to submission-pool storage, and require permission for the context owning that pool; the permission check also prevents cancellation of other contexts' I/O. Builds without either configuration option are unaffected. ### Source excerpt CVE ID :CVE-2026-16511 Published : Nov. 4, 2026, 6:17 a.m. | 3 hours, 54 minutes ago Description :Two RTIO syscall verifiers, in subsys/rtio/rtio_syscalls.c (subsys/rtio/rtio_handlers.c before v4.3.0), did not validate user-supplied pointers before the kernel wrote through them. z_vrfy_rtio_sqe_cancel() performed no validation at all. It passed the caller's struct rtio_sqe pointer straight to z_impl_rtio_sqe_cancel(), which converts it with CONTAINER_OF to a struct rtio_iodev_sqe, ORs RTIO_SQE_CANCELED (BIT(3)) into its 16-bit flags field in supervisor mode, then loads its next pointer and repeats until that pointer is NULL. The syscall takes no RTIO context argument, so it needs no object grant: any user-mode thread on a CONFIG_USERSPACE build can set that bit in a 16-bit word at an address of its choosing in kernel memory, and the kernel continues the write along whatever pointer chain it finds at the corresponding offset. Setting chosen bits in kernel data structures, such as object permission or thread state fields, can be used to escalate privilege from user mode. z_vrfy_rtio_sqe_copy_in_get_handles() validated its RTIO context and the input SQE array, but only NULL-checked the handle out-parameter before writing a kernel SQE pointer through it, with no K_SYSCALL_MEMORY_WRITE check. A user thread that holds a granted RTIO context can therefore make the kernel store a pointer value at an arbitrary address. The fixes validate the handle out-parameter as writable, bound the cancel handle to real submission-pool storage, and require permission on the RTIO context that owns the matching pool. Without that last check a bounded handle still let any user thread cancel submissions belonging to other contexts, silently aborting their I/O. Systems built without CONFIG_USERSPACE or without CONFIG_RTIO are unaffected. Severity: 8.8 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more... ## CVE-2026-85035 - Use-after-free via dynamically allocated message queue retained by the CAN RX filter DevFeed: [CVE-2026-85035 - Use-after-free via dynamically allocated message queue retained by the CAN RX filter]() Original publisher: [Read original article]() Author: cvefeed.io Published: 2026-11-03T14:17:39Z Content type: article Language: en Sources: [Latest High/Critical Vulnerabilitiy Feed]() Topics: [Memory Safety]() Tags: [can](), [cve-2026-85035](), [filter](), [heap](), [isolation](), [kernel](), [message-queue](), [thread](), [use-after-free](), [user](), [zephyr](), [zephyrproject]() ### AI overview In Zephyr builds with CONFIG_USERSPACE=y and CONFIG_DYNAMIC_OBJECTS=y, a user-mode thread can register a CAN RX filter with a dynamically allocated message queue, then release the queue or exit. The filter retains a raw pointer, so a later matching frame can make supervisor-context code access freed memory and corrupt the kernel heap. The verifier previously checked type, initialization, and permission but not whether the queue would remain alive. The fix uses K_SYSCALL_OBJ_STATIC(), allowing only statically defined queues for user-mode registration. Supervisor-mode callers bypass that verifier and must keep the queue valid until removing the filter. The excerpt also notes the dangling-pointer risk if an application thread exits without removing its filter. ### Source excerpt CVE ID :CVE-2026-85035 Published : Nov. 3, 2026, 2:17 p.m. | 1 hour, 12 minutes ago Description :The can_add_rx_filter_msgq() system call installs a CAN RX filter whose callback (can_msgq_put() in drivers/can/can_common.c) is handed the caller's struct k_msgq * as user_data. The controller driver stores that raw pointer in its filter table and dereferences it from the RX path every time a matching frame arrives. The system call verifier z_vrfy_can_add_rx_filter_msgq() in drivers/can/can_handlers.c validated the queue only with K_SYSCALL_OBJ(), which is a point-in-time check of type, initialization and caller permission and says nothing about the object's lifetime. On a build with CONFIG_USERSPACE=y and CONFIG_DYNAMIC_OBJECTS=y, an unprivileged user-mode thread that has been granted access to a CAN device can obtain a message queue whose lifetime it fully controls: k_object_alloc(K_OBJ_MSGQ) followed by k_msgq_alloc_init(). The lifetime of such an object is driven solely by its permission bitmask, and a pointer retained by the kernel is not represented there. After registering the filter, the thread calls k_object_release() -- or simply terminates -- and unref_check() frees the struct k_msgq storage while the CAN driver still holds the pointer. The next matching CAN frame causes k_msgq_put() to run in supervisor context against freed memory that the attacker can have groomed with another kernel allocation: the frame payload is memcpy()d through the reused block's write_ptr, and the queue's wait_q (and poll_events under CONFIG_POLL) list nodes are manipulated. This yields kernel-heap corruption reachable from a user-mode thread, defeating the isolation CONFIG_USERSPACE is intended to provide; the same dangling pointer also arises benignly when an application thread exits without calling can_remove_rx_filter(). The fix validates the queue with K_SYSCALL_OBJ_STATIC(), which additionally rejects objects carrying K_OBJ_FLAG_ALLOC, so only statically defined queues (CAN_MSGQ ## What to Expect at the Zephyr Project Meetup (November 5, 2026) - Milpitas, California, USA DevFeed: [What to Expect at the Zephyr Project Meetup (November 5, 2026) - Milpitas, California, USA]() Original publisher: [Read original article]() Author: Susan Remmert Published: 2026-11-02T21:11:35Z Content type: news Language: en Sources: [Zephyr Project]() Topics: [Zephyr RTOS](), [Embedded Software Dev](), [Embedded Systems](), [Open Source](), [Developer experience](), [Visual Studio Code]() Tags: [2026](), [blog](), [california](), [community](), [contributors](), [developers](), [development](), [electronics](), [embedded](), [embedded-systems](), [engineers](), [event](), [events](), [hardware](), [meetup](), [nxp](), [open-source](), [programming](), [semiconductors](), [software](), [usa](), [zephyr]() ### AI overview The Zephyr Project meetup in Milpitas runs November 5, 2026, from 9:00 AM to 1:00 PM PST, with NXP Semiconductors hosting at Future Electronics. Sessions cover why OEMs should contribute alongside silicon vendors, browser-based Zephyr simulation and hardware development experiments, and challenges in Zephyr development tools. The browser experiments span emulation, simulation, WebAssembly, WebUSB, Web Bluetooth, and Web Serial; the speaker notes that most are early-stage and will discuss what works and known limitations. Community discussion and lunch follow. Registration is required and seats are limited. ### Source excerpt The Zephyr Project community is heading to Milpitas, California! Join us on Thursday, November 5, 2026, from 9:00 AM-1:00 PM PST for an in-person Zephyr Project Meetup hosted by NXP Semiconductors, with Future Electronics as the venue sponsor. NXP Semiconductors will also sponsor hardware board giveaways. The event is open to developers, engineers, contributors, students, technology professionals, and anyone interested in open source, embedded systems programming, and software development. ## What to Expect at the Zephyr Project Meetup (November 5, 2026) - Milpitas, California, USA DevFeed: [What to Expect at the Zephyr Project Meetup (November 5, 2026) - Milpitas, California, USA]() Original publisher: [Read original article]() Author: Susan Remmert Published: 2026-11-02T21:11:35Z Content type: news Language: en Sources: [Zephyr Project]() Topics: [Zephyr RTOS](), [Embedded Software Dev](), [Open Source](), [Embedded Systems](), [Developer experience](), [remote-development](), [Visual Studio Code](), [canonical]() Tags: [2026](), [blog](), [board](), [california](), [community](), [contributors](), [developers](), [development](), [electronics](), [embedded](), [embedded-systems](), [engineers](), [event](), [events](), [hardware](), [meetup](), [nxp](), [open-source](), [programming](), [project](), [usa](), [zephyr]() ### AI overview The November 5, 2026 Zephyr Project meetup in Milpitas features talks on OEM and silicon-vendor collaboration, browser-based Zephyr development and debugging, and the evolution of Zephyr development tools, followed by community discussion and lunch. The collaboration session describes how shared interfaces, upstream contributions, and OEM feedback can reduce duplicated work while letting companies differentiate. The browser session presents early-stage experiments spanning emulation, simulation, WebAssembly, and real hardware access through WebUSB, Web Bluetooth, and Web Serial, with demos and known limitations. The tools session reviews challenges in environment setup, Device Tree management, agentic workflows, and Visual Studio Code solutions. NXP Semiconductors hosts and sponsors board giveaways; Future Electronics provides the venue. Registration is required and seats are limited. ### Source excerpt The Zephyr Project community is heading to Milpitas, California! Join us on Thursday, November 5, 2026, from 9:00 AM-1:00 PM PST for an in-person Zephyr Project Meetup hosted by NXP Semiconductors, with Future Electronics as the venue sponsor. NXP Semiconductors will also sponsor hardware board giveaways. The event is open to developers, engineers, contributors, students, technology professionals, and anyone interested in open source, embedded systems programming, and software development. ## Development of USB support in Zephyr RTOS with the implementation of HID Boot device support DevFeed: [Development of USB support in Zephyr RTOS with the implementation of HID Boot device support]() Original publisher: [Read original article]() Author: Zephyr Project Published: 2026-10-29T05:00:41Z Content type: article Language: en Sources: [Zephyr Project]() Topics: [Zephyr RTOS](), [USB]() Tags: [blog](), [boot](), [hid](), [member-blog](), [open-source](), [rtos](), [usb](), [usb-host](), [zephyr]() ### AI overview Zephyr's USB Host support gained HID Boot support through several prerequisites: multi-packet transfers let Low Speed devices send configuration descriptors larger than their 8-byte packet limit, while scheduled and rescheduled interrupt transfers provide periodic polling and prioritize time-sensitive reports. A generic HID Boot class driver sends SET_IDLE on connection, polls devices, parses reports, and exposes events through Zephyr's input subsystem. The article's example builds a mouse-and-display sample for an STM32H747I Discovery board with a MAX3421E shield; it recommends the SparkFun shield, while noting the demonstration used an Adafruit shield and that display shield choice may depend on board revision. ### Source excerpt The open source Zephyr RTOS continues to gain popularity, and many contributors are committed to further extending Zephyr's reach by helping improve it and add additional features. An example of a feature that is being actively worked on by the community is adding USB Host support. Within this issue, work is underway for developing support for a number of USB classes, such as MSC (Mass Storage Class), CDC ECM (Communication Device Class Ethernet Control Model), or HUB. ## Development of USB support in Zephyr RTOS with the implementation of HID Boot device support DevFeed: [Development of USB support in Zephyr RTOS with the implementation of HID Boot device support]() Original publisher: [Read original article]() Author: Zephyr Project Published: 2026-10-29T05:00:41Z Content type: tutorial Language: en Sources: [Zephyr Project]() Topics: [Zephyr RTOS](), [USB](), [Open Source]() Tags: [blog](), [boot](), [class](), [development](), [hid](), [implementation](), [member-blog](), [rtos](), [usb](), [usb-host](), [zephyr]() ### AI overview Zephyr's USB Host subsystem gained HID Boot support through prerequisites that address the devices' transfer needs. Multi-packet transfers let Low Speed devices send configuration descriptors larger than their 8-byte maximum packet size. New interrupt-transfer scheduling, rescheduling, and prioritization support the regular, time-sensitive polling used by HID devices. A generic HID Boot driver sends SET_IDLE, polls for reports, parses key and mouse events, and exposes them through Zephyr's input subsystem. The article's test instructions use an STM32H747I Discovery board and MAX3421E shield; it recommends the SparkFun shield, notes the demo used an Adafruit version, and says display shield choice may depend on board revision. ### Source excerpt The open source Zephyr RTOS continues to gain popularity, and many contributors are committed to further extending Zephyr's reach by helping improve it and add additional features. An example of a feature that is being actively worked on by the community is adding USB Host support. Within this issue, work is underway for developing support for a number of USB classes, such as MSC (Mass Storage Class), CDC ECM (Communication Device Class Ethernet Control Model), or HUB. ## BeagleConnect QuadESC 4-channel BLDC motor controller uses TI's AM13E23019-based Torque module DevFeed: [BeagleConnect QuadESC 4-channel BLDC motor controller uses TI's AM13E23019-based Torque module]() Original publisher: [Read original article]() Author: Debashis Das Published: 2026-10-29T00:00:24Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [Embedded Systems](), [Microcontroller](), [Embedded Software Dev](), [tinyml]() Tags: [adc](), [ai](), [ai-applications](), [arm](), [battery](), [beagleboard](), [can](), [controller](), [cortex-m33](), [edge-ai](), [freertos](), [hardware](), [inyml](), [mcu](), [microcontroller](), [module](), [motor](), [motor-control](), [open-source](), [openocd](), [robotics](), [sensing](), [sensors](), [software](), [som](), [texas-instruments](), [ti](), [zephyr](), [zephyr-os]() ### AI overview BeagleBoard.org's open-source QuadESC pairs a BeagleConnect Torque SoM with four three-phase BLDC motor channels for robotics and other multi-motor systems. It supports 3S-6S batteries, synchronized current sensing for FOC, phase-voltage and temperature monitoring, CAN-FD, and a flight-controller interface with DShot and telemetry signals. The Torque module uses a 200 MHz TI AM13E23019 Cortex-M33 and can also be used on custom carrier boards; it needs regulated carrier power, a separate analog reference for ADC measurements, and 5V for CAN. The board's stated 40A continuous and 70A burst targets are unverified and depend on cooling and load duration. It does not include ready-to-use motor-control firmware, so developers must implement motor control, driver setup, sensing, and fault handling. Hardware designs, firmware sources, and documentation are provided; pricing and availability have not been announced. ### Source excerpt BeagleBoard.org has introduced the BeagleConnect QuadESC, an open-source 4-channel BLDC motor controller/carrier board built around the BeagleConnect Torque SoM. The SoM features TI's 200 MHz AM13E23019 Arm Cortex-M33 microcontroller with a trigonometric math unit (TMU) and a TinyEngine neural-network accelerator for edge AI applications. The QuadESC carrier board supports four three-phase BLDC motor outputs, twelve current and twelve voltage sensing channels, four temperature sensors, and battery voltage monitoring. It also includes an eight-pin flight controller connector with DShot, telemetry, and current reporting signals, along with SWD debugging, a buzzer connector, and onboard power regulation. BeagleConnect Torque SoM The Torque SoM can also be integrated with custom carrier boards for robotics, motor control, and CAN-connected applications. It provides the processing, sensing, and communication interfaces, while external hardware supplies the motor power . Specifications: Main MCU- Texas Instruments AM13E23019 CPU core - Arm Cortex-M33 MCU @ 200 MHz with FPU Memory - [...] The post BeagleConnect QuadESC 4-channel BLDC motor controller uses TI's AM13E23019-based Torque module appeared first on CNX Software - Embedded Systems News. ## Zephyr RTOS 4.5 Now Available: Two New Architectures, Multimedia Pipelines, SBOMs for the CRA, and More DevFeed: [Zephyr RTOS 4.5 Now Available: Two New Architectures, Multimedia Pipelines, SBOMs for the CRA, and More]() Original publisher: [Read original article]() Author: Benjamin Cabé Published: 2026-10-28T22:46:51Z Content type: release Language: en Sources: [Zephyr Project]() Topics: [Zephyr RTOS](), [cyber resilience act](), [AI Integration Strategies](), [gateway](), [Data pipelines](), [Test automation](), [Cryptography](), [CI/CD](), [WebSocket]() Tags: [announcements](), [architectures](), [blog](), [cra](), [debugging](), [faster](), [hexagon](), [improvements](), [multimedia](), [network](), [network-stack](), [pipelines](), [release](), [rtos](), [sboms](), [testing](), [zephyr]() ### AI overview Zephyr 4.5 adds TriCore and Hexagon support, broader networking, multimedia pipelines, and security and diagnostic features. Its network stack gains up to 21% TCP and 12% UDP throughput in deterministic QEMU loopback benchmarks; it also adds QUIC, HTTP/3 serving, SSH, and IPv4 forwarding with NAT. The experimental mpipe subsystem links source, transform, and sink elements, passing buffers without copies; a leaky queue lets video continue at full rate while slower inference skips frames. SPDX 3.0 SBOM generation records source files and build details, though SPDX 2.3 remains the default. Other additions include per-file assertion levels, heap error detection, trace viewing and export, UDP coredumps, expanded host-backed native_sim peripherals, and multi-device Twister tests. The release also adds six driver classes, 178 boards, and 29 shields. Upgrading from 4.4 may require changes for the ring buffer API and CMake flash/debug targets; TriCore QEMU and the Hexagon toolchain require separate setup. ### Source excerpt Zephyr 4.5 brings two new architectures (TriCore and Hexagon), a faster and broader network stack, multimedia pipelines with mpipe, and a long list of debugging and testing improvements. ## Zephyr RTOS 4.5 Now Available: Two New Architectures, Multimedia Pipelines, SBOMs for the CRA, and More DevFeed: [Zephyr RTOS 4.5 Now Available: Two New Architectures, Multimedia Pipelines, SBOMs for the CRA, and More]() Original publisher: [Read original article]() Author: Benjamin Cabé Published: 2026-10-28T22:46:51Z Content type: release Language: en Sources: [Zephyr Project]() Topics: [Zephyr RTOS](), [cyber resilience act](), [Cryptography](), [Data pipelines]() Tags: [1-3](), [2](), [2026](), [announcements](), [architectures](), [blog](), [cra](), [debugging](), [faster](), [hexagon](), [improvements](), [list](), [multimedia](), [network](), [network-stack](), [pipelines](), [release](), [rtos](), [sboms](), [stack](), [testing](), [with](), [zephyr]() ### AI overview Zephyr 4.5 adds TriCore and Hexagon support, with QEMU targets; TriCore's QEMU and the Hexagon toolchain are not yet included in the Zephyr SDK. Networking updates include benchmark gains of up to 21% for TCP and 12% for UDP, QUIC and HTTP/3 support, SSH, and IPv4 forwarding/NAT plus IPv6 routing features. Experimental mpipe offers GStreamer-style media pipelines with shared buffers and threaded branches. Security additions include SPDX 3.0 build-provenance SBOMs (SPDX 2.3 remains the default), configurable hardening checks that can fail CI, and FIDO2 authentication. The release also improves debugging, host-backed native_sim testing, multi-device Twister tests, kernel performance, and hardware support. Upgrading from 4.4 may require replacing ring-buffer claim/finish calls and CMake flash/debug targets with their listed alternatives. ### Source excerpt Zephyr 4.5 brings two new architectures (TriCore and Hexagon), a faster and broader network stack, multimedia pipelines with mpipe, and a long list of debugging and testing improvements. ## What to Expect at the Zephyr Project Meetup (October 29, 2026) - Dublin, Ireland DevFeed: [What to Expect at the Zephyr Project Meetup (October 29, 2026) - Dublin, Ireland]() Original publisher: [Read original article]() Author: Susan Remmert Published: 2026-10-28T10:55:41Z Content type: news Language: en Sources: [Zephyr Project]() Topics: [Zephyr RTOS](), [Embedded Systems](), [Embedded Software Dev](), [Open Source](), [tinyml](), [developer-relations]() Tags: [2026](), [analog-devices](), [blog](), [community](), [contributors](), [developers](), [development](), [devices](), [embedded](), [embedded-systems](), [event](), [events](), [ireland](), [join](), [meetup](), [october](), [open](), [open-source](), [programming](), [project](), [software](), [zephyr]() ### AI overview The Zephyr Project meetup in Dublin on October 29, 2026, features sessions on robust IPC over zbus, a proposed Zephyr API for streaming raw mmWave radar data, the Zephyr pull request lifecycle, and deploying embedded machine learning. The radar proposal pairs raw frames streamed through RTIO with capture metadata and devicetree build checks; its driver-class versus sensor-API design remains open for community input. MLForge iteratively trains and quantizes models against hardware limits, then measures firmware under QEMU or on a board. A separate session demonstrates integrating ExecuTorch as a West module and running PyTorch models on a Zephyr MCU. Analog Devices hosts the 5-9 PM event; registration is required and seats are limited. ### Source excerpt The Zephyr Project community is heading to Dublin, Ireland! Join us on Thursday, October 29, 2026, from 5:00-9:00 PM for an in-person Zephyr Project Meetup hosted by Analog Devices. The event is open to developers, engineers, contributors, students, technology professionals, and anyone interested in open source, embedded systems programming, and software development. Whether you are an experienced Zephyr developer or just beginning to explore embedded technologies, you are welcome to join. ## What to Expect at the Zephyr Project Meetup (October 29, 2026) - Dublin, Ireland DevFeed: [What to Expect at the Zephyr Project Meetup (October 29, 2026) - Dublin, Ireland]() Original publisher: [Read original article]() Author: Susan Remmert Published: 2026-10-28T10:55:41Z Content type: article Language: en Sources: [Zephyr Project]() Topics: [Zephyr RTOS](), [Embedded Software Dev](), [Embedded Systems](), [Open Source](), [tinyml]() Tags: [2026](), [analog-devices](), [blog](), [community](), [contributors](), [developers](), [development](), [devices](), [embedded](), [embedded-systems](), [event](), [events](), [ireland](), [meetup](), [october](), [open](), [open-source](), [programming](), [project](), [software](), [software-development](), [zephyr]() ### AI overview The Zephyr Project meetup in Dublin is scheduled for October 29, 2026, from 5:00-9:00 PM at Analog Devices' office; registration is required and seats are limited. The agenda includes talks on building reliable command/response, event and streaming IPC over zbus; a proposed Zephyr API for streaming raw mmWave radar frames, with RTIO and devicetree configuration checks; the Zephyr pull request and release process; MLForge's iterative model training and on-device measurement loop; and deploying PyTorch models to microcontrollers through the ExecuTorch Zephyr module. The radar session raises an open design question--whether raw frames need a new driver class or should extend the sensor API. The MLForge presentation describes emulation and board testing, while the ExecuTorch example uses an STM32 running Zephyr and a Linux core that consumes results over UART. ### Source excerpt The Zephyr Project community is heading to Dublin, Ireland! Join us on Thursday, October 29, 2026, from 5:00-9:00 PM for an in-person Zephyr Project Meetup hosted by Analog Devices. The event is open to developers, engineers, contributors, students, technology professionals, and anyone interested in open source, embedded systems programming, and software development. Whether you are an experienced Zephyr developer or just beginning to explore embedded technologies, you are welcome to join. ## nrf54-arduino-core: nRF54 Arduino core for XIAO nRF54L15 and other nRF54 boards DevFeed: [nrf54-arduino-core: nRF54 Arduino core for XIAO nRF54L15 and other nRF54 boards]() Original publisher: [Read original article]() Author: Anne Barela Published: 2026-10-27T18:09:13Z Content type: news Language: en Sources: [Adafruit Industries]() Topics: [Arduino]() Tags: [adafruit](), [arduino](), [arduino-ide](), [ble](), [bluetooth](), [bluetooth-le](), [compatibility](), [core](), [debugging](), [deep](), [experimental](), [gdb](), [github](), [matter](), [nordic](), [nrf54](), [platformio](), [risc-v](), [seeed-xiao](), [software](), [xiao](), [zephyr]() ### AI overview nrf54-arduino-core provides register-level Arduino support for Nordic nRF54L boards without a Zephyr runtime or separate nRF Connect SDK installation. It targets boards including the Seeed XIAO nRF54L15 and XIAO nRF54LM20A, HOLYIOT modules, generic modules, and the nRF54L15 DK. Standard calls such as pinMode, digitalWrite, analogRead, Wire, SPI, and Serial are supported. Bluetooth LE uses a bundled Bluefruit52Lib compatibility layer for porting Adafruit-style sketches with small changes; ArduinoBLE is not the native BLE library. The core also exposes the VPR RISC-V coprocessor and handles board-specific sleep, including nPM1300 PMIC and QSPI flash deep power-down on the LM20A. Install through Arduino IDE Boards Manager or PlatformIO, supported since release 1.0.21 with GDB debugging and Unity tests. Thread, Matter, Zigbee, and Channel Sounding are available for evaluation but marked experimental. ### Source excerpt Lolren has published nrf54-arduino-core on GitHub, an Arduino core for Nordic's nRF54L family that talks to the hardware at the register level. There is no Zephyr runtime underneath and no separate nRF Connect SDK install. Targets include the Seeed XIAO nRF54L15 and XIAO nRF54LM20A, HOLYIOT modules, generic modules and the Nordic nRF54L15 DK. The usual [...] ## What to Expect at the Zephyr Project Meetup (October 28, 2026) - Orlando, Florida, USA DevFeed: [What to Expect at the Zephyr Project Meetup (October 28, 2026) - Orlando, Florida, USA]() Original publisher: [Read original article]() Author: Susan Remmert Published: 2026-10-27T09:49:51Z Content type: news Language: en Sources: [Zephyr Project]() Topics: [Zephyr RTOS](), [Open Source](), [Programming]() Tags: [2026](), [blog](), [community](), [contributors](), [developers](), [development](), [electronics](), [embedded](), [embedded-systems](), [event](), [events](), [florida](), [future](), [join](), [meetup](), [nxp](), [october](), [open](), [open-source](), [project](), [usa](), [zephyr]() ### AI overview An in-person Zephyr Project meetup is scheduled for October 28, 2026, from 3:00-6:00 PM EDT at Hyatt Place Orlando Airport. Registration is required and closes at 3:00 PM EDT that day; seats are limited. Hosted by NXP Semiconductors, with Future Electronics sponsoring the venue, the event marks Zephyr's 10th anniversary and includes talks on NXP's community engagement and Bluetooth Classic audio development in Zephyr, plus strategies for lowering power use through Zephyr's Power Management subsystem. The agenda also includes snacks, a quiz, NXP-sponsored hardware board distribution, and networking. ### Source excerpt The Zephyr Project community is heading to Orlando, Florida! Join us on Wednesday, October 28, 2026, for an in-person Zephyr Project Meetup hosted by NXP Semiconductors, with Future Electronics as the venue sponsor. The event is open to developers, engineers, contributors, students, technology professionals, and anyone interested in open source, embedded systems programming, and software development. ## What to Expect at the Zephyr Project Meetup (October 28, 2026) - Orlando, Florida, USA DevFeed: [What to Expect at the Zephyr Project Meetup (October 28, 2026) - Orlando, Florida, USA]() Original publisher: [Read original article]() Author: Susan Remmert Published: 2026-10-27T09:49:51Z Content type: news Language: en Sources: [Zephyr Project]() Topics: [Zephyr RTOS](), [Open Source](), [Programming]() Tags: [2026](), [blog](), [community](), [contributors](), [developers](), [development](), [electronics](), [embedded](), [embedded-systems](), [event](), [events](), [florida](), [future](), [meetup](), [nxp](), [october](), [open-source](), [programming](), [project](), [semiconductors](), [usa](), [zephyr]() ### AI overview The Orlando Zephyr Project Meetup is scheduled for October 28, 2026, from 3:00-6:00 PM EDT at Hyatt Place Orlando Airport. NXP Semiconductors hosts the event and sponsors hardware board giveaways; Future Electronics sponsors the venue. The agenda includes NXP's work on Bluetooth Classic audio support in Zephyr, including A2DP plans and compliance and robustness coverage, and a session on reducing power consumption with Zephyr's Power Management subsystem. Snacks, a quiz and board distribution, and networking are also scheduled. Registration is required, seats are limited, and registration closes at 3:00 PM EDT on the event date. ### Source excerpt The Zephyr Project community is heading to Orlando, Florida! Join us on Wednesday, October 28, 2026, for an in-person Zephyr Project Meetup hosted by NXP Semiconductors, with Future Electronics as the venue sponsor. The event is open to developers, engineers, contributors, students, technology professionals, and anyone interested in open source, embedded systems programming, and software development. ## CVE-2026-79982 - Out-of-bounds write in the USB Bluetooth HCI transport class when a controller-to-host HCI packet exceeds the bulk endpoint maximum packet size DevFeed: [CVE-2026-79982 - Out-of-bounds write in the USB Bluetooth HCI transport class when a controller-to-host HCI packet exceeds the bulk endpoint maximum packet size]() Original publisher: [Read original article]() Author: cvefeed.io Published: 2026-10-23T20:17:28Z Content type: article Language: en Sources: [Latest High/Critical Vulnerabilitiy Feed]() Topics: [Memory Safety](), [Bluetooth](), [Bluetooth LE]() Tags: [2026](), [bluetooth](), [cve-2026-79982](), [hci](), [net](), [packet](), [size](), [transport](), [usb](), [write](), [zephyr](), [zephyrproject]() ### AI overview In the USB Bluetooth HCI transport, bt_hci_tx_sync_in() copies controller-to-host packets into fixed-size transfer slots without checking packet length. On full-speed-only builds, a slot is 64 bytes, while HCI event or ACL buffers can be larger, so the copy can overwrite adjacent memory. The excerpt says a mandatory 70-byte Read Supported Commands event triggers a six-byte overflow at each host initialization; Bluetooth traffic can also reach the vulnerable path through ACL fragments or extended advertising reports. With assertions disabled, the overwrite can corrupt memory and may enable code execution on targets lacking subsystem memory protection; with assertions enabled, it instead triggers a panic and denial of service. The described fix uses a separate transmit pool sized for the larger configured HCI buffers, while retaining the endpoint-sized pool for host-to-device traffic. ### Source excerpt CVE ID :CVE-2026-79982 Published : Oct. 23, 2026, 8:17 p.m. | 1 hour, 29 minutes ago Description :The Bluetooth HCI USB transport class of the new USB device stack, subsys/usb/device_next/class/bt_hci.c, copies every controller-to-host HCI packet into a USB transfer buffer before enqueuing it on an endpoint. bt_hci_tx_sync_in() allocated that buffer from bt_hci_ep_pool, a fixed pool whose slots are only USBD_MAX_BULK_MPS bytes (64 on full-speed-only builds), and then performed net_buf_add_mem(buf, bt_buf->data, bt_buf->len) with no length check. HCI event and ACL buffers are sized by CONFIG_BT_BUF_EVT_RX_SIZE and CONFIG_BT_BUF_ACL_RX_SIZE and can be far larger, so the copy runs past the end of the 64-byte slot into the adjacent slots and into whatever follows the statically allocated pool. The device runs the local Bluetooth controller in raw HCI mode (CONFIG_BT_HCI_RAW), so the oversized packets originate over the air. With the HCI buffer sizes recommended for full-featured controllers, an unauthenticated attacker within Bluetooth range can supply the overflowing bytes: a connected peer that negotiates Data Length Extension can send ACL fragments up to CONFIG_BT_CTLR_DATA_LENGTH_MAX bytes, and an attacker that merely broadcasts extended advertising data reaches the same path through LE Extended Advertising Report events, which the controller fragments only to CONFIG_BT_BUF_EVT_RX_SIZE. In the stock configuration the overflow is already reached without any radio traffic: the mandatory Read Supported Commands command-complete event is 70 bytes and overruns the 64-byte slot by six bytes on every host initialization. Because net_buf_add_mem() validates tailroom only through an assertion unless CONFIG_NET_BUF_HARDENING is enabled, builds with CONFIG_ASSERT=n -- the usual production setting -- silently corrupt memory adjacent to the USB buffer pool with attacker-chosen contents, which on a target without memory protection between subsystems can lead to arbitrary code execu ## CVE-2026-79977 - WireGuard peer endpoint learned from unauthenticated transport-data messages allows off-path tunnel hijack in Zephyr DevFeed: [CVE-2026-79977 - WireGuard peer endpoint learned from unauthenticated transport-data messages allows off-path tunnel hijack in Zephyr]() Original publisher: [Read original article]() Author: cvefeed.io Published: 2026-10-23T20:17:27Z Content type: article Language: en Sources: [Latest High/Critical Vulnerabilitiy Feed]() Topics: [Virtual Private Network](), [Cryptography](), [Encryption]() Tags: [2026](), [authentication](), [boot](), [cryptographic](), [cryptographic-identity](), [cve](), [cve-2026-79977](), [devices](), [encrypted](), [handshake](), [handshakes](), [hijack](), [index](), [interface](), [key](), [message](), [peer](), [transport](), [wireguard](), [zephyr](), [zephyrproject]() ### AI overview In Zephyr's WireGuard service, an unauthenticated transport-data message with an unknown receiver index could overwrite a peer's endpoint with an attacker-chosen address when no valid handshake or current keypair exists. A reachable UDP listener makes this possible off-path with a single spoofed datagram; later handshakes and tunnel traffic are then redirected, potentially persistently disrupting the tunnel. Relaying redirected handshakes can expose ciphertext and traffic metadata, but WireGuard encryption still prevents content decryption or forgery. The described fix removes endpoint learning from this recovery path: it sends the handshake to an endpoint learned through authentication, falls back to the configured endpoint, or drops the message if neither is known. WireGuard support is experimental and disabled by default. ### Source excerpt CVE ID :CVE-2026-79977 Published : Oct. 23, 2026, 8:17 p.m. | 1 hour, 29 minutes ago Description :The WireGuard VPN service in subsys/net/lib/wireguard/wg.c updated the peer endpoint from a message it could not authenticate. In handle_transport_data(), when the 32-bit receiver index of an incoming transport-data message matched no session, the code both scheduled a new handshake and copied the datagram's source address into peer->endpoint with memcpy(&peer->endpoint, peer_addr, sizeof(peer->endpoint)). Because the receiver index is unknown, there is no key with which such a message could be verified, so the address written into peer->endpoint is entirely attacker-supplied. Every other endpoint update in the implementation happens only after authentication -- after the Noise handshake in handle_handshake_init(), or after AEAD decryption plus the anti-replay check in wg_process_data_message(). The WireGuard listener is registered with net_udp_register() using no remote address or port filter and defaults to UDP port 51820 (CONFIG_WIREGUARD_PORT), and wg_ctrl_recv() resolves the peer by interface rather than by any cryptographic identity. Any host able to send a UDP datagram to that port can therefore reach the defect off-path, with no need to observe legitimate traffic: a 16-byte datagram carrying the transport-data type, zeroed reserved bytes and an arbitrary receiver index is sufficient. The vulnerable branch runs whenever the peer has neither a valid handshake nor a current keypair -- the state at boot and after a session expires. A single spoofed datagram redirects peer->endpoint to an address of the attacker's choosing, and all subsequent handshake initiations, keepalives and encrypted data packets are sent there. The legitimate peer never receives the initiations and so never re-authenticates, and nothing resets the endpoint afterwards, leaving the tunnel persistently unusable on devices whose peer does not initiate handshakes itself. The attacker can also relay t ## Assisted-By: Nobody -- Zephyr Podcast #056 DevFeed: [Assisted-By: Nobody -- Zephyr Podcast #056]() Original publisher: [Read original article]() Author: Benjamin Cabé Published: 2026-10-23T18:32:56Z Content type: news Language: en Sources: [Zephyr Project]() Topics: [Zephyr RTOS](), [Embedded Systems](), [Linux Kernel](), [Linux](), [FOSDEM](), [RIOT](), [AI Chat]() Tags: [blog](), [community](), [embedded](), [fosdem](), [linux](), [news](), [os](), [podcast](), [zephyr]() ### AI overview With Zephyr 4.5 at release candidate 3 and the feature freeze in effect, episode 056 is mostly community news. Linux developers plan to drop the Assisted-by tag requirement because it cannot be enforced; Zephyr adopted the same rule, and its community is discussing whether to keep the tag, which some reviewers find useful while others see it as vendor advertising. Other developments include a proposed vendor-neutral basic_radio API for packet-radio configuration, transmit, receive and continuous-wave testing, initially implemented for TI's CC23x0; Clang Thread Safety Analysis annotations that can catch locking mistakes at compile time with an LLVM toolchain; and per-register I2C target callbacks for behaviors such as clear-on-read and write-1-to-clear. The excerpt also describes OpenDial, a Zephyr-based high-resolution scroll wheel, and a proposed dev-kit test bench that exposes USB-connected boards over Wi-Fi for Twister. It notes the AS5600 sensor's relatively high power draw as a limitation for battery-powered OpenDial builds. ### Source excerpt 4.5 reaches RC3, FOSDEM 2027 gets an embedded OS devroom, Linux plans to drop its Assisted-by tag, and other community news. ## Assisted-By: Nobody -- Zephyr Podcast #056 DevFeed: [Assisted-By: Nobody -- Zephyr Podcast #056]() Original publisher: [Read original article]() Author: Benjamin Cabé Published: 2026-10-23T18:32:56Z Content type: news Language: en Sources: [Zephyr Project]() Topics: [Zephyr RTOS](), [Embedded Systems](), [Linux](), [FOSDEM](), [AI Chat]() Tags: [ai](), [ai-assisted](), [blog](), [community](), [embedded](), [fosdem](), [linux](), [news](), [os](), [podcast](), [rc3](), [tag](), [zephyr]() ### AI overview Zephyr 4.5 is at release candidate 3, so this episode focuses on community updates. Linux developers plan to drop the Assisted-by tag requirement because it is unenforceable and inconsistently used; the tag may help reviewers anticipate mistakes, though some see it as advertising. Zephyr adopted the same rule, and whether to retain it is under discussion. A separate maintainer discussion considered requiring contributors to state how changes were tested. Other updates include a proposed Clang Thread Safety Analysis integration that can catch annotated locking mistakes at compile time when using LLVM, and a draft vendor-neutral basic_radio API for packet radios, with a first TI CC23x0 implementation. The I2C target library's per-register callbacks support behaviors such as clear-on-read status and write-1-to-clear bits. The episode also covers an upcoming FOSDEM embedded OS devroom, a Zephyr-based remote test-bench concept, and tools and projects including OpenDial, Ollama, and Zsign. ### Source excerpt 4.5 reaches RC3, FOSDEM 2027 gets an embedded OS devroom, Linux plans to drop its Assisted-by tag, and other community news. [Next page]()