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.1.0 (Release date: 2023-01-16)
6.1.0 quarterly release. Learn more on
TOR-2746FixedMissing /dev/colibri-spi-cs0 symlinkColibri iMX6, Colibri iMX6ULL, Colibri iMX7Open EmbeddedLow

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.