TorizonCore Issue Tracker

Description: In preparation for making bootloader updates available, we are working on documentation on when, why, and how to use it.

Description: As we prepare to release the first TorizonCore 6.x nightly builds, some tasks must be done to make such nightly builds publicly available.

Description: As regular maintenance, Debian packages based on NXP 5.15 are being updated for TorizonCore 6.x.

Description: Toradex keeps a client implementation of Aktualizr named Aktualizr-Torizon and a fork of libaktualizr.
This adds overhead for feature integration and making a release. We, therefore, plan to use a single fork and keep our client implementation in the same repository.

Description: Keeping a healthy master branch is useful for long-term maintenance. We are giving it a try on building TorizonCore from the master branch and booting it.
Keep in mind that we have not yet decided if we will even release those builds, and even if we do, their quality will never be guaranteed to any degree. Those are mostly for aiding the internal process of developing TorizonCore.

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 kernel config options on TorizonCore for the MCP23S17 16-Bit I/O Expander with Serial Interface support, as a module

Description: Docker uses a configuration file that is kept by default in the user directory (something like "/home/user/.docker/config.json"). This is not ideal for TorizonCore, since the home directory is not touched by updates, and user configuration hardly ever makes sense. Due to that, some of our services explicitly set the DOCKER_CONFIG environment variable to use the config file at /etc/docker/config.json, which is great because, as a user, you can customize it, capture changes with TorizonCore Builder, and replicate the configuration to all boards.

Recently, it was reported that the configuration file /etc/docker/config.json was not being used by the docker-integrity-checker and the docker-compose services, leading to unexpected behavior.

This is being fixed in a way that the DOCKER_CONFIG variable is globally set in TorizonCore, so all systemd services and the shell environment make use of it.

Workaround: Create a systemd override for the affected services that appends the line Environment="DOCKER_CONFIG=/etc/docker", then capture changes with TorizonCore Builder.
Or set "/home/torizon/.docker/config.json" and "/etc/docker/config.json" with the same contents.
Or use a symbolic link from one file to another.

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.

Workaround: As we are actively working on fixing this issue, update your TorizonCore to the latest nightly until the bug is fixed. Until then, synchronous updates are expected to not work.

Description: A generic secondary allows reusing the implementation for various tasks such as updating Docker Compose, bootloader, Arm Cortex-M firmware, among others. An interface must be defined to allow writing the specific part of code that cannot be reused and must be connected to the generic secondary.

Description: As we work on bootloader updates, we have decided to implement it in a way that a generic secondary mechanism allows users to write secondary-specific "action handlers" in the future. At the moment, we will focus on implementing the "bootloader update" action handler.

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: TorizonCore Builder will contain features that allow devices to be provisioned to the Torizon Platform Services without manual intervention. This allows you to provision devices during production programming.

Update: documentation is available on Production Programming in Torizon.

Description: imx-parser is required to support VPU on some SoCs.

Description: linux-imx-headers allow building GStreamer with ion allocator support, which is a pre-requisite for enabling VPU on some SoCs.

Description: The message “Offline-mode header not found…“ is not very important on the default log level. It can bring more confusion than help in the early debug stages. We plan to drop the log level so it is omitted by default.

Description: Enable kernel config options on TorizonCore for the SJA1000 CAN controller support, as a module

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: As of the merge of offline updates into TorizonCore, it is not possible yet to start the service automatically, due to some constraints added to ensure online operation.

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: In TorizonCore, we delay the loading of the mwifiex driver (for on-SoM Wi-Fi), so the boot time is reduced, as mentioned on TorizonCore Boot Time Optimization.

Since this is unique to TorizonCore, different behavior than what the Toradex BSP provides, we decided to write a test case for it.

Description: As part of our maintenance policy, we periodically rebuild the Debian containers provided for Torizon.
Your software should not be impacted, as this maintenance build only bumps the minor version of the containers. Nevertheless, you are encouraged to test your software and consider using the newer version, to benefit from bug and security fixes provided by the Debian community.
To learn more about our containers release strategy and versioning, visit the article TorizonCore Containers Tags and Versioning.

