Build, Flash, and View¶

NSX wraps the normal firmware lifecycle around generated CMake targets.

Run these commands from the app root when possible. NSX resolves the active app by walking upward to the nearest nsx.yml, so --app-dir is only needed when you want to target a different app explicitly.

sequenceDiagram
    participant User
    participant NSX CLI
    participant CMake
    participant J-Link
    participant SWO Viewer

    User->>NSX CLI: nsx configure
    NSX CLI->>CMake: cmake -G Ninja ...
    User->>NSX CLI: nsx build
    NSX CLI->>CMake: cmake --build
    CMake-->>NSX CLI: .axf / .bin
    User->>NSX CLI: nsx flash
    NSX CLI->>CMake: cmake --build (flash target)
    CMake->>J-Link: JLinkExe loadfile
    User->>NSX CLI: nsx view
    NSX CLI->>SWO Viewer: JLinkSWOViewerCL
    NSX CLI->>J-Link: Reset target
    SWO Viewer-->>User: SWO output stream

Configure¶

nsx configure

Build¶

nsx build

Flash¶

nsx flash

This builds the app if needed and then invokes the SEGGER flash path defined by the app’s generated CMake support.

View SWO Output¶

nsx view

nsx view launches the SEGGER SWO viewer for the active board target and uses a board-appropriate reset policy. Most boards open the viewer, wait briefly for it to attach, and then issue the app's normal SEGGER reset target. Apollo4 secure targets default to attach-only viewing because SEGGER's Apollo4 reset flow halts in the secure boot handoff and can make the SWO viewer exit.

If needed, you can force a reset with --reset-on-open, disable the reset with --no-reset-on-open, or adjust the attach delay with --reset-delay-ms.

Clean¶

nsx clean

Typical Sequence¶

nsx configure
nsx build
nsx flash
nsx view

For Apollo4 secure boards, the validated sequence is nsx flash followed by nsx view so the flash command's reset+go starts the app and view attaches without another reset. For Apollo510, the validated behavior is to keep the normal viewer-first reset sequence. A stronger SEGGER reset mode was not required.

If you are running from a source checkout, activate the uv environment first and then use the same nsx ... commands.