TorizonCore Issue Tracker

Description: Enable the Texas Instruments PCM1681 CODEC device driver as a module.

Description: Enable the SHT40 humidity sensor device driver as a module

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.

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

Description: Enable the kernel config CONFIG_LTC1660 as a module on TorizonCore 6 for the Linear Technology LTC1660 and LTC1665 DACs

Description: Due to the Docker daemon starting too early in the boot process, before the usermount service that mounts the external storage, sometimes the Docker data on external storage failed to boot the board and led to an infinite reboot loop.

Description: Enable ISO 15765-2:2016 CAN Transport Protocol (CAN ISOTP) support on TorizonCore 6

Description: Lockboxes don't accept OCI images by default, and therefore support in being added to address this use case.

Description: On TorizonCore 6, only Debian Bookworm containers are tested and thus officially supported by Toradex - even if the previous Debian Bullseye containers are expected to work.

Due to this, Chromium and Cog containers based on Bookworm are provided.

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.

Description: As reported on the Toradex community post OSTree rolling back to "unconfigured" state after flash/deploy, OS rollbacks fail with error "EFI boot manager: Cannot load any image" in TorizonCore 6.

Workaround: Update to TorizonCore 6.3.0-devel-202306 or newer.

Description: Enable the SPI/SDIO to Wi-Fi Module Microchip ATWILC1000 device driver as a module.

Description: The ethtool utility is useful for examining and tuning the settings of ethernet-based network interfaces.

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

Description: In TorizonCore 6 it is not possible to configure the CAN interface with the command "ip" (for example, "ip link set can0 type can bitrate 125000") outside a container. This leads to the error "either "dev" is duplicate, or "type" is garbage" when trying to bring up the CAN interface.

Workaround: Use the "ip" command inside a container, as described on How to Use CAN on TorizonCore.

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.

Description: Enable the HIDRAW interface in TorizonCore. To learn more, read the Linux kernel document HIDRAW - Raw Access to USB and Bluetooth Human Interface Devices.

Description: When synchronous updates happen, the reboot command may be called before the container (application) updates are finished, leading to a reboot in the middle of the process. This leads to an update failure and rollback to the previous state. This was seen with big containers when performing offline updates. Although it has never been reported, in theory, this bug can affect online updates as well.

Workaround: A workaround for TorizonCore 5.7.y and 6.1.0 is available. A side-effect of the workaround is that updates take longer to complete.
Create a new configuration file for Aktualizr as specified in the article Aktualizr - Modifying the Settings of Torizon Update Client, with the following contents:
[uptane] force_install_completion = true
Then, disable the current reboot mechanism as specified in the section enabling and disabling automatic reboot.
This configuration will still trigger the reboot, and it's expected to take a longer time before it happens.

Description: On the Toradex community post USB Storage Encryption, a user has asked how to have a USB storage device encrypted and that can be used with TorizonCore.

We have enabled the kernel config options CONFIG_DM_CRYPT, CONFIG_FS_ENCRYPTION and CONFIG_ECRYPT_FS, so you can leverage those for either full-disk or file-based encryption. Please note however, that the TorizonCore team does not fully validate this use case nor provide documentation about how to use encryption with TorizonCore at the moment, thus you must consult documentation from other sources, such as encryption projects, for more details.

A good starting point to learn more is Sergio Prado's blog post Introduction to Embedded Linux Security - Part 1.

Description: Enable the LTS2952 Pushbutton PowerPath Controller with Supervisor device driver as a module.

Description: Due to missing firmware, Wi-Fi is not working on Verdin iMX8M Plus V1.1A.

Workaround: Build a custom version of TorizonCore with the Yocto Project, including the package "linux-firmware-nxp89xx" in the build.

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.

Description: Enable the TI OPT3001 digital ambient light sensor.

Description: Secure offline updates only support a physical medium for updates - an SD Card or a USB stick. That said, the following unhandled exception was reported when someone tried the unsupported use case of NFS storage instead of a physical medium: "Aktualizr::RunForever exiting: boost::filesystem::status: No such device: "/nfs/update"".

This error might also affect supported use cases, for instance, if the physical medium does not behave as expected. Therefore we are working on fixing it.

Description: The pluggable media such as SD Card and USB Stick are meant to be mount at "/media/label", but sometimes it is mount at "/media/root/label".

