Search by Tags

Torizon OS Issue Tracker

 

The following table contains known issues, scheduled bug fixes, and feature improvements for the Torizon OS images. The tickets are split into two major states:

  • Submitted (open): new features and bug fixes for Torizon OS versions that have not yet been released. They may be scheduled for a specific release version; not planned; or in our backlog. All of them have one of the following states:
    • Known Issue: a bug or unexpected behavior that has been reported and pending a fix. Once fixed, the status will transition to Fixed.
    • Feature Request: a new feature that may be added to a future release. Once released, the status will transition to New Feature.
  • Released (closed): new features and bug fixes for BSP versions that have already been released. All of them have one of the following states:
    • Fixed: a bug that has been fixed and released.
    • New Feature: something that didn't exist before and was added to a news release.

Any schedules are not guaranteed but reflect the current planning. The planning could be shifted due to priority changes.
Issues that are scheduled for a specific version will be integrated into the mentioned version of the BSP.

We will update this table continuously in order to always provide the latest state of our development plan.

Please see also the Toradex Embedded Linux Support Strategy to learn more about the different releases.

How to obtain the Torizon OS Images

Using the Toradex Easy Installer application in a Toradex SoM connected to the internet is the easiest and fastest way to install the latest version of Torizon OS into the device. Toradex also offers offline installers.

Clear Filter
Issue #StatusSubjectModuleComponentsSeverity

6.6.0-devel-202402 (Release date: 2024-02-01)
6.6.0-devel-202402 monthly pre-release
TOR-3312FixedU-Boot failing with error "collect2: error: ld returned 1 exit status" during linking step on Secure Boot images on Verdin iMX8M MiniVerdin iMX8M MiniSecure Boot, U-BootLow

Description: U-Boot fails with the error "collect2: error: ld returned 1 exit status" when building a signed Torizon OS image for Verdin iMX8M Mini.

Update: this is fixed, use Torizon OS 6.6.0-devel-202402 or newer.

6.4.0-devel-202309 (Release date: 2023-09-11)
6.4.0-devel-202309 monthly pre-release
TOR-3065New FeatureAs a developer, I want to investigate what is missing related to VPU-enabled GStreamer support in TorizonCore for SoMs that use the Hantro VPU in BookwormVerdin iMX8M Mini, Verdin iMX8M PlusDebian Base Containers, Debian Packages

Description: TorizonCore lacks some Debian packages that would allow you to use VPU-enabled GStreamer pipelines for Verdin iMX8M Mini and Verdin iMX8M Plus, that use the Hantro VPU. In this task, we investigate which NXP packages we miss and list what Debian packages must be created by Toradex to support it.

Note that Apalis/Colibri iMX6 already have upstream support for VPU acceleration, and Apalis iMX8, Apalis iMX8X and Colibri iMX8X are also supported downstream, the latter with instructions provided on How to use GStreamer on TorizonCore.

Workaround: While it isn't a trivial thing to do, you could start from our instructions for i.MX 8 and add/build the missing NXP packages directly in a Dockerfile.

TOR-2744FixedSplash screen not appearing on Verdin iMX8M Mini and iMX8M PlusVerdin iMX8M Mini, Verdin iMX8M PlusOpen EmbeddedLow

Description: On TorizonCore 6, the splash screen is not being displayed on Verdin iMX8M Mini and Verdin iMX8M Plus.

6.4.0-devel-202308 (Release date: 2023-08-08)
6.4.0-devel-202308 monthly pre-release
TOR-3143FixediMX8 devices sometimes fail to start a GUI on boot with the error "Could not make device fd drm master: Permission denied"Apalis iMX8, Colibri iMX8X, Verdin iMX8M Mini, Verdin iMX8M PlusDebian PackagesCritical

Description: When the device boots or reboots, sometimes the GUI is not brought up, and when inspecting the Weston container logs, the error "seatd returns 00:00:00.140 [ERROR] [seatd/seat.c:281] Could not make device fd drm master: Permission denied" is present.

Update: this is fixed on the Debian Containers for Torizon, and all TorizonCore 6 releases, including the 6.3.0, are not affected anymore by this bug. You must just use the "weston" or the ""touch-calibrator" Debian Containers for Torizon with version 3.1.1 or newer. Learn more about container tags and TorizonCore on TorizonCore Containers Tags and Versioning.

