TorizonCore is our operating system that powers Torizon, a DevOps platform that simplifies the development and maintenance of embedded Linux software. TorizonCore is designed to be used out-of-the-box on devices requiring high reliability, allowing you to focus on your application instead of on building and maintaining an operating system.
Torizon uses software containers, making it simple to add functionality to your system in a way that is both secure and easy to maintain. Torizon supports hardware acceleration in containers and graphical user interfaces.
This release includes all updates from the previous 6.x.y TorizonCore releases.
- Easier network configuration: The ethtool utility was included in TorizonCore and does not need to be added inside containers.
- Support for new features: Remote Access Client (RAC) is integrated and disabled by default, supporting the upcoming Remote Access feature on Torizon Platform Services.
- Device drivers included as a module:
- Enable support for the Microchip KSZ8795/KSZ88X3 switch chips on TorizonCore 6 (upstream kernel)
- Enable support for the SPI/SDIO to Wi-Fi Module Microchip ATWILC1000
- Enable support for the Analog Devices AD7606 ADC
- Enable MAC80211 (Wi-Fi) mesh networking support
- Enable ISO 15765-2:2016 CAN Transport Protocol (CAN ISOTP) support
- Several bug fixes:
- Wi-Fi Access Point does not work in TorizonCore 6
- Offline updates don’t work on container images with symlinks in their layer metadata
- Aktualizr doesn’t send an installation report when it fails to validate metadata
- OS rollbacks failure
- Updates from BSP 6.3.0:
- Please also note that TorizonCore is built on top of the Toradex BSP Layers for the Yocto Project. Read the BSP Layers and Reference Images for Yocto Project release news to learn more.
- The torizon-containers repository has been released. It contains all containers from debian-docker-images, debian-package-devel, debian-cross-toolchain, debian-development-images, and rt-validation, whose repositories will stop being used for newer releases. The containers published on Docker Hub remain the same
- Debian Bookworm:
- Containers rebuilt and published to Docker Hub: chromium and cog. This concludes the containers release, apart from occasional bug fixes
- Samples were upgraded to Bookworm
- All containers were rebuilt against the latest Debian feed
- Developer documentation updated
- Package updates:
- Packages were rebuilt based on the NXP 5.15 BSP: chromium. This concludes the package migration, apart from occasional bug fixes.
- XWayland and gst-plugins-base1.0 were rebuilt with GLX support removed. Instead, Glamor support for 2D acceleration is present. Due to a bug with Glamor, though, it is currently falling back to software rendering until a fix is implemented in the NXP upstream project.
- Important bug fix: CROSS_COMPILE_ARG is not being passed on 64-bit Torizon SDK containers, leading to cross-compilation errors
The TorizonCore 6.3.0 Quarterly Release is a production-grade release. Therefore, if you are in production with TorizonCore 5 or earlier TorizonCore 6 releases, and you are not affected by the TOR-3143 known issue, we recommend moving to this quarterly release.
While the previous quarterly releases were already production-grade, limitations on the tooling and ecosystem were still present. This release provides complete tooling and ecosystem support.
Debian Containers for Torizon
All Debian Bookworm containers were published on Docker Hub with the major tag “3“ and validated by our automated and manual tests. Documentation has been updated, and the environment variables for container tags on TorizonCore were bumped to “3“.
VS Code IDE Extension
Support for TorizonCore 6 has been added to the IDE Extension 2 since the past quarterly release 6.2.0. Throughout the quarter, several bug fixes and improvements were made.
Support for TorizonCore Builder (TCB) on TorizonCore 6 is concluded since the past quarterly release 6.2.0. Make sure you are using TorizonCore Builder 3.7.0 or newer.
Remote and Offline Updates
Upgrade from TorizonCore 5 to TorizonCore 6 using the Torizon updates - either remote or offline - is possible since TorizonCore 6.2.0.
To upgrade to TorizonCore 6, all users will need to first upgrade to the patch release 5.7.2 . The workflow will look as follows:
- TorizonCore 5.7.0 or older → TorizonCore 5.7.x patch release → Bootloader upgrade → Latest TorizonCore 6 release
- Support for Verdin AM62 is expected in the next releases
- Secure Boot: A new Yocto class for building images with secure boot enabled was introduced. It is possible to do a Yocto build of TorizonCore with partial secure boot chain of trust. Complete support is expected in the next releases.
- There is a bug affecting GUI on iMX8 Devices. The bug fix is expected in the next releases.
Get more updates on this from our Release Details.
A quarterly release is a production release, intended to be used in a production environment only with volume products, as long as they are supported by TorizonCore. We run a set of tests to validate them. Learn more about our release types from our Embedded Linux Support Strategy.
- Volume products: Apalis iMX6, Apalis iMX8, Colibri iMX6ULL 1GB, Colibri iMX6DL, and Colibri iMX7D 1GB
This release is intended to be used in production on these modules.
- Sample products:Colibri iMX8X, and Verdin iMX8M Mini, and Verdin iMX8M Plus
Due to the hardware status being “sample”, this release is intended for development.
For Verdin, only the second generation of Verdin products is supported.