Description: Every quarter we do some maintenance such as updating external layers in our manifests, updating software versions in meta-toradex-torizon, among others.

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: Enable kernel config options on TorizonCore for the NXP SC16IS7xx (via SPI) and the PWM Servo Module PCA9685 support, as modules

Description: When we integrated Cog in our kiosk-mode-browser, a bug prevented it from working on GPU-less SoMs (Colibri iMX6ULL and Colibri iMX7).

This has been fixed and it is possible to run Cog on GPU-less SoMs. Learn more on Running Cog

Description: We enable support for matrix keyboard in TorizonCore, shipping it as a module

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: This is a regular maintenance task, as we want to build the Docker engine from a newer, supported version, and this requires building Docker from a different layer.

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.

Description: Torizon uses the meta-lmp layer from Foundries.io. During the quarterly TorizonCore maintenance, this layer version was bumped to newer release. It introduced some fields in the /etc/os-release file that have not been reviewed by Toradex. Some of them point to "foundries.io", others may not be required by Torizon. We will review and update the fields accordingly.

Workaround: We have not seen any side effects. You can safely ignore the new fields for the moment.

Description: On TorizonCore, the loading of on-SoM Wi-Fi drivers are delayed, to improve application boot time. Currently the drivers are loaded for each SoM based on the hostname. This leads to the drivers not loading if the hostname is changed.

The method to infer the SoM model will be changed to allow customers to change the hostname without such an impact.

Workaround: Until the fix is released, avoid changing the hostname.

Description: We enable support for the Rotary encoders connected to GPIO in TorizonCore, shipping it as a module.

This has been requested in our community

Description: This task is a prerequisite for the secure offline updates MVP that we are working on. It will make it possible to perform application (container) offline updates.

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: At the moment, the only supported method for provisioning devices to the Torizon Platform Services is by manually copying the provisioning command from the web interface into the board terminal.

We are working on an implementation that will allow provisioning at scale, in other words provisioning many devices to the platform automatically. In this task, we add support on TorizonCore.

When provisioning at scale is fully implemented, we will provide documentation on how to use it.

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: Given that the Uptane standard has accepted the PURE-2 enhancement, we at Toradex are implementing such in the aktualizr source code. This will be a fundamental part of the secure offline updates MVP being developed by Toradex.

Description: In this task, we implement offline updates metadata validation in the libaktualizr. This is a pre-requisite for the secure offline updates MVP we plan to release.

Description: Even though we pay attention to best practices since practically the birth of Torizon, so far we didn't use a linter in our CI pipelines. After some investigation, we have decided to adopt hadolint and we recommend that, if you write your own Dockerfiles, you also use a linter.

As an example, you can see the implementation in our torizon-samples repository. we ignore some warnings on a per-repository basis, adapted to their context.

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: The ifupdown plugin for NetworkManager may be useful to few TorizonCore users. We evaluate the impact of shipping TorizonCore with this plugin and, if the outcome of the evaluation is positive, we will include the plugin in upcoming TorizonCore releases.

After our evaluation, we have decided to ship TorizonCore with the plugin included 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.

Workaround: You must build a custom version of TorizonCore with the ifupdown plugin.

Description: As preparation for our upcoming secure offline updates MVP, we are implementing on Aktualizr and TorizonCore a mechanism to start updates as soon as a USB stick or SD card is plugged into a carrier board. This feature will be disabled by default and current users of the Torizon Platform Services - and online remote updates - will not be affected by this new feature.

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: D-Bus exposes some features from the base OS such as the ability to reboot or shutdown the system. We have evaluated if this is a security risk and came to the conclusion that, by default, it isn't. This is due to the fact that to use D-Bus from inside a container, you must explicitly bind mount "/var/run/dbus" and therefore evaluate the risk of doing so.
Keep in mind that, in the worst case, even if you expose D-Bus to your container, it will be as secure as a regular non-containerized embedded Linux system, where you don't have the additional security layer offered by containers.

Workaround: If you don't trust the software running in your container, it is advised that you don't bind mount "/var/run/dbus", or at least restrict D-Bus access to some interfaces by creating configuration files on "/etc/dbus-1/system.d/".

