Build, Flash, and View¶

NSX wraps the normal firmware lifecycle around generated CMake targets.

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 --app-dir <app-dir>

Build¶

nsx build --app-dir <app-dir>

Flash¶

nsx flash --app-dir <app-dir>

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 --app-dir <app-dir>

nsx view launches the SEGGER SWO viewer for the active board target, waits briefly for the viewer to attach, and then issues the app's normal SEGGER reset target. This keeps the default reset behavior while avoiding the common case where SWO is empty because the target was already running before the viewer attached.

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

Clean¶

nsx clean --app-dir <app-dir>

Typical Sequence¶

nsx configure --app-dir <app-dir>
nsx build --app-dir <app-dir>
nsx flash --app-dir <app-dir>
nsx view --app-dir <app-dir>

For Apollo510, the validated behavior is to keep the normal Reset sequence and open the viewer before resetting. 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.