Workaround: Use the command "sudo systemctl edit --full docker-compose.service" and change the line with the "After" key from "After=docker.service" to "After=docker.service plymouth-quit.service".

This will increase the time to start the graphical application by a few seconds.

Update: the public workaround is not required anymore.You must just use the "weston" or the ""touch-calibrator" Debian Containers for Torizon with version 3.1.1 or newer. Learn more about container tags and TorizonCore on TorizonCore Containers Tags and Versioning.

6.3.0 (Release date: 2023-07-25)
6.3.0 quarterly release
TOR-1748New FeatureAs a developer, I want a class in OE for signed images, so I can build images with secure boot supportApalis iMX6, Apalis iMX8, Apalis iMX8X, Colibri iMX6, Colibri iMX7, Colibri iMX8X, Verdin iMX8M Mini, Verdin iMX8M PlusOpen 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-202306 (Release date: 2023-06-07)
6.3.0-devel-202306 monthly release
TOR-3024New FeaturePackage Xwayland without GLX support on i.MX8-based SoMsApalis iMX8, Colibri iMX8X, Verdin iMX8M Mini, Verdin iMX8M PlusDebian Packages

Description: NXP GPUs doesn't seem to support GLX, therefore this has been disabled in meta-freescale, as xwayland: Drop GLX for i.MX GPU. This broke Xwayland on the Debian Container for Torizon.

Workaround: Update to the latest version of the Debian Containers for Torizon. At the moment, only software support is provided. 2D graphics acceleration will be added as soon as Xwayland falls back to software rendering due to broken Glamor support on i.MX8-based SoMs is concluded.

6.2.0 (Release date: 2023-04-19)
6.2.0 quarterly release
TOR-2929New FeatureEnable support for the Microchip KSZ8795/KSZ88X3 switch chips on TorizonCore 6 (NXP downstream kernel)Apalis iMX8, Colibri iMX8X, Verdin iMX8M Mini, Verdin iMX8M PlusKernel

Description: Enable the Microchip KSZ8795/KSZ88X3 switch IC device driver as a module on TorizonCore 6, for the NXP downstream kernel.

6.1.0 (Release date: 2023-01-16)
6.1.0 quarterly release. Learn more on https://www.toradex.com/news/torizon-core-release-6-1-0-quarterly-release
TOR-2492FixedSplash screen not showing up on i.MX 8 SoMs in TorizonCore 6Verdin iMX8M Mini, Verdin iMX8M PlusOpen EmbeddedLow

Description: On TorizonCore 6, the splash screen is not being displayed on SoMs that use the downstream-based NXP BSP.

6.0.0-devel-202210 (Release date: 2022-10-11)
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-2476FixedCan't run touch calibration on Verdin iMX8MP with error "_OpenDevice(1249): FATAL: Failed to open device, errno=No such file or directory."Verdin iMX8M Mini, Verdin iMX8M PlusDebian Base ContainersLow

Description: The touch calibrator container does not run successfully, with the following error: "_OpenDevice(1249): FATAL: Failed to open device, errno=No such file or directory."
This happens due to the lack of Vivante drivers for SoMs based on the NXP downstream BSP.

TOR-2433FixedVerdin iMX8M Mini does not boot on nightly candidate to 6.0.0-devel-202209Verdin iMX8M MiniDevice TreesLow

Description: The Verdin iMX8M Mini boot hangs with a Device Tree-related error.

Workaround: Use the latest nightly builds of TorizonCore 6, where it has already been fixed.

5.7.0 (Release date: 2022-07-28)
5.7.0 LTS release. Learn more on https://www.toradex.com/news/torizon-core-release-5-7-0-quarterly-release
TOR-2397FixedChromium container fails to start in the evaluation containers on modules with GPUVerdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX6, Apalis iMX8, Apalis iMX6Debian Base ContainersLow

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 (Release date: 2022-03-09)
5.6.0-devel-202203 monthly pre-release
TOR-2167New FeatureAs a developer, I want to review the NXP license added to TorizonCore without evaluation containersVerdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX6, Apalis iMX8, Apalis iMX6Open 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.6.0-devel-202202 (Release date: 2022-02-01)
5.6.0-devel-202202 monthly pre-release
TOR-1931New FeatureAs a developer, I want to investigate what is missing related to VPU-enabled GStreamer support in TorizonCore for SoMs that use the Hantro VPUVerdin iMX8M Plus, Verdin iMX8M MiniDebian Base Containers, Debian Packages

