Torizon OS Issue Tracker

Description: Enable kernel config option CONFIG_MCP4728 in Torizon OS

Description: On Torizon OS 7.0.0 it was noticed that the Splash Screen didn't work on some modules, using several display outputs (native HDMI, LVDS, and VGA).

Update: this has been fixed on 7.1.0 nightly pre-releases. It is advisable to wait for the 7.1.0 release to make this feature to production in your product, or alternatively, you may backport the solution as a patch to 7.0.0.

Description: Enable kernel config option for "Watchdog device controlled through GPIO-line"

Description: The aktualizr-data-proxy was a Torizon-specific implementation to send device monitoring data to the Torizon Cloud. It was replaced with the standard Fluent Bit HTTP output, but the old proxy was kept active in Torizon OS 6 for backward compatibility.

On Torizon OS 7 the proxy is disabled. If you have custom metrics, in other words, if you manually modified the /etc/fluent-bit/fluent-bit.conf file, check the [OUTPUT] section. It should look as follows: ``` [OUTPUT] name http match * host dgw.torizon.io port 443 uri monitoring/fluentbit-metrics format json tls on tls.verify off tls.ca_file /usr/lib/sota/root.crt tls.key_file /var/sota/import/pkey.pem tls.crt_file /var/sota/import/client.pem Retry_Limit 10 ```

Description: Enable IIO High Resolution Timer Trigger on Torizon OS

Description: Enable the device driver for the Texas Instruments DP83867 Gigabit Ethernet PHY as a module on Torizon OS 6

Description: Enable the Linear Technology LTC2497 I2C 16-Bit 8-/16-Channel DS ADC on Torizon OS 6

Description: It is a common request to be able to customize the device name on the Torizon Cloud. This usually reflects how a company manages its product lines, with company-specific unique identifiers, product names, among other parameters.

This task implements a streamlined easy-to-use mechanism for updating a product name.

Description: When trying to connect to a Wi-Fi network, the system throws "Error: Connection activation failed: (53) The Wi-Fi network could not be found."

This only happens after a cold boot.

Update: this issue is fixed on nightlies as of May 10th 2024, and will be released on upcoming monthly and quarterly releases.

Workaround: It was observed Wi-Fi works given the following workarounds:

- Restart NetworkManager with the command "sudo systemctl restart NetworkManager"
- Toggle Wi-Fi off and on again with the commands "nmcli radio wifi off" and "nmcli radio wifi on"
Then try to connect again.

It was also observed that, without applying the above workaround, NetworkManager will successfully connect after about 10 minutes since the board is powered on, regardless of whether it is the first try to connect.

Description: Some RPC-based apps seem to not work on Torizon OS 6 inside a container.

Workaround: It appears that using future versions of Containerd resolves this issue. One can backport the recipe for Containerd 2.0.0 from here: https://git.yoctoproject.org/meta-virtualization/tree/recipes-containers/containerd/containerd-opencontainers_git.bb?h=scarthgap Only very basic testing has been done on such a backport.

Description: Enable support for LED Multicolor Class Support on Torizon OS 6

Description: Enable the kernel option for the ExFAT file system.

Description: The splash screen is not displayed on the DSI to LVDS adapter interface on Verdin AM62

Description: Enable support for the Marvell SD8787 in Torizon OS, more specifically, for the power sequence of the module.

Description: The serial number is being appended to machine name to be able to have a unique device name for toradex machines. The serial number is being read out from /proc/device-tree/serial-number, but qemuarm64 and genericx86-64 machines dont have it, so currently the unique device name is not supported on these machines. A solution could be using partuuid (hexadecimal digits) of the root disk and translate it to a 8 decimal digits, since we have only one root partition and it's different for a specific build.

Description: genericx86-64 grub fail to boot per my test, this is a know issue of grub 2.6, and it's been fixed in grub upstream, OE master has the backport patch: https://github.com/openembedded/openembedded-core/commit/51eab4bb0cae46c9c32d28986eb97badf47594b7 we need port it in meta-toradex-torizon.

