East - tool for building NCS/Zephyr applications
East is a command line meta-tool, useful for creating, managing, and deploying Zephyr or nRF Connect SDK (NCS) projects.
It is built on top of Zephyr's RTOS meta-tool West and Nordic's nRF Connect Toolchain Manager.
Documentation
docs directory contains several markdown documents about East:
- Installation - How to install East and its dependencies.
- Example Project - Quickly setup an example project and get it building with East.
- How East works - How East works under the hood and what to expect from it.
- Configuration - How to configure the
east.ymlfile. - Pack - How to use
east packcommand to create a release package. - Environmental variables - How to configure East using environmental variables.
- Development guide - How to setup the development environment for working on East.
Reasoning behind East
There are several reasons why someone would like to create yet another tool on top of west:
- Working on several projects at once means using different versions of the NCS repository and different versions of the toolchain. Managing these differences is not a trivial task.
- There is no reproducible build guarantee between the developer's machines. Slight differences between tool versions can manifest into hard-to-find bugs.
- Creating GitHub releases manually takes ages as you have to run the build process for every combination of the board, application, build variant, etc. and properly rename the release binary. The release procedure gets longer with every addition of new hardware and build variation option.
East automates the above tasks and tries to make the developer more productive.
Key features
- Automated detection and installation of tooling required for NCS projects.
- Common
westcommands used for the development, such asbuild,flash, etc. - Sandboxed development environment, thanks to the nRF Connect Toolchain Manager, every
build,flash, etc. command runs inside of its toolchain environment. - Automated process of packaging release artifacts for your entire project.
- RTT utility commands to connect and see the RTT stream.
- CodeChecker integration for static code analysis.
- Generating configuration files for the Cortex Debug VScode extension.
1 maintainer
Metadata
1 maintainer
Release files for east-tool 0.31.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| east_tool-0.31.7.tar.gz | 182.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| east_tool-0.31.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 264.8 kB
Release files / east_tool-0.31.7.tar.gz
| Download URL | east_tool-0.31.7.tar.gz |
|---|---|
| Size | 182.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4a04af0e54d53aed7dc0525e58ae580554598acf1c47b65917a1d76a7b6c4da9
|
|
BLAKE2b-256 checksum How to use checksums |
3f24c6c9a1c901b7710cc6d1c6090d723e12a1c30c18bf8dc5b3865c55e049b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 17, 2026.
Transparency logRelease files / east_tool-0.31.7-py3-none-any.whl
| Download URL | east_tool-0.31.7-py3-none-any.whl |
|---|---|
| Size | 82.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2ab07385c27a74355c05b0214742c936a2d326d2be502624cb48b8cfbd8fefde
|
|
BLAKE2b-256 checksum How to use checksums |
10d86b5ac3cc6f776f775246f37848d8ecb73cbb5ce229d2760d2da925850efd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 17, 2026.
Transparency log