Description: Every device tree overlays that's loaded by the bootloader gets a node under /proc/chosen/device-tree/overlays/overlay_name.dtbo, and its value is the return value of the load/apply operation by the bootloader. So now you can properly check whether all overlays were properly applied during runtime.

Documentaiton is available on Checking applied overlays.

Description: Enable the kernel config option CONFIG_INV_ICM42600_I2C as a module on TorizonCore 6 for the Invensense ICM-42688-P 6-axis MEMS MotionTracking device support

Description: The gateway to which devices connect to access the platform is being updated, and with it, the new gateway certificate is being updated on TorizonCore. This should be transparent to all users of the Torizon Platform Services, as long as they update their devices to TorizonCore 6 or newer until 2030.

Description: Enable the kernel config options CONFIG_NET_DSA_SMSC_LAN9303, CONFIG_NET_DSA_SMSC_LAN9303_MDIO, CONFIG_NET_DSA_TAG_LAN9303 and CONFIG_NET_DSA as modules on TorizonCore for the Microchip LAN9303 3-Port 10/100 Managed Ethernet Switch support

Description: On Colibri iMX6ULL, two warnings were seen when running "docker info": "WARNING: No swap limit support" and "WARNING: No cpuset support". We will enable the SWAP configuration in the kernel, and cpuset is expected since this is a single-core CPU.

Description: The rngd.service fails to start on Verdin iMX8M Plus, which may lead to a slower boot.

Update: this was fixed at the BSP level for release 6.0.0, therefore this ticket has been rejected.

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.

Description: The Colibri iMX7 boot hangs during the kernel startup.

Update: this was fixed at the BSP level, so nothing was done on TorizonCore. Use a nightly image from September 30 or newer to get the fix.

Description: Enable kernel config options on TorizonCore for the Microchip KSZ9897 7-Port Gigabit Ethernet Switch with SGMII/RGMII/MII/RMII support, as a module

Description: Every time the "setup-environment" script is run, it automatically appends data to "auto.conf", making it inconvenient to use it.

Description: As TorizonCore 6.0.0 release gets closer, we start doing internal work on updating the documentation for the release.

Description: This backport refers to the bugfix TOR-2458.

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.

Description: Enable the kernel config options CONFIG_W1, CONFIG_W1_MASTER_GPIO and CONFIG_W1_SLAVE_SMEM as modules on TorizonCore for the DS2401 Silicon Serial Number support

Description: The error "Top level object in '/var/sota/storage/docker-compose/docker-compose.yml.tmp' needs to be an object not ''." shows up in rare occasions, due to power cut on secondary updates leading to an empty /var/sota/storage/docker-compose/docker-compose.yml.tmp file. This leads to a scenario where the board cannot recovery from updates in the web UI and thus leads to a state where application updates cannot be performed anymore.

We are fixing it by making the file creation operation atomic, so it properly fails and rolls back if the file is not populated with the expected content during a power cut.

Description: The error "docker: Error response from daemon: transport is closing: unavailable." was identified by our test infrastructure on some SoMs, as Colibri iMX6ULL, Colibri iMX7, and Apalis iMX6D 1GB IT. We are investigating why.

If you experience the same error, please report it in our community website.

Update: we have downgraded from docker-moby 20.x to docker-ce 19.03.14, which is proven to be stable from our previous releases and test cases.

Description: During our internal tests to validate the secure offline updates implementation, we have noticed that synchronous updates don't work.

Description: The Weston configuration file does not make changes as expected. This was identified when trying to rotate the screen by 90 degrees, as documented in Working with Weston on TorizonCore.

Workaround: We suspect this is an issue with sharing the configuration file with the Weston container. Try to share the entire directory where the configuration file is located, instead of only the file itself. For example: "-v ${PWD}/weston/:/etc/xdg/weston" or "-v ${PWD}/weston-dev/:/etc/xdg/weston-dev"

Update 1: It seems that the underlying culprit are trailing whitespaces. Ensure that your configuration file does not contain trailing whitespace.

Update 2: in the end, the "name=*" line of the configuration file was commented out. Please remember to uncomment this line to make your customization effective.

Description: Enable kernel config CONFIG_NETFILTER_XT_MATCH_OWNER in TorizonCore, as requested by a customer.

Description: Currently, it is stated that splash screen on Apalis iMX8 is not supported due to an NXP DRM driver limitation.

However, if the HDMI interface is disabled (HDMI device tree overlays removed) and only the LVDS interface is enabled (LVDS device tree overlays added), then the splash screen shows up on the LVDS display.