Description: TorizonCore lacks some Debian packages that would allow you to use VPU-enabled GStreamer pipelines for Verdin iMX8M Mini and Verdin iMX8M Plus, that use the Hantro VPU. In this task, we investigate which NXP packages we miss and list what Debian packages must be created by Toradex to support it.

Note that Apalis/Colibri iMX6 already have upstream support for VPU acceleration, and Apalis iMX8, Apalis iMX8X and Colibri iMX8X are also supported downstream, the latter with instructions provided on How to use GStreamer on TorizonCore.

Workaround: While it isn't a trivial thing to do, you could start from our instructions for i.MX 8 and add/build the missing NXP packages directly in a Dockerfile.

5.5.0-devel-202112 (Release date: 2021-12-07)
5.5.0-devel-202112 monthly release
TOR-1638New FeatureAs a user, I want an easier way to configure video output and resolution, so I don't spend much time doing this manuallyVerdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX8, Apalis iMX6, Apalis iMX8XDebian 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.5.0-devel-202111 (Release date: 2021-11-05)
5.5.0-devel-202111 monthly release
TOR-2046New FeatureAs a user, I want to be able to use NXP GStreamer packages on iMX8Verdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Apalis iMX8, Apalis iMX8XDebian Packages

Description: The NXP fork of GStreamer provides some hardware-accelerated features that are not available in the upstream GStreamer project. Due to a mismatch between the version of NXP's fork compatible with our BSP, and the upstream package provided by Debian, we provide Debian packages for a fixed version of the NXP fork. Learn more about it on How to use GStreamer on TorizonCore.

5.3.0 (Release date: 2021-07-08)
5.3.0 Quarterly Release. Learn more on https://www.toradex.com/news/torizon-core-release-5-3-0-quarterly-release
TOR-1935FixedCannot update Verdin iMX8MM from TorizonCore 5.1.0 (quarterly) to TorizonCore 5.3.0 (nightly)Verdin iMX8M MiniOpen EmbeddedLow

Description: When updating Verdin iMX8MM from TorizonCore 5.1.0 (quarterly release ) to TorizonCore 5.3.0 (nightly build), the boot fails with a "device tree not found" error.

TOR-1909FixedQt5 with EGLFS/KMS backend not working on iMX8Verdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Apalis iMX8, Apalis iMX8XDebian Base ContainersLow

Description: On some modules, we cannot start the QT5 container using the EGLFS interface due to misconfigured DRI card interface.

5.3.0-devel-202106 (Release date: 2021-06-02)
5.3.0-devel-202106 Monthly Release
TOR-1820New FeatureUpdate Debian packages to NXP BSP L5.4.70_2.3.2Verdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Apalis iMX8, Apalis iMX8XDebian Base Containers, Debian Packages

Description: Update Debian packages to the latest NXP BSP release (L5.4.70_2.3.2).

5.3.0-devel-202105 (Release date: 2021-05-05)
5.3.0-devel-202105 Monthly Release
TOR-1696FixedThe imx-gpu-viv-demos package is not installingVerdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Apalis iMX8, Apalis iMX8XDebian Base ContainersLow

Description: The imx-gpu-viv-demos package installation is failing with dependencies issues.

5.2.0-devel-202103 (Release date: 2021-03-09)
5.2.0-devel-202103 Monthly Release
TOR-1720FixedTorizonCore will reboot indefinitely if the docker service failsVerdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX8, Apalis iMX6, Apalis iMX8XOpen EmbeddedLow

Description: TorizonCore reboots indefinitely if the docker service fails. This should only happen if the system is executing an update.

TOR-1687New FeatureAdd image metadata to /etc/os-releaseVerdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX8, Apalis iMX6, Apalis iMX8XOpen Embedded

Description: Add image type information (Docker, Podman) to /etc/os-release.