Description: Learn how to setup a DHCP server with internet forward in the Ethernet interface on Networking with Torizon.

Description: Pushing OS images to the Torizon Cloud with Yocto fails due to an authentication error.
Update: this is fixed in Torizon OS 6.5.0.

Description: Enable the Lattice Sil9022 RGB-HDMI bridge device driver as a module on TorizonCore 6.

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

Description: Enable support for NTC thermistor sensors on TorizonCore 6.

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

Description: Enable kernel config MAXIM_THERMOCOUPLE on TorizonCore 6 so the MAX31855 thermocouple chip can be used

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

Description: In TorizonCore 6, it is not possible to connect to a Toradex SoM with on-SoM Wi-Fi configured in Access Point (AP) mode. When configuring the device in AP mode, no errors are displayed.

Description: Enable MAC80211 (Wi-Fi) mesh networking support on TorizonCore 6.

Description: Enable the Analog Devices AD7606 ADC as a module in TorizonCore 6.

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

Description: Offline sync updates are not working on TorizonCore 6. Even though both OS and application updates are installed, the process is never concluded and after the reboot with the new OS version, the application is never started.

Update: this bug has been fixed. As a side-effect, in case a rollback happens during a synchronous offline update, the newer application container image is not removed from the system, as it should. This means that some of the flash storage space will be used without need.

Description: Enable the Ilitek I2C 213X/23XX/25XX/Lego Series Touchscreen Controller device driver as a module on TorizonCore 6.

Description: Enable the VUB300 USB to SD/SDIO IC device driver as a module on TorizonCore 6.

Description: As reported in the community thread [aktualizr, offline updates] Found in archive a file with bad file type: 40960, some docker images may contain layers that are symlinked to other layers, which leads to an error. The reason a docker image would contain a symlink in the layers is unknown.

Description: Once a synchronous update is triggered, the new application is not expected to start until the system reboots and the new OS version is available. On this bug, which affects TorizonCore 6.x releases only, the application starts on the upcoming polling for updates (which by default is 5 minutes) regardless of whether the system reboots and the new OS is loaded.

Given the TorizonCore default polling of 5 minutes and that usually, a reboot due to a synchronous update happens before that time, this bug should not affect most customer use cases. If you customize TorizonCore to use a much shorter polling time, there might be a case when this undesired behavior happens.

Description: Although unsupported on TorizonCore 5, Bluetooth has been reportedly working on Verdin iMX8M Plus V1.0. It does not work on Verdin iMX8M Plus V1.1A, though.

We plan to add basic Bluetooth support only on TorizonCore 6 or newer, without testing any specific Bluetooth profile in particular.

Description: Enable the SI5351 I2C-programmable any-frequency CMOS clock generator + VCXO device driver as a module.

Description: Enable the DS2782 Stand-Alone Fuel Gauge IC device driver as a module.

Description: Bootloader updates will only be supported with bootloader binaries published by Toradex - at least initially. Therefore, publishing them and making them available for you is necessary.

TorizonCore 5 bootloader binaries will allow you to downgrade from TorizonCore 6 to 5 if you find non-obvious bugs in the field and later decide a downgrade is necessary.

Description: Enable the kernel config option CONFIG_NET_CLS_MATCHALL so the PROFINET stack/driver from Siemens can be used.

Description: From our automated test reports, it was noticed that "lshw" is not working properly. This was found out in Aktualizr logs and it has been confirmed by running "sudo lshw -json" on the command-line. The error is "terminate called after throwing an instance of 'std::length_error'".

Aktualizr is not functionally affected, as it can recover from this issue and continue to properly function.

Description: On TorizonCore 6, the splash screen is not being displayed on SoMs that use the downstream-based NXP BSP.

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: Our platform web UI displays the currently installed packages for all ECUs for each device. This information is determined via the manifest that Aktualizr regularly sends back to the server. There is an edge case where certain sync update rollbacks will cause incorrect information to be sent in the manifest. This then causes the web UI to display the incorrect package as installed on the Docker Compose secondary.