Description: The provisioning service has a timeout of 30 minutes. We plan to reduce it to 5 minutes, so provisioning retry does not take too long in case it's required.

Description: The current default "weston.ini" provided in our Debian containers has a trailing space in the commented line "#[output]". If this line is uncommented, a silent error happens due to the file being considered malformed.

Workaround: Remove the trailing whitespace manually.

Description: We plan to bump the Chromium version in our kiosk mode browser container as regular maintenance. We plan to enable hardware acceleration specific to the GPU, related to operations as rendering.

Update: hardware-accelerated Chromium has been released! Learn how to run it on .

Description: On development PCs with newer versions of Git that address CVE-2022-24765 and CVE-2022-24767, the TorizonCore build with Yocto Project/OpenEmbedded fails.

Workaround: This is fixed on commit 256b379f02da66522eb20d93071f95b9bd859f8e, update your local version of meta-toradex-torizon to this commit or newer.

Description: If you push an application update with a given version, let's say "1.0", then you override the Docker Compose on the Platform Services but use the same version "1.0" and push a new application update, this leaves the device into an application update hanging state.

Description: The kiosk-mode-browser includes both Chromium and Cog. To keep things lean for customers and also easier for us to maintain, we will split the container in two.

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.

Description: The persistent journald logging should work, as it has been tested in the past. The feature was reported as not working in our community, therefore we are investigating and fixing it.

Update: the documentation is updated and the reported issue is fixed.

Description: In the Torizon Platform Services, you can perform synchronous updates. In other words, you can deploy OS and application updates together.

We have documented it on Torizon Remote Updates Technical Overview - Synchronous updates (5.4.0).

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.

Description: Every time we release a TorizonCore version (quarterly or LTS) we test Qt using different back-ends, including the "linuxfb". We have noticed that, after running a Qt app with this back-end, it is not possible anymore to access the device via VNC/RDP, and a reboot is required.

Our latest findings show that the problem is due to the app leaving the TTY stuck in "graphics" mode instead of returning to "text" mode after the exit of the program. We are investigating how to ensure the TTY is returned to the "text" mode before an application is restarted.

Workaround: For this specific sample, if you exit it by pressing "Ctrl+Q" or "Right click --> Quit", it will properly return the TTY to "text" mode as to not let the error happen again. We are still evaluating why it happens, though.

In general, if you need VNC/RDP access, run your Qt app with either the Wayland or the EGLFS/KMS back-end for the moment.

Update: we have added a script to the weston Debian container to make sure the terminal is always reset to a usable state. This should fix the issue while being transparent to you.

Description: The "ifupdown" plugin for NetworkManager is included in TorizonCore and disabled by default. As stated in our article Networking with TorizonCore, please refer to the official NetworkManager docs on how to use the plugin.

Description: We lack documentation on what does a "successful remote application update" means. This creates a misalignment between what customers expect from the feature and how it behaves. It has been documented and is available in the Torizon Remote Updates Technical Overview.

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.

Description: Nowadays, certificate-based authentication is a more secure and preferred method over password-based authentication. Nevertheless, we want to at least provide the tools for our customers to create strong passwords, shall they decide to use this method.
When this task is completed, you will get documentation explaining how to enforce the setup of a strong password and learn more about certificate-based authentication.
TorizonCore will not change the default implementation on how to set a new password: you are required to update the password on the first login, but you still can set a weak password without being prompted about it.

Description: Currently, when you install TorizonCore and provision it on the Torizon Platform Services, the Platform does not display the TorizonCore version that is installed on the device. This is a limitation that must be first fixed in libaktualizr.
This fix will allow users of the Platform Services to see the TorizonCore version that is installed on the board during the first installation.

Description: If you are interested in monitoring the output of your containers (stdout and stderr), it is made possible with Fluentd. Learn how to do it on Device Monitoring in TorizonCore - Containerized Application Monitoring.
Keep in mind that you have to implement the server-side monitoring since the Torizon Platform Services currently don't interpret and present this data.

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.

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.

Description: Enable MS5637 I2C temperature/pressure sensor in TorizonCore.

Description: TorizonCore is failing to build in the plymouth's do_fetch task. The reason is that the upstream project renamed the master branch to main.

Description: The rngd service is failing on Colibri iMX6ULL eMMC because there is no entropy source (that is because iMX6ULL doesn’t have the CAAM module).

