TorizonCore Issue Tracker

Issue #	Status	Subject	Module	Components	Severity

5.7.0-devel-202205 (Release date: 2022-05-09)
5.7.0-devel-202205 monthly pre-release
TOR-2161	New Feature	As a developer, I want to investigate how to run graphical applications on a headless board	Not applicable	Automated 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.
5.6.0 (Release date: 2022-04-08)
5.6.0 quarterly release. Learn more on https://www.toradex.com/news/torizon-core-release-5-6-0-quarterly-release
TOR-2211	Fixed	LAVA test case for TorizonCore "hw-automounting-test" is failing	Not applicable	Automated testing	Low
Description: Our CI test infrastructure caught a regression on automounting a USB stick. This is due to the fact that, if a drive without a partition table is inserted during boot, it is not mounted properly. On hotplug, it does work as expected.
Not Planned
TOR-2654	Known Issue	Add, remove, and then re-add a secondary lead to the error “At least one ecu in EcuIdentifier was already used and removed for DeviceId and cannot be reused"	Not applicable	Aktualizr, Automated testing	Low
Description: In the TorizonCore update system, each updateable component - the OS, the application described by a Docker Compose file, the bootloader, and possibly other components in the future - is registered as a new ECU when introduced to a new TorizonCore release. The ECU naming comes from the automotive industry, and in our case it can be interpreted as a component that can be updated alone. Due to how the updates are implemented in TorizonCore, you cannot automatically - that is, without manual intervention - update the OS to a version that has a new ECU, downgrade to a version that does not have it, and then update again to a version that has it. The system will see this as an attempt to add, remove, and re-add the ECU. This is a rare scenario, and one example when this can happen is when Toradex introduced bootloader upgrades - which in practice introduced an ECU. If you update from TorizonCore 5.7.0 or older to 5.7.2 or newer, then downgrade to 5.7.0 or older, then update to 5.7.2 or newer, you will get the error “At least one ecu in EcuIdentifier was already used and removed for DeviceId and cannot be reused". Workaround: Run the following command on the affected device: "rm -rf /var/sota/storage/bootloader"
Backlog
TOR-2969	Known Issue	Graphical applications fail to run on Verdin iMX8M Mini DualLite with error "ioctl(DRM_IOCTL_GEM_CLOSE) failed failed to initialize GBM"	Verdin iMX8M Mini	Automated 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.

Torizon OS Issue Tracker

How to obtain the Torizon OS Images