ZView, a Zephyr RTOS runtime visualizer
Real-time system observability for Zephyr RTOS, delivered over SWD.
Stop guessing your stack margins and heap health. ZView provides a zero-footprint, high-fidelity visualization of your Zephyr application’s runtime, delivered over SWD with zero instrumentation.
No UART, no RTT, and no manual code changes. Just Kconfig and your probe.
This page covers the standalone pip installation. If you are using ZView inside a west workspace (the most common setup), see the main documentation instead.
Prerequisites
To properly analyze your Zephyr app, your ELF binary must be compiled with specific Kconfig options enabled:
## prj.conf
CONFIG_INIT_STACKS=y # Required for stack watermarks
CONFIG_THREAD_MONITOR=y # Required for thread discovery
CONFIG_THREAD_STACK_INFO=y # Required for thread metadata
# Optional Features
CONFIG_THREAD_NAME=y # Enables thread name display
CONFIG_THREAD_RUNTIME_STATS=y # Enables CPU usage tracking
CONFIG_SYS_HEAP_RUNTIME_STATS=y # Enables heap runtime stats and fragmentation map
Installation
Install ZView in your Python virtual environment:
pip install zview
Or from the root of the repository:
pip install .
How to Use
# Example: nRF5340 DK via JLink
zview -e build/zephyr/zephyr.elf -r jlink -t nRF5340_xxAA
Commands
ZView is invoked through one of four commands. Bare zview ... is a shortcut for zview live ....
| Command | Purpose | TUI |
|---|---|---|
live |
Attach to a probe and render the TUI. Default when no command is given. | yes |
record |
Capture a live session to a .ndjson.gz recording file and exit. |
no |
replay |
Render the TUI from a previously captured recording. | yes |
dump |
Emit a single polling frame and exit. | no |
Common arguments
| Argument | Used by | Description |
|---|---|---|
-e, --elf-file |
all | Path to the firmware .elf file. |
-r, --runner |
live, record, dump |
Debug runner: jlink, nrfutil, pyocd, or gdb. |
-t, --runner-target |
live, record, dump |
MCU descriptor for the chosen runner (see below). |
--period |
live, record, dump |
Polling period in seconds (default: 0.10). |
Command-specific arguments
| Argument | Command | Description |
|---|---|---|
-o, --output |
record |
Recording target path (.ndjson.gz). |
--duration |
record |
Recording upper bound, in seconds. |
--frames |
record |
Recording upper bound, in data frames. |
-i, --input |
replay, dump |
Recording source path (.ndjson.gz). |
--no-pacing |
replay |
Drain the recording as fast as possible instead of honoring its wall-clock cadence. |
--frame |
dump |
Which polling frame to emit (1-indexed; default: 1). |
--json |
dump |
Emit the frame as JSON on stdout. |
Finding the right value for -t
The -t argument is the MCU descriptor name as expected by your chosen runner. How to find it depends on the runner:
JLink (-r jlink)
Use the device name from the J-Link Supported Devices list.
# Example: Nordic nRF5340 DK
zview -e build/zephyr/zephyr.elf -r jlink -t nRF5340_xxAA
nrfutil (-r nrfutil)
zview -e build/zephyr/zephyr.elf -r nrfutil -t 001057722700
pyOCD (-r pyocd)
Run pyocd list --targets to see the available target names for your installed packs.
pyocd list --targets # find your target name
# Example: STM32F401 Nucleo
zview -e build/zephyr/zephyr.elf -r pyocd -t stm32f401xe
GDB server (-r gdb)
Pass the host:port of your GDB server instead of a device name.
zview -e build/zephyr/zephyr.elf -r gdb -t localhost:1234
For navigation, offline recording/replay workflows, advanced usage, and QEMU/GDB targets, refer to the main documentation.
1 maintainer
Release files for zview 0.14.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| zview-0.14.0.tar.gz | 58.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zview-0.14.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 95.8 kB
Release files / zview-0.14.0.tar.gz
| Download URL | zview-0.14.0.tar.gz |
|---|---|
| Size | 58.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8d18cf47a2b718f6219169ce3fcf7298cbb6661b01852d54293cdfca6911a43b
|
|
BLAKE2b-256 checksum How to use checksums |
e952c93e3c1e4cf9ca7c2626dbcbf41a6dbea117d6fd652de4b2650b9dcd9c4d
|
| 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 Sep 11, 2026.
Transparency logRelease files / zview-0.14.0-py3-none-any.whl
| Download URL | zview-0.14.0-py3-none-any.whl |
|---|---|
| Size | 36.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8d1137f437f2615761314568f72f06b57e103e544332ec25804a6ddbaa6a643d
|
|
BLAKE2b-256 checksum How to use checksums |
a2423a9ba8d71946a83d6f0f29765319da1502ae9e1a3ee54cc8cda464fb01a2
|
| 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 Sep 11, 2026.
Transparency log