TOR-1667New FeatureUpdate Docker and Podman to the latest versionsVerdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX8, Apalis iMX6, Apalis iMX8XOpen Embedded

Description: Update Docker from 19.03.12-ce to 19.03.14-ce and Podman to 2.2.1.

TOR-1664New FeatureBump Portainer container to version 2.1.1Verdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX8, Apalis iMX6, Apalis iMX8XDebian Base Containers

Description: Bump Portainer container version from 2.0.0 to 2.1.1.

TOR-1655New FeatureBump opencv package to version 4.4.0Verdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Apalis iMX8, Apalis iMX8XDebian Packages

Description: OpenCV package updated to version 4.4.0

TOR-1636New FeatureAs a user, I want to remotely access TorizonCore UI, so I can access graphical applications without a displayVerdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX7, Colibri iMX6, Apalis iMX8, Apalis iMX6, Apalis iMX8XDebian Base Containers

Description: Add VNC and RDP support in the Weston container.

5.2.0-devel-202102 (Release date: 2021-02-01)
5.2.0-devel-202102 Monthly Release
TOR-1627New FeatureAs a user, I want recipes in meta-toradex-torizon to be fetched from https instead of git, so it is more user-friendlyVerdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX8, Apalis iMX6, Apalis TK1, Apalis iMX8XOpen 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-1378FixedTouchscreen issues with Weston and QtWidgetsVerdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Colibri iMX6ULL, Colibri iMX7, Colibri iMX6, Apalis iMX8, Apalis iMX6, Apalis iMX8XDebian Base ContainersLow

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 (Release date: 2021-01-06)
5.1.0 Quarterly Release. Learn more on https://www.toradex.com/news/torizon-core-release-5-1-0-production-release-quarterly
TOR-1615FixedDevice trees for Verdin missing in the device-trees repositoryVerdin iMX8M Plus, Verdin iMX8M MiniDevice TreesLow

Description: The device trees for Verdin are missing in the device-trees repository.

TOR-1097New FeatureUpdate kmscube package to match the NXP 5.4 based releaseVerdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Apalis iMX8, Apalis iMX8XDebian Packages

Description: Build and add kmscube package to our Debian package feed.

5.1.0-devel-202012 (Release date: 2020-12-04)
5.1.0-devel-202012 Monthly Release. Learn more on https://www.toradex.com/news/torizon-core-prerelease-5-1-0-devel-202012
TOR-1088New FeatureUpdate gstreamer-imx package to match the NXP 5.4 based releaseVerdin iMX8M Plus, Verdin iMX8M Mini, Colibri iMX8X, Apalis iMX8, Apalis iMX8XDebian Packages

Description: Update gstreamer-imx package to match the NXP 5.4 based release.

5.1.0-devel-202011 (Release date: 2020-11-06)
5.1.0-devel-202011 Monthly Release. Learn more on https://www.toradex.com/news/torizon-core-prerelease-5-1-0-devel-202011
TOR-1469FixedBoot hangs or module freezes after docker run on Torizon Core 5Verdin iMX8M MiniKernelLow

Description: Boot hangs or module freezes on Verdin iMX8MM after docker run on Torizon Core 5

TOR-1465FixedWiFi doesn't workVerdin iMX8M Mini, Colibri iMX8X, Apalis iMX8KernelLow

Description: WiFi doesn't work on iMX8 based modules

TOR-1352FixedVerdin HDMI output is not workingVerdin iMX8M Plus, Verdin iMX8M MiniKernelLow

Description: The DSI to HDMI adapter is not enabled in the device tree, so by default the HDMI output is not working on Verdin.

4.0.0-devel-202008 (Release date: 2020-08-11)
4.0.0-devel-202008 Monthly Release. Learn more on https://www.toradex.com/news/torizon-core-prerelease-4-0-0-devel-202008
TOR-1166FixedRemove extra hyphen on demo debian containerVerdin iMX8M Mini, Colibri iMX8X, Apalis iMX8XDebian Base ContainersLow

Description: Error in the comment about how to accept EULA required to run imx8 vivante graphic drivers.

TOR-1028New FeatureOpenCV packageVerdin iMX8M Mini, Colibri iMX8X, Apalis iMX8XDebian Base Containers, Debian Packages

Description: Provide the OpenCV package and improve the container with DLR support, a compact runtime for Machine Learning Models.

