Sponsored Session: Why NXP is Doubling Down on Zephyr Project
summary
NXP commits more engineering and org resources to Zephyr, shifting from an incubator model to making Zephyr enablement standard across new products and moving SDKs to GitHub first. Concrete results include upstreamed board support, a demo running the same application on RT1060 (600 MHz) and MCX‑N using the NPU with a TFLite pipeline, a VS Code extension and installer, display driver contributions, TSN quad‑motor example, and plans for downstream early access and five‑year support alignment.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:09Why NXP doubled down on Zephyr
- 7:20Supply chain and Zephyr adoption
- 10:12Zephyr complexity vs benefits
- 13:50NXP portfolio and Zephyr
- 16:01Value beyond silicon with Zephyr
- 18:30Live demo: RT1060 and MCX N
- 23:50Zephyr developer experience
- 27:02NXP’s Zephyr strategy
- 30:37Zephyr roadmap and collaboration
- 31:40Q&A
related talks
33mSponsored Session: Why NXP is Doubling Down on Zephyr Project
08mKeynote: Zephyr as the Foundation for a Microcontroller SDK
40mBof: Zephyr Community in Japan: From Hobbyist To Automotive, Roboti...
13mKeynote: How Zephyr Enables Industry Collaboration
39mZephyr Project: Unlocking IoT Innovation with an Open Source RTOS
31mA Zephyr User Story
49mThe Zephyr™ Project – An Updated Overview
01h 03mZephyr RTOS: Software power tools for constrained devices