Description: This will allow, in the future, Toradex partners and customers to host their own OSTree repos.
This ticket is a step toward reaching this goal.
Updates on the Torizon Platform Services and our public documentation will follow, yet we don't have defined dates when they will be done.

Description: Especially during development, it is common that the system accumulates several stopped containers, networks, and dangling images. This may lead to annoying usage of storage.
Since this feature was added, TorizonCore is shipped with a systemd service named "docker-auto-prune" that you can enable during development, and it will run periodically to remove the accumulated garbage.
Learn more on Debian Containers for Torizon - Docker Auto Prune

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: This update does not impact TorizonCore customers. As preparation for the offline-updates MVP, we rebase our fork of aktualizr/libaktualizr against the latest upstream version. We also update our client implementation to use the rebased version and test it.

Description: From a customer perspective this operation will be transparent and you can continue to use TorizonCore without any impact.

The Aktuaklizr implementation is composed of two parts: (1) the client implementation, which is expected to be different for different vendors, and (2) libaktualizr, the core functionality that is used by the client implementations.
As we implement secure offline updates leveraging Aktualizr, we must make changes to libaktualizr and add patches on top of it until they are upstreamed.
The TorizonCore fork of libaktualizr is made available on https://github.com/toradex/aktualizr and it must not be confused with the implementation of the client, available on https://github.com/toradex/aktualizr-torizon.

Description: This is a regular maintenance task. Since only the minor version fo Portainer has been updated, no impact is expected for TorizonCore users.
The version of Portainer included in TorizonCore with Evaluation Containers has been updated from 2.6.2 to 2.9.3

Description: When using the torizoncore-builder push command, you can set the OS update package name and version. This way, you can easily manage and select your packages on app.torizon.io.

Description: The Colibri iMX8X 1.0B is an early sample. We advise you to move to the latest version as soon as possible.

Workaround: While you don't procure a newer version, use the latest supported TorizonCore version 5.4.0.

Description: Apalis iMX8X is being phased out and we are removing the support in TorizonCore.

Workaround: Migrate to a supported SoM that meets your requirements. Options and Apalis iMX8, Verdin iMX8M Plus and others. Browse for available SoMs on toradex.com

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: Design the generation of takeout images for offline updates in TorizonCore Builder.

Description: Improve the script that checks the integrity of Docker container images.

Description: Update Portainer version to 2.6.2.

Description: Create an article on the developer website about Weston features and configuration options.

Description: TorizonCore should be more resilient to container problems. So we need to 1) make sure the containers described in the docker-compose file are really running and 2) identify corrupted Docker data as soon as possible, and try to recover from it, like force-pulling the corrupted images.

Description: After stopping the Weston container, the console screen is not displayed on the connected display. It is just blank instead.

Description: conmon fails to build because the upstream project renamed the master branch to main.

Description: The project git://github.com/coreos/go-systemd.git has renamed their master branch to main. Due to that, the build fails.

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.

Description: We have performance issues when starting Chromium from another Chromium instance (Portainer), so let's change to Cog in the template.

Description: Enable the following ADC/DAC in the kernel configuration: AD5592R, CONFIG_AD5593R, CONFIG_AD7124.

Description: Cog is a single “window” launcher for the WebKit WPE port. It is small, provides no user interface, and is suitable to be used as a Web application container. The “window” may be fullscreen depending on the WPE backend being used.“ It can be an alternative to Chromium for HTML application development.

Description: On each execution a new .X*-lock entry is created under /tmp and XWayland keeps incrementing X display number, this generates issues for any X-based application.

Description: The repo tool has been changed a while ago to create the manifest file as a plain xml file instead of a symlink. This was causing an issue where use-head-next was being added to MACHINEOVERRIDES even on monthly/quarterly builds, causing TorizonCore builds to build from the latest u-boot/kernel trees.

Description: The kernel configuration option CONFIG_POWER_RESET_GPIO makes it possible to power off the device via a GPIO.

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

Description: The BSP stores platform (SoM) related kernel arguments in the defargs U-Boot environment variable. Let's append the content of this variable in the default TorizonCore kernel arguments.

Description: Test and document how to configure Wi-Fi Access Point mode with Network Manager in TorizonCore.

Description: Integrate Greenboot framework in TorizonCore.