Description: There is an issue with the libopencv-java/jni package being interpreted as a mutli-arch package. This can cause issues when this package is pulled into a non-arm based container such as our "debian-cross-toolchain*" container images.

Description: Update Torizon Debian containers to the Bullseye stable release.

Description: The aktualizr-torizon project fails to compile outside of Yocto builds (i.e. when built manually).

Description: There is an issue when running neofetch inside Torizon's Debian-based containers, where Torizon's logo is not showed.

Description: Add Colibri iMX6ULL 1G (eMMC version) in TorizonCore.

Description: Measure, optimize and document TorizonCore boot time.

Description: On Colibri iMX6ULL, we cannot deploy custom images generated by TorizonCore Builder.

Edit: in the end, we have identified this an issue related to OSTree and U-Boot, and have fixed it with a patch in our OpenEmbedded layer meta-toradex-torizon. No changes were applied to TorizonCore Builder.

Description: Between the splash screen and Portainer, we can see a console terminal. The transition between the splash screen and Portainer should be smooth.

Description: Poor chromium performance on Colibri iMX8X when running the Grafana sample application.

Description: Installation of qtdeclarative5-dev fails inside a Debian container.

Workaround: Workaround 1: Forcing the package in Debian feed: apt-get install ... qtdeclarative5-dev:arm64=5.15.2+dfsg-5 Workaround 2: updating /etc/apt/sources.list in Dockerfile to use the new snapshot: RUN sed -i 's/20210525T091852Z/20210626T065617Z/' /etc/apt/sources.list

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.

Description: Change Torizon logo in the Portainer interface.

Description: After updating to version 88.0.4324, Chromium doesn't start in fullscreen anymore.

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

Description: Add neofetch in TorizonCore and Debian containers.

Description: VT switching between getty 1-6 (as enabled by systemd by default) and Weston running in the container does not seem to work.

Description: Implementation of a proxy in Aktualizr-Torizon to receive JSON formatted data from a local TCP socket and send it to Torizon OTA.

Description: Add TorizonCore support on Verdin iMX8M Plus.

Description: Change credentials of the PWM files to a pwm group, and add the torizon user to it. That way, the torizon user can access the PWM interface without root access.

Description: Update chromium package to version 88.0.4324 and rebuild kiosk-mode-browser containers to the latest Debian Bulleye snapshot.

Description: Integrate systemd watchdog feature in TorizonCore.

Description: Add Fluent Bit log collector/forwarder to TorizonCore. The service will be disabled by default and may be configured/enabled by the user.

Description: Add to TorizonCore i2c-tools (i2C bus utilities) and evtest (input subsystem utility).

Description: Aktualizr update client application forked and renamed to Aktualizr-Torizon.

Description: Since we have now Colibri iMX8X V1.0D, let's remove "for V1.0C HW" from the image name.

Description: Missing permission for the video group on /sys/class/backlight/backlight/bl_power.

Description: Create a container to run Cockpit in TorizonCore.

Description: When deploying a new OSTree image with TorizonCore Builder, the system automatically rollback after 3 reboots.

Workaround: After the deploy command, and then reboot, run the following commands: $ sudo fw_setenv upgrade_available 0 $ sudo fw_setenv bootcount 0

Description: Currently, we do not do any authentication when pulling container images in Aktualizr. That means we only support pulling from a public registry. If we have for example container images from a private registry defined in docker-compose.yml, it won’t work due to the lacking of authentication. So we need to investigate and document the best approach to authenticate in private registries in TorizonCore.

Description: Bump Portainer container version from 2.0.0 to 2.1.1.

Description: Debian package wayland-protocols bumped to version 1.20.

Description: Debian package libg2d-viv bumped to version 6.4.3.p1.0

Description: Containers graphics-tests and graphics-tests-vivante available to test the graphical stack on a running device.

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.

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.

Description: TotalCross has a Partner Demo Container that runs on top of Weston, and we should add it to the list of Portainer templates.

Description: It is annoying to have the keyboard popping up all the time when you have a non-touch display and a mouse + keyboard attached, especially on a VGA screen where the keyboard uses a relevant amount of space.

Description: Change the Debian Shell template to use the weston-terminal application from the Weston container.

Description: Docker compose config files are missing in Aktualizr.

Description: A new machine verdin-imx8mp has been introduced in meta-toradex-nxp layer, let's add the support in Torizoncore.

