Run on a device you cannot install Wingman on

Build a pipeline on this machine and run it on an Axelera machine that keeps only the Voyager runtime, over your own ssh.

A device target is an Axelera machine you can reach with ssh but cannot install Axelera Wingman on. It can carry a card of either generation in Hardware generations & product names. Wingman builds the pipeline here, sends it to the device as a bundle, runs it there and brings the results back. It installs nothing on the device: it only writes into one stage folder.

What the device needs

Run a bundle on the device

  1. Add the target

    wingman target add cell3 --ssh <alias> saves the target. The alias comes from your own ssh config.

  2. Probe it

    wingman target probe cell3 records the device’s runtime release and host facts. Add --interactive the first time to answer a password or second-factor prompt.

  3. Pack the bundle

    wingman target pack --bundle <package> --target cell3 writes the bundle manifest and prints the bundle id.

  4. Push it

    wingman target push cell3 --bundle <package> sends it.

  5. Run it

    wingman target run cell3 --bundle <id> --follow starts the device check and streams its log.

  6. Pull the results

    wingman target pull cell3 --bundle <id> brings results/ back.

Approval

Where the results land

The results land in the package’s results/ folder, with results/PULL_SUMMARY.json. Run ./RUN_HERE.sh --author-check in the package to finish validation here. A bundle carried back by hand writes results/IMPORT_SUMMARY.json instead.

Gated and offline devices

If your administrator only allows reviewed bundles, ask for the gate script: it admits only bundles whose id they listed. A device with no network path takes the bundle by hand, with export and import. Device targets reference covers both.