|6.3.0 quarterly release|
| TOR-1748||New Feature||As a developer, I want a class in OE for signed images, so I can build images with secure boot support||Apalis iMX6, Apalis iMX8, Apalis iMX8X, Colibri iMX6, Colibri iMX7, Colibri iMX8X, Verdin iMX8M Mini, Verdin iMX8M Plus||Open Embedded|
Description: To make it possible for you to build a TorizonCore image with Secure Boot enabled, a new Yocto Project/OE class named "torizon-signed" is being introduced. You must include it into your TorizonCore custom image to enable secure boot. A how-to guide will be released with more instructions.
|6.3.0-devel-202305 monthly release|
| TOR-2975||New Feature||Enable support for the Microchip KSZ8795/KSZ88X3 switch chips on TorizonCore 6 (upstream kernel)||Apalis iMX6, Colibri iMX6, Colibri iMX6ULL, Colibri iMX7||Kernel|
Description: Enable the Microchip KSZ8795/KSZ88X3 switch IC device driver as a module on TorizonCore 6, for the upstream kernel.
|6.2.0 quarterly release|
| TOR-2452||Fixed||Increased boot time by approximately 2x on TC 6 when compared to TC 5 on SoMs that use an upstream kernel||Apalis iMX6, Colibri iMX6||Open Embedded||Low|
Description: The boot time on TorizonCore 6 for 32-bit devices has increased by approximately 2x.
Update: the root cause of the increased boot time seems to be that our Embedded Linux BSP 6 is using 2x CPU when compared with BSP 5.
Update 2: the BSP performance has been fixed. Despite that, TorizonCore first boot time seems to be greater on TorizonCore 6 than 5, so we continue to investigate it.
|6.1.0 quarterly release. Learn more on https://www.toradex.com/news/torizon-core-release-6-1-0-quarterly-release|
| TOR-2746||Fixed||Missing /dev/colibri-spi-cs0 symlink||Colibri iMX6, Colibri iMX6ULL, Colibri iMX7||Open Embedded||Low|
Description: The Colibri Evaluation Board uses the SPI interface for an SPI-to-CAN controller, however, we do enable the spidev (a userspace SPI API) on the same SPI interface and CS with an overlay that is currently enabled by default. This leads to a conflict.
Starting from BSP 6.1.0, the overlay that enables spidev on the given SPI interface is not loaded by default. Our test infrastructure caught this change as a possible issue due to a missing symlink to "/dev/colibri-spi-cs0". In fact, this was the intended behavior after the change.
As a customer, if you want to use such an interface with spidev, you must disable the CAN and enable the spidev overlay. For more details on CAN and SPI in our BSP, refer to the CAN (Linux) and the SPI (Linux) articles. To manage device tree and overlays on TorizonCore, we recommend the articles Device Tree Overlays on Torizon and TorizonCore Builder Tool - Customizing TorizonCore Images.
|6.0.0-devel-202210 monthly pre-release. Learn more on https://www.toradex.com/news/torizon-core-release-6-0-0-devel-202210-release-monthly|
| TOR-2451||Fixed||LAVA test "hw-links-buses" fails due to possibly missing SPI symlink||Colibri iMX6, Apalis iMX6||Open Embedded||Low|
Description: On automated tests for our monthly pre-release, some symlinks to devices were missing. The missing ones are "/dev/colibri-spi-cs0" and "/dev/apalis-spi1-cs0", and they prevent the test from running through and checking other symlinks.
Update: this was fixed on the BSP level, nothing was required or done on TorizonCore.
Workaround: Test it on a nightly that has been released after the 6.0.0-devel-202209 monthly. Alternatively, if you plan to use the monthly, then access the given device directly, not though the symlink.
|5.7.0 LTS release. Learn more on https://www.toradex.com/news/torizon-core-release-5-7-0-quarterly-release|
| TOR-2397||Fixed||Chromium container fails to start in the evaluation containers on modules with GPU||Verdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX6, Apalis iMX8, Apalis iMX6||Debian Base Containers||Low|
Description: The Chromium and Cog containers were split, and HW acceleration on the GPU (rendering) enabled on Chromium. These changes have broken the startup of Portainer in our "TorizonCore with Evaluation Containers" image.
|5.6.0-devel-202203 monthly pre-release|
| TOR-2167||New Feature||As a developer, I want to review the NXP license added to TorizonCore without evaluation containers||Verdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX6, Apalis iMX8, Apalis iMX6||Open Embedded|
Description: TorizonCore releases come in two “flavors”: with and without evaluation containers. We add the NXP license to the Toradex Easy Installer image without evaluation containers, but we don’t use it. In other words, when installing TorizonCore, users are not prompted to accept the license.
In this task, we will evaluate if the license is being deployed as a mistake, or if we should enable prompting users to accept NXP’s EULA.
Update: we came to the conclusion that, even for images without evaluation containers, some of them are shipped with components that are subject to NXP's EULA. Therefore, the license will also show up on those images, on a case-by-case basis mostly dependent on the SoC that equips a given SoM.
|5.5.0-devel-202112 monthly release|
| TOR-1638||New Feature||As a user, I want an easier way to configure video output and resolution, so I don't spend much time doing this manually||Verdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX8, Apalis iMX6, Apalis iMX8X||Debian Base Containers|
Description: A section dedicated to this has been added to the article Working with Weston on TorizonCore, together with comments on our weston.ini files on our Weston Debian Docker image. In summary, it points to the official weston-drm documentation.
|5.3.0 Quarterly Release. Learn more on https://www.toradex.com/news/torizon-core-release-5-3-0-quarterly-release|
| TOR-1937||Fixed||Chromium fails with out-of-memory errors on Colibri iMX6||Colibri iMX6||Debian Base Containers||Low|
Description: The kiosk-mode-browser container is not running on a fresh installation of TorizonCore 5.3.0 on Colibri iMX6. After launching the container and waiting for some time, the Linux kernel starts killing the "chromium" processes.
|5.2.0-devel-202104 Monthly Release. Learn more on https://www.toradex.com/news/torizon-core-release-5-2-0-release-monthly|
| TOR-1721||New Feature||Build kmscube and glmark2 for 32 bits architectures||Colibri iMX6, Apalis iMX6||Debian Packages|
Description: Provide kmscube and glmark2 packages for 32 bits architectures in Toradex Debian feed.
|5.2.0-devel-202103 Monthly Release|
| TOR-1720||Fixed||TorizonCore will reboot indefinitely if the docker service fails||Verdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX8, Apalis iMX6, Apalis iMX8X||Open Embedded||Low|
Description: TorizonCore reboots indefinitely if the docker service fails. This should only happen if the system is executing an update.
| TOR-1687||New Feature||Add image metadata to /etc/os-release||Verdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX8, Apalis iMX6, Apalis iMX8X||Open Embedded|
Description: Add image type information (Docker, Podman) to /etc/os-release.
| TOR-1667||New Feature||Update Docker and Podman to the latest versions||Verdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX8, Apalis iMX6, Apalis iMX8X||Open Embedded|
Description: Update Docker from 19.03.12-ce to 19.03.14-ce and Podman to 2.2.1.
| TOR-1664||New Feature||Bump Portainer container to version 2.1.1||Verdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX8, Apalis iMX6, Apalis iMX8X||Debian Base Containers|
Description: Bump Portainer container version from 2.0.0 to 2.1.1.
| TOR-1636||New Feature||As a user, I want to remotely access TorizonCore UI, so I can access graphical applications without a display||Verdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX7, Colibri iMX6, Apalis iMX8, Apalis iMX6, Apalis iMX8X||Debian Base Containers|
Description: Add VNC and RDP support in the Weston container.
|5.2.0-devel-202102 Monthly Release|
| TOR-1627||New Feature||As a user, I want recipes in meta-toradex-torizon to be fetched from https instead of git, so it is more user-friendly||Verdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX8, Apalis iMX6, Apalis TK1, Apalis iMX8X||Open Embedded|
Description: In an approach to make it more user-friendly, especially for big company customers that do not allow git-protocol in their networks, we decided to use https as a fetching source in meta-toradex-torizon.
| TOR-1378||Fixed||Touchscreen issues with Weston and QtWidgets||Verdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX8, Apalis iMX6, Apalis iMX8X||Debian Base Containers||Low|
Description: It seems like QApplication which is used for Widgets does not support automatic translation of touch events to mouse events. That leads to touchscreen not working with QTWidgets applications.
|5.1.0-devel-202012 Monthly Release. Learn more on https://www.toradex.com/news/torizon-core-prerelease-5-1-0-devel-202012|
| TOR-2139||Fixed||TorizonCore Builder dt checkout fails||Colibri iMX6||Open Embedded||Low|
Description: When using the latest TorizonCore nightly and then do a torizoncore-builder dt checkout we get the following error: "Branch name does not exist in upstream repository".
|5.1.0-devel-202011 Monthly Release. Learn more on https://www.toradex.com/news/torizon-core-prerelease-5-1-0-devel-202011|
| TOR-1506||Fixed||CONFIG_IGB is not enabled in mainline-based modules||Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX6||Kernel||Low|
Description: CONFIG_IGB is not enabled in mainline-based modules.
|5.0.0-devel-202010 Monthly Release. Learn more on https://www.toradex.com/news/torizon-core-prerelease-5-0-0-devel-202010|
| TOR-1361||Fixed||Issue with Aster bottom USB using TorizonCore||Colibri iMX6||Device Trees, Kernel||Low|
Description: The Aster bottom USB isn't working on the TorizonCore image on Colibri iMX6.
|4.0.0-devel-202004 Monthly Release|
| TOR-806||New Feature||NXP PCF85363 RTC support||Colibri iMX7, Colibri iMX6, Apalis iMX6||Kernel|
Description: Add support for NXP PCF85363 RTC
| TOR-410||New Feature||Tool to manage device tree overlays in the device||Colibri iMX8X, Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX8, Apalis iMX6, Apalis iMX8X|
Description: Create a tool to manage device tree overlays on device
| TOR-374||New Feature||Add support to reboot module after update||Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX6|
Description: Creating a file under /run/aktualizr-session/need_reboot will trigger automatic reboot.
| TOR-367||Fixed||Docker Compose does not work with Balena||Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX6||Low|
Description: Images running Balena do not support using docker-compose
| TOR-346||New Feature||Support OSTREE for different torizon versions||Colibri iMX8X, Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX8, Apalis iMX6, Apalis iMX8X||Low|
Description: OSTREE references have been updated. Check here for the current OSTREE feeds: https://developer.toradex.com/knowledge-base/torizon-update-system#OSTree_Update_From_Toradex_Feeds
| TOR-304||New Feature||Use udev to provide Toradex standardized access to devices||Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX6|
Description: TorizonCore provides system links to all standard Toradex interfaces (e.g. /dev/ttycolibri0-3, /dev/i2c-colibri)
| TOR-300||New Feature||Kernel per-process IO accounting support||Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX6|
Description: Enable kernel per-process IO accounting.
| TOR-266||New Feature||Real-time TorizonCore image||Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX6|
Description: Real time images are available on Toradex Easy installer CI feed.
| TOR-56||Fixed||Docker --init does not work||Colibri iMX8X, Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX8, Apalis iMX6, Apalis iMX8X||Low|
Description: The Docker init binary seems to be missing in the root file system
Workaround: Do not use --init, consider using an alternative like tiny-init.
| TOR-319||Known Issue||Colibri iMX6S gets very slow with Docker||Colibri iMX6||Open Embedded||Low|
Description: Limited amount of memory on iMX6S prevents the system from running fast.
Update: Colibri iMX6S is not supported by TorizonCore anymore, since the low RAM leads to a poor user experience and limited use cases.