Description: Create PREEMPT_RT validation containers and measure worst-case latency on all TorizonCore supported modules.

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

Description: We need to update the gstreamer-plugins-good-imx package to match the NXP 5.4 based release.

Description: TorizonCore already has PPP support in kernel space, but it is lacking PPP support in NetworkManager.

Description: Move to Portainer Community Edition (Portainer CE)

Description: There is no weston-touch-calibrator for bullseye yet. We don’t need to compile weston-touch-calibrator as we had to for buster but we still need to add the special init file which exposes the touch API.

Description: Debian base container does not start the shell when run with no args.

Description: Move the HDMI firmware to the root filesystem so it is updateble via OSTree.

Description: Remove the boot partition from TorizonCore images.

Description: Enable useful config options in mainline/downstream kernel.

Description: It is possible to customize the Portainer logo. Toradex logo can be added as example.

Workaround: Go to the Portainer "settings", enable the option "Use custom logo" and paste the URL to your logo.

Description: Add the following WiFi firmware to TorizonCore: linux-firmware-rtl8188eu
, linux-firmware-rtl8192cu and linux-firmware-sd8997.

Description: The symlinks to eMMC devices are not being created, and fw_setenv/fw_printenv commands are not working.

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

Description: WiFi doesn't work on iMX8 based modules

Description: nmcli commands should not require sudo

Description: It seems that the System boot is categorized as degraded because of the polkit daemon.

Description: TorizonCore images by default should have configured docker-compose as a secondary.

Description: Currently TorizonCore images for iMX6ULL are published in the TEZI feeds, and it is not clear in the description of the images that they are experimental and TorizonCore is not officially supported on iMX6ULL. So let’s change the name and description of the images to improve this situation.

Description: Make the boot scripts update-able with Aktualizr via OSTree.

Description: Move all samples containers to Bullseye.

Description: Change the exposed TCP port of the ASP.NET/Blazor container to 8841.

Description: Standardize TCP ports used by Web UI applications in TorizonCore.

Description: iMX8 Qt5 OpenGL issue when linking against Standard Debian Qt5 Libraries

Description: Environment variables used to define containers tags compatible with TorizonCore should be bumped to Debian Bullseye.

Description: /etc/sudoers.d/torizon renamed to /etc/sudoers.d/50-torizon

Description: gstreamer sample container fail while building for armhf

Description: The Aster bottom USB isn't working on the TorizonCore image on Colibri iMX6.

Description: Make it possible to receive users and groups updates via OTA event if the local users and groups files are changed.

Description: Automount USB storage devices at /media//.

Description: Documentation with an overview of 'best practices' regarding Docker Containers

Description: Make it possible to update containers without rebooting.

Description: New architecture for the Toradex Debian packages feeds

Description: TorizonCore based on Yocto Project 3.1 (Dunfell) LTS release.

Description: Add to OSTree metadata the OpenEmbedded build information.

Description: Add bash completion support to Docker and OSTree.

Description: Prevent Aktualizer from setting bootcount and upgrade_available to zero on every boot to avoid wearing of flash.

Description: Add basic OpenEmbedded metadata to OSTree such as distribution, machine or image name.

Description: pkg-config is not searching in the multi-arch folders by default and this leads to issues when a configuration script uses it to collect information about a specific library/package. Adding the arch-specific path to PKG_CONFIG_PATH solves the issue,

Workaround: Manually set PKG_CONFIG_PATH to the folder where .pc files are stored for multi-arch packages.

Description: Standardizing PIN access across SoM's

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

Description: Error on dtconf when trying to apply a device tree overlay for the 7" parallel display with capacitive touch.

Description: Docker 19.03.11 fixed the rather severe CVE-2020-13401.

Description: Enable drivers in the TorizonCore Linux kernel to be supported by Gumstix's AutoBSP tool.

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.

Description: On modules without GPU support such as Colibri iMX7 or Colibri iMX6ULL the Wayland compositor Weston is started with Pixman renderer. It seems that Chromium currently does not render properly when Weston is using Pixman renderer.

Workaround: Use Weston with Mesa software OpenGL (rebuild the Debian Weston base container and drop the `--use-pixman` flag in entry.sh).

Description: We need to provide the licence files in TorizonCore binary images.

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

Description: The mwifiex.conf file is missing in /etc/modprobe.d/, therefore it is not possible to use the WiFi interface in access point mode.

Workaround: Create the file on your own with the following content: 'options mwifiex driver_mode=0x3'

