Zephyr®

Scalable. Secure. Open Source. The Zephyr® RTOS is a scalable, open-source real-time operating system optimized for resource-constrained devices.

nobutton

About

Zephyr® is a free, open-source real-time operating system (RTOS) designed to scale from simple, resource-constrained sensing applications up to complex, connected, compute-intensive edge devices - without forcing a rewrite as your design grows. That range matters on Infineon silicon in particular: the same Zephyr® foundation runs on power- and memory-constrained devices like PSOC™ 4, and on higher-compute, AI-capable devices like PSOC™ Edge, so you're not choosing a different OS for every point in your product line.

Infineon's Platinum membership underscores its commitment to strengthening Zephyr® enablement across its MCU, automotive MCU, and connectivity portfolios and developer workflows - supporting accelerated development and consistent software reuse for connected devices across industrial, consumer, and automotive markets. As a Platinum member, Infineon also contributes to Zephyr's strategic working groups, including secure update and lifecycle management for IoT devices, safety concepts for automotive and industrial controllers, and long-term support strategies for qualified software baselines. Infineon builds and maintains Zephyr® support across its silicon portfolio - SoC, driver, and devicetree enablement spanning PSOC™ MCUs, TRAVEO™ T2G MCUs, AURIX™ TriCore™ MCUs, AIROC™ Bluetooth® and multiprotocol devices, and XMC™ MCUs - so you get a direct, first-party path to Zephyr® on Infineon hardware rather than a third-party or community-only port.

Zephyr project member logo

Mainline first, with early access when you need it. Our goal is for every feature to live in mainline Zephyr® - the community-governed repository anyone can build against with no vendor lock-in. For newer silicon or in-development features (like CAPSENSE™ middleware integration), Infineon also maintains downstream repositories that carry support ahead of upstream acceptance, so early adopters can get moving sooner while that same code is actively being upstreamed - consolidating back into mainline over time, not fragmenting away from it.

This is an ongoing commitment, not a one-time integration: our engineering teams continue to resolve upstream issues, extend driver coverage, and enable new silicon as our product portfolio grows.

Zephyr®  support spans Infineon's MCU, automotive MCU, and connectivity portfolios, giving developers a consistent, first-party path to Zephyr®  on Infineon hardware - from cost-sensitive general-purpose MCUs to AI-enabled edge devices - across industrial, consumer, and automotive designs. Coverage grows as new boards are added, and the list below reflects what's supported in Zephyr®  today, organized by product family. For the complete, always-current list of supported Infineon boards, see the Zephyr® Boards documentation.

 

PSOC™ Edge (PSE84)

 

PSOC™ Control (C3/PSC3)

 

TRAVEO™ T2G

 

AURIX™ (TC3x/TC4x)

Zephyr® upstream support in progress - refer to Infineon/zephyr-aurix for access.

  • Application Kit TC397 ADAS (KIT_A2G_TC397XA_3V3_TFT)
  • Application Kit TC3X7 (KIT_A2G_TC3X7_TFT)
  • KIT A3G TC4D7 Lite (KIT_A3G_TC4D7_LITE)
  • TC375 LiteKit (KIT_A2G_TC375_LITE)
  • TriBoard TC377TX (KIT_A2G_TC377TX_3V3_TR)
  • TriBoard TC3X6 (KIT_A2G_TC3X6_TRB)
  • TriBoard TC3X7 (KIT_A2G_TC3X7_TRB)
  • TriBoard TC4x7 COM (KIT_TC4X7_COM_TRB)

 

AIROC™

 

PSOC™ 4

 

PSOC™ 6

 

XMC™ 7000

 

XMC™ 4000

 

Looking for a specific part number? Board pages above list the reference kit, not every individual MPN variant. To confirm exact MPN-level support, check the board and devicetree files directly in the Zephyr GitHub repository - each board's .dts/.yaml defines precisely which part numbers it targets.

Zephyr's kernel and subsystem set covers what most embedded projects need out of the box - real-time scheduling, memory protection, and native connectivity - so your team can move straight from board bring-up into application development instead of assembling and integrating a separate RTOS, network stack, and driver framework. These are core Zephyr® capabilities, available unmodified across every supported Infineon device.

  • Highly configurable, highly modular, open-source real time operating system
  • Comprehensive, lightweight kernel
  • Supports cooperative and preemptive threading
  • Memory and resources are typically statically allocated
  • Integrated device driver interface
  • Memory protection: stack overflow protection, kernel object and device driver permission tracking, thread isolation
  • Highly connected:
    • Bluetooth® 5.0 and Bluetooth® Low Energy (with both controller and host, BLE Mesh)
    •  Wi-Fi, Ethernet, CANbus
    •  IoT protocols: CoAP, LwM2M, MQTT
    •  USB & USB-C
  • Native, fully featured and optimized networking stack
  • Supports a range of subsystems, including USB, filesystem, logging, DFU
  • Open-source graphics library through LVGL
