Skip to content

nsx flash

Builds and flashes a generated NSX app.

Syntax

nsx flash [--app-dir APP_DIR] [--board BOARD]
          [--build-dir BUILD_DIR] [--toolchain TOOLCHAIN]
          [--target TARGET] [--probe-serial PROBE_SERIAL] [--jobs JOBS]
          [--update] [--frozen] [--timeout SECONDS] [app]

Main Arguments

  • --app-dir: app directory containing nsx.yml; when omitted, NSX searches upward from the current directory
  • app: optional app name or directory; overrides --app-dir and is resolved under the current directory and examples/
  • --board: select a board from the app's supported targets instead of targets.default
  • --build-dir: build directory override
  • --toolchain: toolchain override (gcc, armclang, atfe). Defaults to nsx.yml → arm-none-eabi-gcc
  • --target: optional executable target to flash; omitted selects the app's primary executable
  • --probe-serial: select one J-Link explicitly when multiple probes are attached
  • --jobs: parallel build jobs
  • --update: re-resolve module constraints to upstream tips and re-vendor before flashing
  • --frozen: when configure is needed, reject manifest, lock, or vendored-module drift; explicit probe selection still forces configure
  • --timeout: wall-clock budget per subprocess; a timeout terminates the process group

Example

cd <app-dir>
nsx flash

# Flash another executable finalized by the same NSX/CMake project.
nsx flash --target hpx_profiler_power

Notes

  • discovers J-Link Commander from JLINK_PATH, PATH, or the standard SEGGER install locations on Linux, macOS, and Windows; the resolved path is passed into CMake so discovery is consistent across NSX operations
  • uses the board-defined flash settings
  • requires the selected target's .bin and generated jlink/<target>/flash_cmds.jlink recipe
  • rejects a successful process exit unless J-Link reports an actual flash-download operation
  • run nsx commands --json for the authoritative machine-readable argument schema