neuralspotx
neuralspotx is the NSX tooling repo.
NSX is a lightweight bare-metal workflow for Ambiq targets. It provides:
- the
nsxCLI - packaged app templates
- packaged CMake helpers
- built-in board definitions
- curated metadata for module and SDK selection
The primary audience is app developers creating small, focused NSX applications for bring-up, profiling, validation, and simple demos.
NSX is also the build-and-deploy vehicle for Ambiq's Helia AI stack:
- heliaRT — optimized LiteRT (TFLite Micro) runtime, shipped as an NSX module
- heliaAOT — ahead-of-time compiler that
generates NSX modules from
.tflitemodels - heliaPROFILER — on-device model profiler built on NSX
For contributor workflows such as releases, CI, and the Python API surface, use
the docs site under docs/.
Documentation
The main documentation lives in the docs site built from docs/.
Install the docs toolchain:
cd <nsx-repo>
uv sync --group docs
Run the docs site locally:
cd <nsx-repo>
uv run --group docs zensical serve
Build the static site:
cd <nsx-repo>
uv run --group docs zensical build
Quick Start
NSX uses an app-first flow. Each app is a self-contained project directory with vendored modules, board definitions, and build helpers.
For app users, the cleanest install path is pipx:
pipx install neuralspotx
nsx doctor
nsx create-app hello_ap510 --board apollo510_evb
For contributors working from a source checkout:
cd <nsx-repo>
uv sync
source .venv/bin/activate
uv tool install pre-commit
pre-commit install
nsx doctor
nsx create-app hello_ap510 --board apollo510_evb
pre-commit install sets up the lint and pre-push hooks that CI also runs. See docs/contributing/index.md for
what runs at each stage.
Build the app:
nsx configure --app-dir hello_ap510
nsx build --app-dir hello_ap510
Repo Scope
This repo owns:
src/neuralspotx- packaged documentation and templates
- packaged board definitions
- CMake helper assets used by generated apps
Built-in firmware modules are described by the packaged registry and fetched from their default upstream repos as needed. Normal app users create standalone app directories and let NSX manage module resolution, vendoring, configuration, build, flash, and view flows.
Metadata
Release files for neuralspotx 0.8.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| neuralspotx-0.8.1.tar.gz | 348.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| neuralspotx-0.8.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 706.5 kB
Release files / neuralspotx-0.8.1.tar.gz
| Download URL | neuralspotx-0.8.1.tar.gz |
|---|---|
| Size | 348.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1f57b69c8078ed5a08dcbe55e9fa66f68bbaac44a775c4612503e7eb1fd6b1c3
|
|
BLAKE2b-256 checksum How to use checksums |
fc6cc5bbc95b609c8e6312469fff511960341bdee14e35044604c4601e70a442
|
| 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 10, 2026.
Transparency logRelease files / neuralspotx-0.8.1-py3-none-any.whl
| Download URL | neuralspotx-0.8.1-py3-none-any.whl |
|---|---|
| Size | 357.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7aac6f1b2e89ebf41dfe087c7588e0db11d65e8a11cac2cda03f6d7c510a9094
|
|
BLAKE2b-256 checksum How to use checksums |
a4e77e4acc9912a07977915314ec5985229889c46a07720bf9a7311cae2213a2
|
| 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 10, 2026.
Transparency log