Description: Add VPN support in TorizonCore using Wireguard, an extremely simple yet fast and modern VPN that utilizes state-of-the-art cryptography.

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

Description: Update via Torizon OTA is failing from the last monthly build (5.2.0-devel-202103+build.9) to the last nightly build (5.2.0-devel-20210328+build.257).

Description: Following the gstreamer article, the demo fails on iMX7 with "/dev/video2: no such file or directory".

Description: Provide kmscube and glmark2 packages for 32 bits architectures in Toradex Debian feed.

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

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

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

Description: OpenCV package updated to version 4.4.0

Description: Debian package libg2d-dpu bumped to version 1.8.12.

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

Description: Make it possible to extend container storage using external media like an SD Card or a USB stick.

Description: So for modules without GPU (colibri-imx7, colibri-imx7-emmc), let’s change the Portainer template to use the quickwidget Qt demo application.

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

Description: When doing a bad update, the rollback feature is not working as expected.

Description: The rngd service is failing on Colibri iMX6ULL.

Description: Change the Aktualizr polling frequency from 10 seconds to 300 seconds.

Description: The CROPS container provides a configured environment to make it easier to build TorizonCore.

Description: The Yocto Project community maintains a project called CROPS that provides, among other things, a Docker container to build OpenEmbedded/Yocto based Linux distributions. So let's have our own version of the CROPS container to make it easier to build TorizonCore.

Description: Provide official real-time (PREEMPT_RT) support in TorizonCore, including container(s) to validate PREEMPT_RT functionality.

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

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

Description: TorizonCore should be able to apply overlays using the overlays.txt implementation of the BSP.

Description: Error generating SDK image for TorizonCore.

Description: When using the latest TorizonCore nightly and then do a torizoncore-builder dt checkout we get the following error: "Branch name does not exist in upstream repository".

Description: Adapt the opencv sample containers to Debian Bullseye.

Description: When building RT distros (torizon-rt and torizon-upstream-rt), we should disable kernel configuration options that could impact system latency, mainly kernel debugging options and power management options.

Description: Change credentials to access hardware-related sysfs interfaces so the user can access them without running the application as root inside containers.

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

Description: Docker compose fails if power is cut during a docker pull operation

Description: CONFIG_IGB is not enabled in mainline-based modules.

Description: A bug is preventing containers from being updated if there is no /var/sota/storage/docker-compose/docker-compose.yml file.

Description: Missing UPSTREAM in in the name of mainline-based images with preprovisioned containers

Description: The automount feature of USB Sticks does not work after a reboot. It only mounts on unplug/plug events.

Description: Torizoncore does not ask for end user to set up a new password any more at the first boot.

Description: Split Colibri iMX7 TorizonCore images for eMMC and NAND based devices

Description: Release TorizonCore Builder version 1.1.0

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: Publish kiosk container Docker files to GitHub.

Description: Improve 32-bit emulation support on 64-bit host when building containers.

Description: systemd-analyze is a tool that enables system manager analysis and debugging.

Description: Kiosk container is not working in sht31 and grafana sample.

Workaround: add this to the docker-compose file: security_opt: - seccomp:unconfined

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

Description: Add modem support (3G, 4G, LTE, etc) in TorizonCore.

Description: Added git to SDK cross-compilation toolchain containers

Description: We should investigate the possibilities to have a virtual keyboard available for graphical applications.

Description: Add templates support to Portainer.

Description: Podman 2.0.0 release marks the HTTP API as stable.

Description: Research has shown that jitterentropy is causing high CPU. It seems that does threads run with regular priority, and hence really slow down the boot process. Since we install rngd mainly to fill the entropy pool from the hardware device, this change makes sure that jitterentropy is disabled by default.

Description: The default behavior of Portainer is to present a dialog which ask the user to change the password for 5 minutes, and shutdown itself if the user does not create a password for the admin account. To workaround this issue, we decided to set the container's restart policy to always. That way Portainer immediately restarts in the background.

Description: Container to help calibrating the touchscreen in the Torizon platform.

Description: Fixes a bug that was preventing i2c-tools from been installed inside a Debian container.

Description: Containers started via docker-compose can't be stopped via 'systemctl stop docker-compose.service'

