Introduction
Understand UltraEdge HPC-I architecture for edge AI and mixed workloads
Provision a Google Axion C4A VM for Yocto image builds on Arm
Build and install Yocto images for NXP S32G-VNP-GLDBOX3 with UltraEdge
Install UltraEdge on Debian and Ubuntu for Edge AI workloads
Run and manage UltraEdge HPC-I for AI and mixed workloads on Arm
Next Steps
In this section, you’ll use the Tinkerblox CLI to deploy, manage, and monitor microservices on the UltraEdge platform. You’ll practise inspecting system state, installing a sample microservice, and observing its runtime behavior.
To get started, download a sample MPAC file from the Tinkerblox support repository and install it on your device.
The Tinkerblox Command Line Interface (CLI) lets you manage the Edge Agent and microservices on UltraEdge devices.
Basic usage:
tinkerblox-cli [OPTIONS] <COMMAND>
Common commands:
status: Show connection status with the Edge Agentmicroboost: Microservice management commandshelp: Print this message or the help for a given subcommandOptions:
-h, --help: Print help-V, --version: Print versionTo verify that the CLI is connected to the Edge Agent, run:
sudo tinkerblox-cli status
The output shows whether the CLI is connected to the Edge Agent.
You can install, list, start, stop, and uninstall microservices using the microboost command. Replace /path/to/your.mpac with the path to your MPAC file and <id> with the microservice ID.
Install a microservice:
sudo tinkerblox-cli microboost install -f /path/to/your.mpac
List installed microservices:
sudo tinkerblox-cli microboost list
Show microservice status:
sudo tinkerblox-cli microboost status <id>
Stop a microservice:
sudo tinkerblox-cli microboost stop <id>
Start a microservice:
sudo tinkerblox-cli microboost start <id>
Uninstall a microservice:
sudo tinkerblox-cli microboost uninstall <id>
Use the diagnostics command to check system health and connectivity on your UltraEdge device.
Syntax:
sudo tinkerblox-cli diagnostics <command>
Available diagnostics:
sudo tinkerblox-cli diagnostics full
sudo tinkerblox-cli diagnostics system
sudo tinkerblox-cli diagnostics network
sudo tinkerblox-cli diagnostics filesystem
sudo tinkerblox-cli diagnostics engine
If you encounter errors while running CLI commands or deploying microservices, use the following guidance to resolve them:
Permission denied
sudo privileges.Directory creation failed
Cross-architecture build issues Cross-architecture issues usually occur when binaries are built for a different CPU architecture than your host system. These are not related to Yocto build issues.
bash qemu-aarch64-static --versionbash ls /proc/sys/fs/binfmt_misc/In this section, you:
Next, explore more advanced CLI features, automate deployments, or integrate with additional monitoring and orchestration tools for your edge environment.