TT-Lensium :tm:
A low-level hardware debugger
A low-level debugging tool for Tenstorrent hardware that enables direct access to and communication with Wormhole and Blackhole devices.
Quickstart
You can install latest published version with:
pip install tt-exalens
Or specific version with:
pip install tt-exalens=="x.y.z"
Alternatively, you can install the latest code from GitHub with:
pip install git+https://github.com/tenstorrent/tt-exalens.git
The CLI application can be run by invoking the tt-exalens command after installing the wheel.
Running the CLI application
The CLI application can be run via the tt-exalens.py script or by invoking the tt-exalens command after installing the wheel.
The application supports both local and remote device access. For remote connections, a server instance must be started using the same application.
A GDB server can be launched, enabling stepping, breakpoints, and other debugging features via a GDB client.
For more usage information, refer to the tutorial or the documentation.
Using library
The application functionality is also available through the ttexalens Python library, enabling you to create custom scripts that interact with Tenstorrent hardware.
For a quick start with the library, check out the tutorial. Full documentation is also available here.
Development
Setting up environment
The recommended way to manage dependencies is by creating a virtual environment with:
./scripts/create-venv.sh
To activate the created environment, use:
.venv/bin/activate
Alternatively, you can use your existing environment and just install dependencies with:
./scripts/install-deps.sh
Testing
Test requirements
The following dependencies are required to build the necessary kernels:
- ninja-build,
- cmake
- make
Running tests
The easiest way to run all tests locally is by using the make wrapper from the project root directory:
make test
This command will build dependencies, run all tests, create the wheel, and run wheel tests.
If you don't need all of these steps, you can run them manually:
# Compile kernels that tests use
make
# Install runtime dependencies
pip install -r ttexalens/requirements.txt
# Install test dependencies
pip install -r test/test_requirements.txt
# Run library tests
pytest test/ttexalens
# Run CLI application tests
pytest test/app
If you're developing with VSCode (or its derivatives), you can use the Testing extension. Install the Python extension to enumerate all tests within the Testing tab in the activity bar.
Updating documentation
Library documentation is automatically generated from source code docstrings. To update the library documentation, run the following command in your development environment:
make docs
in the project root.
For more advanced use cases, refer to the source code of the documentation generation scripts, located in docs/bin.
Static checks
Pre-commit
We have defined various pre-commit hooks that check the code for formatting, licensing issues, etc.
To install pre-commit, run the following command:
pip install pre-commit
After installing pre-commit, you can install the hooks by running:
pre-commit install
Now, each time you run git commit the pre-commit hooks (checks) will be executed.
If you have already committed before installing the pre-commit hooks, you can run on all files to "catch up":
pre-commit run --all-files
For more information visit pre-commit
mypy
We use mypy for static code analysis.
You can use the make wrapper to execute it with:
make mypy
Or run it directly from your development environment with:
mypy
1 maintainer
Metadata
1 maintainer
Release files for tt-exalens 0.3.32
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| tt_exalens-0.3.32-cp313-cp313-manylinux_2_34_x86_64.whl | CPython 3.13 | CPython 3.13 | Linux glibc 2.34+ x86-64 | Details |
| tt_exalens-0.3.32-cp313-cp313-manylinux_2_34_aarch64.whl | CPython 3.13 | CPython 3.13 | Linux glibc 2.34+ ARM64 | Details |
| tt_exalens-0.3.32-cp312-cp312-manylinux_2_34_x86_64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.34+ x86-64 | Details |
| tt_exalens-0.3.32-cp312-cp312-manylinux_2_34_aarch64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.34+ ARM64 | Details |
| tt_exalens-0.3.32-cp311-cp311-manylinux_2_34_x86_64.whl | CPython 3.11 | CPython 3.11 | Linux glibc 2.34+ x86-64 | Details |
| tt_exalens-0.3.32-cp311-cp311-manylinux_2_34_aarch64.whl | CPython 3.11 | CPython 3.11 | Linux glibc 2.34+ ARM64 | Details |
| tt_exalens-0.3.32-cp310-cp310-manylinux_2_34_x86_64.whl | CPython 3.10 | CPython 3.10 | Linux glibc 2.34+ x86-64 | Details |
| tt_exalens-0.3.32-cp310-cp310-manylinux_2_34_aarch64.whl | CPython 3.10 | CPython 3.10 | Linux glibc 2.34+ ARM64 | Details |
Total release size: 7.5 MB
Release files / tt_exalens-0.3.32-cp313-cp313-manylinux_2_34_x86_64.whl
| Download URL | tt_exalens-0.3.32-cp313-cp313-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 952.9 kB |
| Tags | CPython 3.13 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
5f2279a8e7e638eabc3c57bf86c40b2c6a4e9f3877bc84843bff74fd06f63398
|
|
BLAKE2b-256 checksum How to use checksums |
c5b0c21b02627944230aacf37182c01f637df22e767e04d3a6b092caa5d40b95
|
| 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 2, 2026.
Transparency logRelease files / tt_exalens-0.3.32-cp313-cp313-manylinux_2_34_aarch64.whl
| Download URL | tt_exalens-0.3.32-cp313-cp313-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 917.3 kB |
| Tags | CPython 3.13 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
1677b465104d85e5806946a760b1e6a58b05002c10dd7b25587c68ed8b774d20
|
|
BLAKE2b-256 checksum How to use checksums |
812fcc651d944e4e84cd8bead3ac46e62542857d536a264e2701c9bd043990f3
|
| 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 2, 2026.
Transparency logRelease files / tt_exalens-0.3.32-cp312-cp312-manylinux_2_34_x86_64.whl
| Download URL | tt_exalens-0.3.32-cp312-cp312-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 953.0 kB |
| Tags | CPython 3.12 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
8f6b35c57c0059d4039c56c9c787d2251ed3b5e8d06ce8dc33e542a91abe615b
|
|
BLAKE2b-256 checksum How to use checksums |
f5c681fce3518e66bf9a8cf7f206f235ced0417d438751d6d6f864cff7ffe3d0
|
| 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 2, 2026.
Transparency logRelease files / tt_exalens-0.3.32-cp312-cp312-manylinux_2_34_aarch64.whl
| Download URL | tt_exalens-0.3.32-cp312-cp312-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 917.4 kB |
| Tags | CPython 3.12 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
907f2625cd8fdf6572b2227c95939f9599ce4b0a82f73eaf02d7ba4237609732
|
|
BLAKE2b-256 checksum How to use checksums |
545477df90c8bc6ff51d3d3301a4e3207fafae090c0b740aabec21c6a448f147
|
| 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 2, 2026.
Transparency logRelease files / tt_exalens-0.3.32-cp311-cp311-manylinux_2_34_x86_64.whl
| Download URL | tt_exalens-0.3.32-cp311-cp311-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 953.5 kB |
| Tags | CPython 3.11 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
a6991194232b7faa33bc00ff795dc0542814a845fa5d0ec226dc2bb95594cea7
|
|
BLAKE2b-256 checksum How to use checksums |
0e8d6a99432198968118b5a7cef984f8b7dd312bc76c09684e3426ee8fc3041d
|
| 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 2, 2026.
Transparency logRelease files / tt_exalens-0.3.32-cp311-cp311-manylinux_2_34_aarch64.whl
| Download URL | tt_exalens-0.3.32-cp311-cp311-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 918.1 kB |
| Tags | CPython 3.11 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
3d10649b421472618bc471659944365be4fb7bc151e0210c67d4b8d92a8f71f3
|
|
BLAKE2b-256 checksum How to use checksums |
38ff9821eaa5e38166ba2c1472d4979d2950aaf05597dcc0f2cfc099e1d129d0
|
| 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 2, 2026.
Transparency logRelease files / tt_exalens-0.3.32-cp310-cp310-manylinux_2_34_x86_64.whl
| Download URL | tt_exalens-0.3.32-cp310-cp310-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 953.3 kB |
| Tags | CPython 3.10 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
751a951df90a82bcb526f20a22d6b9b8c2e5c129b2cabdd4c9a3f9b3e918ad91
|
|
BLAKE2b-256 checksum How to use checksums |
8b989ec97c6274b0561e4bff2bb60ad8b4c802d10b26a040b31bb1ff4789e89e
|
| 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 2, 2026.
Transparency logRelease files / tt_exalens-0.3.32-cp310-cp310-manylinux_2_34_aarch64.whl
| Download URL | tt_exalens-0.3.32-cp310-cp310-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 917.9 kB |
| Tags | CPython 3.10 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
f9b7f19250b58e2d5136edb59d95166ec6e05cd2a73ce4ae9a26ccabe9627ce1
|
|
BLAKE2b-256 checksum How to use checksums |
860afaee31826f5ee47ca1d246d048a25eb903df5f4bb3561e05772fe40ed6ee
|
| 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 2, 2026.
Transparency log
