Update with sima-cli
Use sima-cli update when the DevKit is running and reachable over the network. This method downloads the firmware image and triggers the update on the DevKit.
sima-cli update installs official SiMa.ai builds only. If you built your own image, see Flash an Image to eMMC instead.
DevKits running 2.x firmware cannot use this update mechanism to move directly to 3.0. Follow Convert from 2.1.3 to 3.0.0 once. After conversion, use sima-cli update to update from eLxr 3.0 to a newer release.
Before you continue, confirm that the host can reach the DevKit over the network. See:
- From DevKit
- From Host Machine
- Download only
Run sima-cli directly on the standalone DevKit. Make sure the DevKit has an active Internet connection, then run:
modalix:~$ sima-cli update
On MLSoC running Yocto Linux and on Modalix running eLxr 3.0 or later, you may also specify a full URL instead of a version string if you have downloaded and hosted the image yourself. This includes updating from eLxr 3.0 to a newer release.
modalix:~$ sima-cli update http://your-server/image.tar.gz
Host-initiated updates are supported on MLSoC running Yocto Linux and on Modalix running eLxr 3.0 or later, including updates from 3.0 to a newer release. For Modalix running eLxr 2.x, perform the update directly on the DevKit; moving to 3.0 requires the conversion guide linked above.
Use this command from the host machine:
sima-user@sima-user-machine:~$ sima-cli update --ip {ip_address_of_the_devkit}
This command also installs the appropriate Linux driver version on the host, if applicable.
If you have downloaded the firmware and hosted it on your network, provide the URL to avoid repeated Internet downloads.
sima-user@sima-user-machine:~$ sima-cli update --ip {ip_address_of_the_devkit} http://your-server/image.tar.gz
To download only the firmware image for manual update steps, run sima-cli download with the URL of the appropriate Modalix firmware archive.
To downgrade the DevKit or install a build that is not the latest release (e.g. a pre-release develop build or an internal engineering image), use Net Boot Recovery instead. It boots the DevKit from a TFTP server on the host and flashes the target image directly to eMMC.