Description: The Verdin iMX8M Mini boot hangs with a Device Tree-related error.

Workaround: Use the latest nightly builds of TorizonCore 6, where it has already been fixed.

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: Colibri iMX7 has two watchdog sources: the SoC and the PMIC. BSP 5 uses the PMIC watchdog as "/dev/colibri-watchdog", which in turn is the one used by TorizonCore. It turns out that the watchdog firmware for the PMIC on BSP 5 is not as featureful as required to ensure the "shutdown" properly works.

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: When using Vim on TorizonCore, the following message is printed before Vim is started: "E1187: Failed to source defaults.vim". While it does not prevent you from using Vim, a defaults.vim file is missing which would suppress such a message, therefore we'll add it.

Description: For a while, our device-trees repository got out of sync with the Linux kernel device trees. It is fixed as of June 9th. If you have done some work previously and your device tree is not working, please pull the latest changes.

Description: If you define a synchronous update using a vanilla TorizonCore image - that is, one provided by Toradex and not customized with TorizonCore Builder - then synchronous updates fail.

Workaround: Push a TorizonCore image to the Platform Services using TorizonCore Builder, then use this image for synchronous secure offline updates.

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

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: 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: 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: We enable support for the RTC Micro Crystal RV8803 in TorizonCore, shipping it as a module.
This has been requested in our community.

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: 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: 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: 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: 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: Enable MS5637 I2C temperature/pressure sensor in TorizonCore.

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: The aktualizr-torizon project fails to compile outside of Yocto builds (i.e. when built manually).

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

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: The project git://github.com/coreos/go-systemd.git has renamed their master branch to main. Due to that, the build fails.

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: 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: 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: 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: 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: Missing permission for the video group on /sys/class/backlight/backlight/bl_power.

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: Make it possible to extend container storage using external media like an SD Card or a USB stick.

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

Description: The rngd service is failing on Colibri iMX6ULL.

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: TorizonCore should be able to apply overlays using the overlays.txt implementation of the BSP.

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: 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: 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: 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: Since we use reproducible builds, time stamps are set to 0.

Description: Enable in TorizonCore the support to Abracon AB1805 RTC, PPS GPIO, CAN J1939 and Samba 2/3

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: Create and use torizon-upstream distro for machines that are build with mainline BSP.

Description: Add to OSTree metadata the kernel sources used to build the kernel image in that OSTree

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

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

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

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

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: 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: Containers started via docker-compose can't be stopped via 'systemctl stop docker-compose.service'

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: 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: Add timezones support in TorizonCore image

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: The error: ‘CURLOPT_PROTOCOLS’ is deprecated: since 7.85.0. Use CURLOPT_PROTOCOLS_STR [-Werror=deprecated-declarations] happens when trying to build Torizon OS 6 (kirkstone) on a PC with Debian 12.

this is the outcome of using Debian 12 (bookworm) + building kirkstone + using curl 8.6.0 in meta-toradex-torizon. Curl added the deprecation warnings somewhere after 7.82 (which is the default in OE kirkstone), and gcc 12 (and newer) make the building fail – and since bookworm has gcc 12, the problem surfaces.

Workaround: Either use a container such as explained on Build Torizon OS from Source With Yocto Project/OpenEmbedded or a supported distro on your PC as listed on Yocto Manual - Supported Distributions.

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: When running U-Boot fw-utils commands as fw_setenv or fw_printenv as the torizon user, the command fails with the error message "Configuration file wrong or corrupted".

Workaround: Either run the commands with sudo, or switch to the root user before running the commands.

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: Reading the U-Boot environment early in the boot stage with the “fw_printenv“ command may fail due to a missing symlink to “/dev/emmc-boot0“, which is created from a udev rule. It may happen, for example, from a Greenboot check script as documented on Update Checks and Rollbacks.

Workaround: Either wait for the symlink to be created before running “fw_printenv“, or if you need to use the command in the early boot stages, change the fw-utils configuration to use the eMMC device directly instead of the symlink.

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 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.