Torizon is a new Linux-based software platform that simplifies the process of developing and maintaining embedded software. It allows you to configure the system for your use case quickly and easily, so you can focus on application development instead of Linux builds.
Torizon fully supports the following modules, which use eMMC as flash storage:
Raw NAND-based modules are currently supported only by experimental releases and they may not be supported in the stable versions of TorizonCore:
Browse for Torizon resources from the tabs below.
Torizon is installed via the Toradex Easy Installer. The latest builds can be obtained by enabling the Toradex Continous Integration Server feed in the Toradex Easy Installer Feeds dialog. We currently have three types of images:
Upon booting one can login using the following users:
root
torizon
Follow our Step-by-step Getting Started Guide for fully supported modules as an overview step to get you set up in no time.
After you have completed it, check the other tabs from the current article, where you can find a list of Torizon features as well as a list of related articles from our knowledge-base.
The base image for Torizon is a minimal image that provides OTA and containers capabilities out-of-the-box. This tab presents an overview of Torizon's features and points you towards broader documentation.
Docker containers are the base in which Torizon relies for application development. You are able to run any image built for your respective module's architecture. Along with TorizonCore we provide a default container as a sort of friendly starting environment:
TorizonCore is built with OSTree, a shared library and suite of command line tools that combines a "git-like" model for committing and downloading bootable filesystem trees, along with a layer for deploying them and managing the bootloader configuration. In short, this image has the foundation for OTA (over-the-air) update capabilities:
The traditional device tree process is laborious. Torizon uses device tree overlays hoping to somewhat streamline this process. With overlays, you just create a small snippet containing the hardware changes you need.
Toradex provides a public release roadmap for the TorizonCore platform:
An overview of relevant articles from our knowledge base is presented in this tab.
| Article | Brief Description |
|---|---|
| Debian Container for Torizon | Toradex provides a default container as a friendly starting environment |
| Device Tree Overlays | How to modify the device tree without having to re-compile it |
| Install Debian Packages on Target | How to start a container, install packages and modify the container for custom application startup |
| Speed up Build of Debian Based Images for Torizon | Use your computer as a proxy for Debian feeds when doing a Docker build, saving a lot of time |
| Article | Brief Description |
|---|---|
| Torizon Update System | An overview and a practical demonstration of OSTree, which is the foundation for over-the-air updates |
| Create OSTree Union | How to modify files inside OSTree |
| Article | Brief Description |
|---|---|
| Build TorizonCore | How to build the Yocto-based Torizon base-image |
The full-featured image is rather large taking up most of the space on the raw NAND-based modules. As such it is not recommended to experiment with containers on these devices since there isn't much space for containers as is. In the future, we hope to slim down the footprint. Alternatively, the Balena based image is slimmer by about ~70MB.
In our i.MX6-based Debian containers we are using the Armada X.org DDX driver which seems to have worked fine in our tests but, it might show stability issues.
The error is probably related to missing session management inside the container.
Make sure to clear the U-Boot environment by using env default -a && env save.