Description: The AP interface 'uap0' doesn't always show up properly and only gets initialized after another reboot.

Description: Using `torizon/arm64v8-debian-wayland-base-vivante` one cannot install `libopenvx-vivante1`.

Description: Qt Widgets and QML support on devices with no HW acceleration using Weston/Mesa/Pixman

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: The devicetree overlay naming is confusing and should be improved.

Description: When using dtconf activate the output mentions that the overlay has been validated, but it is not clear that it also has been enabled.

Description: It is often helpful to be able to quickly edit a device tree overlay file. It would be good to have some kind of editor in the development tools container, e.g. vim-tiny.

Description: By default spidev on Colibri i.MX8X is disabled. It should be enabled by default to be consistent with other Torizon modules.

Description: Applications that use only widgets work when launched in a privileged container mounting /dev, those that require opengl hang.

Description: Add development tools container to pre-provisioned images

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

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

Description: Create a container to run Toradex Easy Installer Image Server with Zeroconf

Description: Add timezones support in TorizonCore image

Description: Implement a container to launch Portainer

Description: Add Apalis iMX8X support to TorizonCore

Description: Add Goodix touchscreen support to TorizonCore

Description: Creating a file under /run/aktualizr-session/need_reboot will trigger automatic reboot.

Description: Images running Balena do not support using docker-compose

Description: Support for Apalis iMX8X

Description: Colibri iMX6ULL is only supported under Toradex Labs. Images can be found on Toradex Easy Installer CI feed.

Description: Support for Colibri iMX8X

Description: Real time images are available on Toradex Easy installer CI feed.

Description: Automatically use Pixman renderer on non-GPU Modules

Description: Bump the Linux kernel to 5.4 release

Description: Support for Verdin iMX8M Mini

Description: Support seccomp in Docker

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: Qt 5 with the EGLFS backend in some specific conditions does not work. While it was identified on BSP 5.3.0 and an Apalis iMX6Q 2GB IT V1.1C, the root cause remains unknown as even on other SoMs with the same configuration it does work.

Workaround: Use the Weston backend. If you need EGLFS and Weston cannot meet your needs, please contact us.

Description: Installing Java or the use of Java-dependent applications does not work during docker build

Workaround: Do not use java directly on your Dockerfile which will use a distro based on ARM architecture. Create a multistage Dockerfile and use a x86-64 distro as a base to perform tasks that require java.

Description: Limited amount of memory on iMX6S prevents system from running fast.

Description: This is a regular maintenance task. Since only the minor version of Portainer has been updated, no impact is expected for TorizonCore users.
The version of Portainer included in TorizonCore with Evaluation Containers will be updated from 2.13.1 to x.y.z.

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: E1187: Failed to source defaults.vim

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

Description: As described in the Torizon Remote Updates Overview, application updates pull containers, then check if Docker Compose starts them without errors and last prunes the system, thus removing unnecessary containers.

A side-effect is that, between starting containers with Docker Compose and pruning them, some containers may exit/finish their task, and thus get pruned. For offline updates, there is no way for the system to pull those containers back.

Workaround: If your application includes oneshot/short-lived/ephemeral containers that exit shortly after they are started, you must add an artificial delay before the container exits, for example using the "sleep" command.

Description: While it is possible to block updates locking a given file, the offline updates are never unblocked after the lock expires.

Workaround: Two workarounds are possible. Either remove and re-attach the lockbox media to trigger another update, or restart the aktualizr service after releasing the lock.

Description: It is a common scenario to make updates over a LAN. This happens when your devices are already connected locally, but due to security reasons they cannot access the internet.

We plan to introduce a feature that allows secure offline updates over a local network.

Description: imx-vpu-hantro-vc is required to support VPU on Verdin iMX8M Plus

Description: Support JTAG Debugging in Torizon

Description: Evaluate the adoption of a MAC implementation (AppArmor, SELinux, TOMOYO, SMACK, etc).

Description: Implement secure boot support in TorizonCore.

Description: Monitor the health of the system and the running containers and implement in TorizonCore.

Description: Add VPU support for NXP downstream SoMs (iMX8/8X/8M Mini/8M Plus) devices in TorizonCore.