Install and Setup¶
Everything you need to go from a blank terminal to a working nsx
command — in about five minutes.
The setup has four parts:
- System prerequisites — Python,
uv, CMake, Ninja, Git - Compiler toolchain — Arm GNU Toolchain (GCC) by default
- Debug probe — SEGGER J-Link (only needed to flash and view on hardware)
- The
nsxCLI — installed withpipx
Then nsx doctor checks the installed tools and reports anything missing.
No board yet?
You don't need hardware to start. nsx configure and nsx build work
with no probe attached — only nsx flash and nsx view need a connected
EVB. You can skip the J-Link step until you have a board, but nsx doctor
will still report J-Link as missing until it is installed.
Choose Your Platform¶
Steps 1–3 (host tools, compiler, debug probe) are platform-specific. Follow
the guide for your OS, then come back here for the CLI install and the
nsx doctor check.
4. Install the nsx CLI¶
The CLI install is the same on every platform. For app developers, the
cleanest option is pipx — it puts nsx on your
PATH in an isolated environment:
If you do not already have pipx, install it first:
Open a new terminal after ensurepath, then install neuralspotx:
To pin a specific published version:
Prefer a source checkout? (contributors)
Clone the repo and let uv manage the environment:
Then either activate the venv (source .venv/bin/activate) so nsx is on
your PATH, or prefix commands with uv run (e.g. uv run nsx doctor).
Verify with nsx doctor¶
Whatever install path you chose, confirm your environment:
doctor checks each prerequisite and prints a clear pass/fail per tool. A
fully provisioned host looks like:
Python ✓
uv ✓
cmake ✓
ninja ✓
git ✓
arm-none-eabi-gcc ✓
(armclang toolchain not detected — optional)
(ATfE not detected — optional)
J-Link ✓
The Arm GNU toolchain and SEGGER J-Link tools are required for the complete flash/view workflow; armclang and ATfE are optional and only reported when detected. If you intentionally skipped J-Link because you do not have hardware yet, expect the SEGGER checks to fail until you install it. Each failing check includes a hint describing what to install.
Docs Tooling (Optional)¶
Working on the documentation site? Install the docs dependencies:
Next Steps¶
Environment is ready — time to build your first app.