Development environments

Zephyr development needs host tools, Python packages, and target toolchains. Their compatible versions change between Zephyr releases.

Workshop keeps this software in a versioned development environment. The zephyr SDK channel binds the tools to Zephyr 26.04 LTS. The project directory stays on the host and is mounted at /project.

Why Workshop is the standard path

Workshop gives each developer the same base and SDK channel. It reduces differences between workstations and CI jobs.

An SDK refresh updates the tools as one tested unit. An immutable source tag selects the manifest and repository revisions as a separate tested unit. This design keeps tool updates separate from source updates.

Hardware access is explicit. Workshop requires explicit connection of custom-device interfaces. The developer grants access only when a board needs it.

When to install on your host system

A host system installation is useful where Workshop is unavailable. It is also useful when a developer must inspect each tool separately.

The host system path has the same source manifest and west workflow. However, the developer maintains the host packages, Python environment, Zephyr SDK, and device permissions.

Both paths produce standard Zephyr workspaces. They differ in how the host tools and toolchains are supplied.

See also

Tutorial:

• Get started with Workshop

How-to guides:

• How to install Zephyr 26.04 LTS on your host system

Reference:

• Workshop environment