Description: Using `torizon/arm64v8-debian-wayland-base-vivante` it's not possible to install `libvulkan-vivante1` due to dependency error.

Description: If the system clock is not synchronized, the command "docker pull" may fail.

Description: After open Visual Studio with the plugin installed, I can succesfully build and debug a new project. However, after terminate the first debug session, the "Rebuild Torizon Application" button become grayed out and I cannot build and run the application again.

Description: In case an older dtconf container is used the branch on the local git repo is missing. Normally we should update our containers so that they already have the branch there. However, it could be that a customer has an older container locally and upated the system or similar situation. We probably should suggest to pull from the git repo in those cases.

Description: Since vim is not “user-friendly”, let's add nano as a text editor option to the TorizonCore’s root filesystem.

Description: Overlay display_EDT5.7_parallel_res_touch.dts does not work on Apalis iMX6 (activating the overlay does not show anything on the screen)

Description: Currently TorizonCore does not have support for fw_env.conf file(s) for nand and emmc. It is needed for fw_utils to read and set boot environment variables

Description: Add support for NXP PCF85363 RTC

Description: Enable parallel RGB on Colibri iMX8X by default. Set resolution to 640x480.

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

Description: Enable use of journald log driver.

Description: Fix an issue that prevents Qt5 Containers to run on iMX8 modules

Description: Show the splash screen earlier and transition to the UI later to improve splash screen display time

Description: Add Verdin iMX8M Mini to TorizonCore

Description: Add Colibri iMX8X support

Description: Create a tool to manage device tree overlays on device

Description: Add support for splash screen

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

Description: Add basic support for Apalis iMX8

Description: TorizonCore provides system links to all standard Toradex interfaces (e.g. /dev/ttycolibri0-3, /dev/i2c-colibri)

Description: Enable kernel per-process IO accounting.

Description: Add Colibri iMX6ULL support

Description: Support USB-to-Serial converters on i.MX8 modules

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.

Description: Fix bug that was preventing LVDS Atmel Tochscreen from working properly

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"

Description: Wireguard requires UDP access to function. There are some use cases where a TCP-based solution is needed.

Workaround: It is possible to run OpenVNP on TorizonCore. Read the article OpenVPN and Weston's VNC/RDP on TorizonCore for more details.

Description: It has been reported by a customer that the PREEMPT_RT version of TorizonCore reboots spontaneously on Apalis iMX8. Internally, we were able to reproduce this bug on TorizonCore 5.7.0.
As of July 2022 - when 5.7.0 LTS has been released, the images with the PREEMPT_RT patch haven't been fully validated by Toradex. We have only run smoke tests and cyclictest to make sure that the system boots properly and the PREEMPT_RT patches are working on idle conditions.
In the TorizonCore Download Links we only list PREEMPT_RT images as monthly pre-releases, because they don't go through our validation steps to promote them to production-ready.
This bug is rejected because the customer who reported it didn't follow up on it and we suspect they may have been able to use the regular image without PREEMPT_RT, or another alternative. If you are waiting for this bug fix, please contact us so we can re-evaluate this decision and possibly resume our investigation.

Description: Although we advise customers to keep the first UART dedicated to debugging purposes by default, in the end, it should be a customer decision (for example, it may make sense in scenarios where security concerns are high).
Our investigations show that it isn't possible to keep an easy-to-use solution in TorizonCore Builder, therefore we may document our findings with documentation, but we won't provide this as a feature. Please have a look at the workaround below to find some documentation.

Workaround: You can find some useful information in the article Configuring Serial Port Debug Console (Linux/U-Boot).

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.

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.

Description: Support for hotspot, or in other words, AP mode with internet forward, will be added to TorizonCore.

Description: Due to a mismatch between how the client and the server calculate the hashes of packages names and versions, updates of packages that contain multi-character bytes in their name or version fail.

Workaround: Only use non-control ASCII characters in package name and version.

Description: The weston.ini configuration file is strict with syntax errors, and it doesn't allow trailing whitespaces.

Workaround: When applying any configuration described either on the official Weston documentation, or on our article Working with Weston on TorizonCore, make sure there are no trailing whitespace in your configuration file.

Description: The log message with a result equal to INTERNAL_ERROR results from the online updates call chain and it does not affect offline updates. Post the Secure Offline Updates MVP we plan to support concomitant online + offline updates and then review this log message.

Workaround: Just ignore the message.