4.0.0-devel-202007 (Release date: 2020-07-03)
4.0.0-devel-202007 Monthly Release. Learn more on https://www.toradex.com/news/torizon-core-prerelease-4-0-0-devel-202007
TOR-1034FixedError installing qt5-default: trying to overwrite '/usr/lib/aarch64-linux-gnu/libGL.so.1', which is also in package libgl1:arm64 1.1.0-1Verdin iMX8M Mini, Colibri iMX8X, Apalis iMX8XDebian Base ContainersLow

Description: Error when trying to install qt5-default: trying to overwrite '/usr/lib/aarch64-linux-gnu/libGL.so.1', which is also in package libgl1:arm64 1.1.0-1.

4.0.0-devel-202006 (Release date: 2020-06-01)
4.0.0-devel-202006 Monthly Release. Learn more on https://www.toradex.com/news/torizon-core-prerelease-4-0-0-devel-202006
TOR-1027New FeatureQt with GPU acceleration support on iMX8Verdin iMX8M Mini, Colibri iMX8X, Apalis iMX8XDebian Base Containers, Debian Packages

Description: Create Debian packages and a sample container to have Qt with GPU acceleration support on iMX8.

4.0.0-devel-202004 (Release date: 2020-04-07)
4.0.0-devel-202004 Monthly Release
TOR-777New FeatureSHT3x sensor support on i.MX 8 series modulesVerdin iMX8M Mini, Colibri iMX8X, Apalis iMX8, Apalis iMX8XKernel

Description: Add SHT3x sensor support on i.MX 8 series modules

TOR-776FixedCFS Quota/Period support on i.MX 8 series modulesVerdin iMX8M Mini, Colibri iMX8X, Apalis iMX8, Apalis iMX8XLow

Description: Enable CFS Quota/Period support on i.MX 8 series modules

TOR-763FixedU-Boot devicetree overlays support on Verdin modulesVerdin iMX8M MiniLow

Description: Enable U-Boot devicetree overlays support on Verdin modules

TOR-498New FeatureVerdin iMX8M Mini supportVerdin iMX8M Mini

Description: Add Verdin iMX8M Mini to TorizonCore

TOR-54New FeatureVerdin iMX8M Mini supportVerdin iMX8M Mini

Description: Support for Verdin iMX8M Mini

Not Planned
TOR-2406Known IssueHW Accelerated Chromium is not able to render SVG Images on Debian Bullseye containerApalis iMX8, Colibri iMX8X, Verdin iMX8M Mini, Verdin iMX8M PlusDebian Base ContainersLow

Description: When running hardware-accelerated Chromium, SVG images are not rendered.

This is an issue in the upstream Chromium project, see the chromium-ozone-wayland 101 SVG issue, therefore the TorizonCore team will wait until there is a fix upstream.

Update: this issue only affects the Torizon container for Debian Bullseye (tag with major number equal to 2). The container for Debian Bookworm (tag with major number equal to 3) is not affected.

Workaround: There are alternatives:

Backlog
TOR-3032Known IssueXwayland falls back to software rendering due to broken Glamor support on i.MX8-based SoMsApalis iMX8, Colibri iMX8X, Verdin iMX8M Mini, Verdin iMX8M PlusDebian PackagesLow

Description: Xwayland is being started with Glamor disabled, which leads it to fallback to software rendering without 2D graphics acceleration.

This is being fixed in the meta-freescale layer, in the issue xwayland: glamor support broken on iMX8, and once fixed we will leverage it to reintroduce graphics acceleration.

TOR-2969Known IssueGraphical applications fail to run on Verdin iMX8M Mini DualLite with error "ioctl(DRM_IOCTL_GEM_CLOSE) failed failed to initialize GBM"Verdin iMX8M MiniAutomated testing, Debian Base Containers

Description: Under unknown circumstances, in rare occasions, the error "ioctl(DRM_IOCTL_GEM_CLOSE) failed failed to initialize GBM" is thrown when trying to run graphical applications (it was seen at least once when running the kmscube demo application). After extensively trying to reproduce this error, it was decided to not work on it anymore until a means to reproduce it is found. So far, there are no affected customers, therefore if you get this error, please contact us.