v2.1.17

SiMa CLI 2.1.17 simplifies DevKit recovery, makes SDK setup more flexible, and previews the system update experience coming with eLxr 3.0.

✨ Release highlights

• Recover with fewer manual steps: prepare a reachable DevKit for netboot directly from the CLI.
• Set up from downloaded bundles: install the Neat SDK and Model Compiler with fewer repeat downloads.
• Keep browser VS Code compatible: SDK setup selects a compatible Codex extension version.
• Choose your SDK tools: select extensions and opt into Edgematic Studio.
• Preview the next update workflow: explore eLxr 3.0 recovery and A/B system updates.

---

🔄 Easier DevKit recovery

Prepare a reachable DevKit for network boot directly from SiMa CLI. The CLI configures the boot settings and reboots the device for recovery—no manual U-Boot menu changes required.

Your preferred workflow	What to expect
CLI-assisted netboot	Select a reachable DevKit and let the CLI prepare its network-boot settings.
Automatic flashing	Add --autoflash to flash the selected device after its network boot has been verified.
Manual netboot	Continue configuring network boot through the U-Boot console, as before.

Example: netboot and automatically flash a Modalix DevKit

Run this command on your host computer, replacing 192.168.1.20 with your DevKit's IP address and 2.1.3 with the firmware version you want to install:

sima-cli bootimg -v 2.1.3 \
  --netboot --devkit 192.168.1.20 --autoflash

Modalix and eLxr are the defaults, so no board or firmware-type options are needed.

Review and confirm the selected device when prompted. The CLI prepares network boot, reboots the DevKit, and automatically flashes its internal eMMC storage after verifying that the selected device is running the network boot image. Keep the host computer and CLI session running until recovery finishes.

Warning

Recovery flashing overwrites the DevKit's internal eMMC storage. Back up any data you need before proceeding. This is a recovery operation, not the data-preserving A/B update described below.

Note

Automatic preparation requires the DevKit to be accessible over SSH. If it cannot boot far enough to accept an SSH connection, use the U-Boot console for manual preparation.

🧪 Preview: eLxr 3.0 recovery and system updates

Important

eLxr 3.0 is not yet available to customers. These capabilities are a preview for pre-release testing, not a generally available upgrade path.

This release previews netboot recovery, full-system updates, and system-slot inspection for compatible eLxr 3.0 devices.

What changes from eLxr 2.1.x?

	eLxr 2.1.x	eLxr 3.0 — preview
How device software is updated	APT updates individual packages on the installed system.	SWUpdate installs a complete system image into a second system slot.
Where the update is installed	The existing system is updated in place.	The inactive slot is updated while the current slot remains in place.
How the new system starts	Follows the package-based update workflow.	Reboot after installation to start the updated system.
Fallback	Does not use the new A/B system-slot workflow.	The previous system slot provides a fallback if the new system cannot boot successfully.

A/B means two system slots: one runs the current system, while the other receives the update. On appropriately provisioned devices, the update preserves persistent data. You can inspect slot versions and update status before deciding when to reboot.

This changes the device system update workflow; it does not remove APT from the operating system.

Note

Full-system updates require the 3.0 A/B system layout. Devices using an older layout require recovery or provisioning first.

📦 Install from offline bundles

Set up your tools using downloaded bundles that include the Neat SDK and Model Compiler. This reduces repeated downloads and helps you prepare development environments where internet access is limited.

During SDK setup, SiMa CLI detects a compatible local Model Compiler package and offers three choices:

• Install locally from the downloaded package.
• Install online by downloading a package.
• Skip Model Compiler installation.

Note

System and Python prerequisites may still require internet access.

🛠️ A more flexible SDK environment

Compatible Codex extension

SDK setup now pins the Codex VS Code extension to a compatible version. The latest extension version is incompatible with the SDK's VS Code server; selecting a compatible version helps prevent extension startup problems.

Choose the tools you need

Select the Neat, Codex, and Claude browser VS Code extensions during setup. Edgematic Studio is optional—add --edgematic-studio when you want to install it.

---

⚙️ For automated installations

Review these options when updating your SDK setup scripts:

Option	Behavior
--noninteractive	Installs a compatible local Model Compiler package if available; otherwise skips Model Compiler.
--noninteractive -y	Allows online Model Compiler installation when no compatible local package is available.
--all-extensions	Selects all three browser VS Code extensions: Neat, Codex, and Claude.
--edgematic-studio	Adds Edgematic Studio as a separate opt-in.

Explicit compiler skip options still take priority.