Skip to main content

Pair with a DevKit

Pair the SDK with a DevKit when the DevKit is on the same network as the SDK host. Pairing enables DevKit Sync, which exposes one shared workspace across the host, SDK container, and DevKit.

Host-Container-DevKit workspace mapping

The same workspace is mounted into the SDK container and the DevKit as /workspace, so build artifacts, logs, traces, and model files are visible from each environment.

Pair the Environment​

Run this setup command from the host before opening the SDK shell:

sima-cli sdk setup --devkit {devkit-ip}

During setup:

  • Select container ghcr.io-sima-neat-sdk-latest if multiple SDK containers are present.
  • Enter the host admin password when prompted for NFS server setup on the host.
  • Enter the DevKit user sima password, edgeai, when prompted for NFS client setup on the DevKit.

When setup succeeds, you should see output similar to:

============================================================
  DevKit Connected
============================================================
  DevKit target : sima@192.168.91.221:22
  Mounted path  : /workspace
  Host export   : 192.168.74.48:/Users/joey/workspace

  You can now run DevKit binaries from this SDK shell:
    dk /workspace/<path-to-arm64-binary> [args...]
============================================================

Update an Existing Pairing​

Use this flow when the Neat Development Environment is already installed and you need to pair a different DevKit or update the pairing after your DevKit IP address changed.

From inside the SDK container, run:

source devkit.sh <devkit-ip>

Replace <devkit-ip> with the IP address of the DevKit you want to use.

Example:

source devkit.sh 192.168.91.221

Set Up Without DevKit Pairing​

Use this flow when the DevKit is not reachable from the SDK host:

sima-cli sdk setup

You can still build binaries in the SDK container, but you must transfer them to the DevKit manually for testing. Make sure the DevKit is running a compatible Neat Library version.

File Sharing with DevKit Sync​

DevKit Sync connects three environments:

  1. Host
  2. SDK container
  3. DevKit

sima-cli sdk setup --devkit {devkit-ip} configures NFS so the same workspace is available in all three environments:

  • The host workspace folder is exported through host NFS.
  • The folder is mounted into the SDK container as /workspace.
  • The same content appears on the DevKit as /workspace through NFS.
  • The mounted folder name defaults to /workspace and can be changed during SDK setup.

This setup provides a direct workflow for build artifacts:

  • Artifacts produced in the SDK are immediately visible on the DevKit without a separate deploy step.
  • Agents can access logs, outputs, traces, and other interim files generated while the app runs on the DevKit.
  • Developers and agents can inspect the same files from one workspace context.

With Insight, you can view the workspace from a web browser. Some SiMa.ai specific model archives, such as *.tar.gz model artifacts, are automatically optimized for easier inspection.

Next Step​

Continue to Run on the DevKit.