Zephyr® architecture diagram

Getting Zephyr® running on Infineon hardware follows these stages:

1. Set up your development environment

  • Install west, Zephyr's workspace and build tool
  • Install host build dependencies for your OS (Windows, macOS, or Linux) - CMake, Python, and a device tree compiler

2. Get the Zephyr® source

  • Create a workspace with west
  • Fetch the Zephyr® repository, along with the hardware abstraction layers (HALs) and libraries it depends on

3. Install the Zephyr® SDK

  • Run the SDK installer (west sdk install)
  • Select the toolchain for your target architecture (Arm® Cortex®-M, for most Infineon boards)

4. Build a sample application

  • Pick a sample app, such as Hello World or Blinky
  • Run west build, targeting your board

5. Program and debug your board

  • Install the ModusToolbox™ Programming Tools - provides Infineon's OpenOCD build and KitProg3 drivers, needed for Infineon boards' onboard KitProg3 programmer/debugger
  • Flash your application with west flash
  • Debug with west debug (GDB-based)

Full step-by-step instructions are in the Zephyr® Getting Started Guide; once you're past your first build, Beyond the Getting Started Guide covers next steps like structuring your own application and choosing a build/flash workflow. Board-specific flashing/debugging details are on each board's own documentation page (see picks below).

Pick a board to try it on:

 

For the full list of supported Infineon boards, see the Supported Products tab above.

Zephyr® is developed in the open, upstream, by the Zephyr®  Project community - and Infineon builds on that foundation with our own downstream repositories, where new hardware support and features land first before they're contributed upstream. Start with the general Zephyr®  resources and community links below, or jump straight to the mainline Zephyr®  repository or Infineon's own downstream repositories for Infineon-specific enablement.

Zephyr® Project Resources

  • Zephyr® documentation - official build, configuration, and API documentation, including board-specific pages.

 

Upstream (Zephyr® Project repository)

  • Zephyr® on GitHub - the mainline Zephyr® RTOS source tree: kernel, subsystems, drivers, and board support for the entire ecosystem, including Infineon's upstream contributions.

 

Downstream (Infineon repositories)

  • Infineon/ifx-zephyr-sdk - a west manifest and sample apps that layer Infineon-specific dependencies on top of upstream Zephyr® in one west init, for teams who want the Infineon extras alongside mainline Zephyr®.
  • Infineon/ifx-zephyr - Infineon's main downstream fork; early-access features and fixes ahead of upstream acceptance.

Zephyr® is a free, open-source real-time operating system (RTOS) designed to scale from simple, resource-constrained sensing applications up to complex, connected, compute-intensive edge devices - without forcing a rewrite as your design grows. That range matters on Infineon silicon in particular: the same Zephyr® foundation runs on power- and memory-constrained devices like PSOC™ 4, and on higher-compute, AI-capable devices like PSOC™ Edge, so you're not choosing a different OS for every point in your product line.

Infineon's Platinum membership underscores its commitment to strengthening Zephyr® enablement across its MCU, automotive MCU, and connectivity portfolios and developer workflows - supporting accelerated development and consistent software reuse for connected devices across industrial, consumer, and automotive markets. As a Platinum member, Infineon also contributes to Zephyr's strategic working groups, including secure update and lifecycle management for IoT devices, safety concepts for automotive and industrial controllers, and long-term support strategies for qualified software baselines. Infineon builds and maintains Zephyr® support across its silicon portfolio - SoC, driver, and devicetree enablement spanning PSOC™ MCUs, TRAVEO™ T2G MCUs, AURIX™ TriCore™ MCUs, AIROC™ Bluetooth® and multiprotocol devices, and XMC™ MCUs - so you get a direct, first-party path to Zephyr® on Infineon hardware rather than a third-party or community-only port.

Zephyr project member logo

Mainline first, with early access when you need it. Our goal is for every feature to live in mainline Zephyr® - the community-governed repository anyone can build against with no vendor lock-in. For newer silicon or in-development features (like CAPSENSE™ middleware integration), Infineon also maintains downstream repositories that carry support ahead of upstream acceptance, so early adopters can get moving sooner while that same code is actively being upstreamed - consolidating back into mainline over time, not fragmenting away from it.

This is an ongoing commitment, not a one-time integration: our engineering teams continue to resolve upstream issues, extend driver coverage, and enable new silicon as our product portfolio grows.

Zephyr®  support spans Infineon's MCU, automotive MCU, and connectivity portfolios, giving developers a consistent, first-party path to Zephyr®  on Infineon hardware - from cost-sensitive general-purpose MCUs to AI-enabled edge devices - across industrial, consumer, and automotive designs. Coverage grows as new boards are added, and the list below reflects what's supported in Zephyr®  today, organized by product family. For the complete, always-current list of supported Infineon boards, see the Zephyr® Boards documentation.

 

