Search by Tags




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:

  • Apalis iMX6
  • Colibri iMX7 1GB
  • Colibri iMX6

Raw NAND-based modules are currently supported only by experimental releases and they may not be supported in the stable versions of TorizonCore:

  • Colibri iMX7 256MB/512MB
  • Colibri iMX6ULL


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:

  • torizon-core-docker: A full-featured image containing Docker and OTA. All other instructions on this page require this image.
  • torizon-core-balena: Similar to the above but with Balena instead of Docker for a smaller footprint. Currently, this image is in evaluation and might be dropped in the future.
  • torizon-core-lite: A minimal image only containing OTA. Can serve as a base for customers building custom images using OpenEmbedded and planing to leverage TorizonCore update system.

Upon booting one can login using the following users:

  • root

    • Login: root
    • Password: (none)
    • Only active on serial console!
  • torizon

    • Login: torizon
    • Password: torizon
    • Available on SSH and serial console.

How to Start

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.

Additional Resources

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:

Device Tree Overlays

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.

Additional Information

  • The full image is quite minimal featuring basic command line utilities.
  • The kernel itself is following mainline.
  • There is no package management in the base system.
  • Docker containers can be used to acquire other features.
  • The minimal image is even more bare-bones containing just the bare minimum to support OTA+.

TorizonCore Release Details and Roadmap

Toradex provides a public release roadmap for the TorizonCore platform:

  • Image Space limitation

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.

  • Xorg video driver

In our i.MX6-based Debian containers we are using the Armada DDX driver which seems to have worked fine in our tests but, it might show stability issues.

  • Error "No session for pid" on container startup

The error is probably related to missing session management inside the container.

  • Image not booting properly

Make sure to clear the U-Boot environment by using env default -a && env save.