Search by Tags

TorizonCore Issue Tracker

 

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

  • Submitted (open): new features and bug fixes for TorizonCore 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 TorizonCore 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 TorizonCore into the device. Toradex also offers offline installers.

Clear Filter
Issue #StatusSubjectModuleComponentsSeverity

5.7.0-devel-202205 (Release date: 2022-05-09)
5.7.0-devel-202205 monthly pre-release
TOR-2161New FeatureAs a developer, I want to investigate how to run graphical applications on a headless boardNot applicableAutomated testing

Description: Running graphical applications on a board that does not have a display connected can be useful. For example, it may help validating graphical apps on CI pipelines, or remote accessing a board while sharing it with others during a development phase.
While we execute this task mainly motivated to improve our CI pipeline, as we consider some results of this investigation useful to customers, we will publicly document them. If you have interesting in such, please contact us.

Update 1: how to force a display connector state to "on" is documented on Working with Weston on TorizonCore - Running graphical application without a display connected.

Workaround: Check if the display connector state is on. If not, force it with a command similar to "echo on > /sys/class/drm/card1-HDMI-A-1/status", depending on your board.