PSOC™ Edge (PSE84)

 

PSOC™ Control (C3/PSC3)

 

TRAVEO™ T2G

 

AURIX™ (TC3x/TC4x)

Zephyr® upstream support in progress - refer to Infineon/zephyr-aurix for access.

  • Application Kit TC397 ADAS (KIT_A2G_TC397XA_3V3_TFT)
  • Application Kit TC3X7 (KIT_A2G_TC3X7_TFT)
  • KIT A3G TC4D7 Lite (KIT_A3G_TC4D7_LITE)
  • TC375 LiteKit (KIT_A2G_TC375_LITE)
  • TriBoard TC377TX (KIT_A2G_TC377TX_3V3_TR)
  • TriBoard TC3X6 (KIT_A2G_TC3X6_TRB)
  • TriBoard TC3X7 (KIT_A2G_TC3X7_TRB)
  • TriBoard TC4x7 COM (KIT_TC4X7_COM_TRB)

 

AIROC™

 

PSOC™ 4

 

PSOC™ 6

 

XMC™ 7000

 

XMC™ 4000

 

Looking for a specific part number? Board pages above list the reference kit, not every individual MPN variant. To confirm exact MPN-level support, check the board and devicetree files directly in the Zephyr GitHub repository - each board's .dts/.yaml defines precisely which part numbers it targets.

Zephyr's kernel and subsystem set covers what most embedded projects need out of the box - real-time scheduling, memory protection, and native connectivity - so your team can move straight from board bring-up into application development instead of assembling and integrating a separate RTOS, network stack, and driver framework. These are core Zephyr® capabilities, available unmodified across every supported Infineon device.

  • Highly configurable, highly modular, open-source real time operating system
  • Comprehensive, lightweight kernel
  • Supports cooperative and preemptive threading
  • Memory and resources are typically statically allocated
  • Integrated device driver interface
  • Memory protection: stack overflow protection, kernel object and device driver permission tracking, thread isolation
  • Highly connected:
    • Bluetooth® 5.0 and Bluetooth® Low Energy (with both controller and host, BLE Mesh)
    •  Wi-Fi, Ethernet, CANbus
    •  IoT protocols: CoAP, LwM2M, MQTT
    •  USB & USB-C
  • Native, fully featured and optimized networking stack
  • Supports a range of subsystems, including USB, filesystem, logging, DFU
  • Open-source graphics library through LVGL
Zephyr® architecture diagram

Getting Zephyr® running on Infineon hardware follows these stages:

1. Set up your development environment

  • Install west, Zephyr's workspace and build tool
  • Install host build dependencies for your OS (Windows, macOS, or Linux) - CMake, Python, and a device tree compiler

2. Get the Zephyr® source

  • Create a workspace with west
  • Fetch the Zephyr® repository, along with the hardware abstraction layers (HALs) and libraries it depends on

3. Install the Zephyr® SDK

  • Run the SDK installer (west sdk install)
  • Select the toolchain for your target architecture (Arm® Cortex®-M, for most Infineon boards)

4. Build a sample application

  • Pick a sample app, such as Hello World or Blinky
  • Run west build, targeting your board

5. Program and debug your board

  • Install the ModusToolbox™ Programming Tools - provides Infineon's OpenOCD build and KitProg3 drivers, needed for Infineon boards' onboard KitProg3 programmer/debugger
  • Flash your application with west flash
  • Debug with west debug (GDB-based)

Full step-by-step instructions are in the Zephyr® Getting Started Guide; once you're past your first build, Beyond the Getting Started Guide covers next steps like structuring your own application and choosing a build/flash workflow. Board-specific flashing/debugging details are on each board's own documentation page (see picks below).

Pick a board to try it on:

 

For the full list of supported Infineon boards, see the Supported Products tab above.

Zephyr® is developed in the open, upstream, by the Zephyr®  Project community - and Infineon builds on that foundation with our own downstream repositories, where new hardware support and features land first before they're contributed upstream. Start with the general Zephyr®  resources and community links below, or jump straight to the mainline Zephyr®  repository or Infineon's own downstream repositories for Infineon-specific enablement.

Zephyr® Project Resources

  • Zephyr® documentation - official build, configuration, and API documentation, including board-specific pages.

 

Upstream (Zephyr® Project repository)

  • Zephyr® on GitHub - the mainline Zephyr® RTOS source tree: kernel, subsystems, drivers, and board support for the entire ecosystem, including Infineon's upstream contributions.

 

Downstream (Infineon repositories)

  • Infineon/ifx-zephyr-sdk - a west manifest and sample apps that layer Infineon-specific dependencies on top of upstream Zephyr® in one west init, for teams who want the Infineon extras alongside mainline Zephyr®.
  • Infineon/ifx-zephyr - Infineon's main downstream fork; early-access features and fixes ahead of upstream acceptance.
Documents

Design resources