Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions MAINTAINERS.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2893,6 +2893,19 @@ Input:
- drivers.input
- input

Instrumentation Subsystem:
status: maintained
maintainers:
- fkokosinski
- tgorochowik
files:
- include/zephyr/instrumentation/
- samples/subsys/instrumentation/
- scripts/instrumentation/
- subsys/instrumentation/
labels:
- "area: Instrumentation"

Intel Platforms (Agilex):
status: maintained
maintainers:
Expand Down
6 changes: 3 additions & 3 deletions samples/subsys/instrumentation/README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -40,18 +40,18 @@ Alternatively you can run this using QEMU:

After the sample is flashed to the target (or QEMU is running), it must be possible to
collect and visualize traces and profiling info using the instrumentation CLI
tool, :zephyr_file:`scripts/zaru.py`.
tool, :zephyr_file:`scripts/instrumentation/zaru.py`.

.. note::
Please note, that this subsystem uses the ``retained_mem`` driver, hence it's necessary
to add the proper devicetree overlay for the target board. See
:zephyr_file:`./samples/subsys/instrumentation/boards/mps2_an385.overlay` for an example.

Connect the board's UART port to the host device and
run the :zephyr_file:`scripts/zaru.py` script on the host.
run the :zephyr_file:`scripts/instrumentation/zaru.py` script on the host.

Source the :zephyr_file:`zephyr-env.sh` file to set the ``ZEPHYR_BASE`` variable and get
:zephyr_file:`scripts/zaru.py` in your PATH:
:zephyr_file:`scripts/instrumentation/zaru.py` in your PATH:

.. code-block:: console

Expand Down
File renamed without changes.
Loading