Skip to main content
Version: Torizon OS 7.x.y

Torizon OS Upgrade Notes

Introduction​

In this article, you will learn about the technical details of Torizon OS releases which impact customers when upgrading.

Torizon OS releases are maintained according to our Embedded Linux Support Strategy.

Release Details and Upgrade Notes​

In this section, you find notes on the impact of updating to a newer Torizon OS release.

Torizon OS 7.0.0​

Torizon OS 7.0.0 is the first quarterly release from the Torizon OS 7 series.

  • All users of the early Torizon OS 7 monthly pre-releases should update to this release until it is superseded. All previous monthly pre-releases will not be patched - maintenance releases are based on the latest quarterly.

  • All users of the Torizon OS 6 series should upgrade to Torizon OS 7. There are available instructions for Upgrading from Torizon OS 6.x to Torizon OS 7.x.

  • If you are still on TorizonCore 5: First, upgrade from TorizonCore 5 to Torizon OS 6, then, Upgrade to Torizon OS 7.x, as direct upgrade path is not supported.

  • The aktualizr-data-proxy used in Torizon 6.4.0 and older for Device Monitoring has been disabled in Torizon 7:

    • If you have a custom /etc/fluent-bit/fluent-bit.conf file, make sure to update the [OUTPUT] section:
    # From
    [OUTPUT]
    name tcp
    port 8850
    format json_lines
    match *
    ---
    # To
    [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
    • If you didn't customize the file /etc/fluent-bit/fluent-bit.conf, it will be automatically updated and you don't need to take any action.
  • Wi-Fi Access Point (AP) configuration via NetworkManager has been disabled due to issues between NetworkManager and the AP interface. You must use hostapd moving forward. Learn how to use hostapd on Networking with Torizon OS.

  • The userspace utility to manage the CPU frequency has been replaced from cpufrequtils to cpupower. Learn how to use cpupower on CPU Frequency and DVFS (Linux).

  • In the OS, neofetch has been replaced with fastfetch. In the Debian Containers for Torizon, it is scheduled to be replaced as well. As this is a development utility, no real impact is expected with this change.

Read the Torizon OS 7.0.0 news for a complete list of updates and highlights for this release.

Torizon OS 6.8.0​

Torizon OS 6.8.0 is the last quarterly release of the Torizon OS 6 series and has new features.

  • All users of the Torizon OS 6 series should update to this release until it is superseded. All previous Torizon OS 6.X releases will not be patched - maintenance releases are based on the latest quarterly.

Read the Torizon OS 6.8.0 release news for a complete list of updates and highlights for this release.

Torizon OS 6.7.0​

Torizon OS 6.7.0 is a quarterly release from the Torizon OS 6 series.

Read the Torizon OS 6.7.0 release news for a complete list of updates and highlights for this release.

Torizon OS 6.6.1​

Torizon OS 6.6.1 is a quarterly release from the Torizon OS 6 series.

Read the Torizon OS 6.6.1 release news for a complete list of updates and highlights for this release.

Torizon OS 6.5.0​

Torizon OS 6.5.0 is a quarterly release from the Torizon OS 6 series.

  • All users of the Torizon OS 6 series should update to this release until it is superseded. All previous Torizon OS 6.X (formerly named TorizonCore) releases will not be patched - maintenance releases are based on the latest quarterly.
  • If your product has low or unstable connection to the internet and you perform remote updates, consider tweaking the default configuration to make your updates more robust, as documented on Configuring Options for Low-Bandwidth Connections.
  • Device monitoring data buffering is now available. The default values are a reference implementation. If you use device monitoring and your device has intermittent connection to the internet, it is recommended that you adjust the parameters to your use case constraints, as documented on Data Buffering.
  • eMMC lifespan has been added to the default device monitoring metrics. If you use device monitoring, review whether it makes sense to follow the default or remove this metric.
  • .NET 8 containers for Torizon are released, following the .NET 8 release announcement:
  • A Qt 6 template is available for the VS Code IDE Extension for Torizon, providing an improved user experience that is built on top of the Debian Containers provided in the previous quarterly 6.4.0 release.

Read the Torizon OS 6.5.0 release news for a complete list of updates and highlights for this release.

Torizon OS 6.4.0​

Torizon OS 6.4.0 is a quarterly release from the Torizon OS 6 series.

  • All users of the Torizon OS 6 series should update to this release until it is superseded. All previous Torizon OS 6.X (formerly named TorizonCore) releases will not be patched - maintenance releases are based on the latest quarterly.
  • Qt 6 Debian Containers for Torizon are available and support hardware acceleration. Updates to the related documentation and the VSCode Torizon template should happen after this release. Before this update, projects based on this template will rely on the software-rendered implementation.
    • If your use case relies on hardware acceleration and you can't wait for the template and docs update, you may want to try the new containers by replacing your project Dockerfile's FROM statement to use one of the following: torizon/qt6-wayland for SoMs based on NXP i.MX 6/6ULL/7 or; torizon/qt6-wayland-vivante for SoMs based on NXP i.MX 8/8X/8M Mini/8M Plus.
    • For testing purposes, you can run examples with the torizon/qt6-wayland-examples-vivante container. The torizon/qt6-wayland-examples container is not available because the Qt 6 examples package is not available in the Debian feed.
    • Python bindings are not yet easy-to-use. As a hint, you may use PyQt6 which already has Debian packages available, or PySide6 which doesn't have the packages available but on the other hand has a license that may better suit your product. See a comparison on PyQt6 vs PySide6.
  • The Debian Containers for Torizon were rebuilt against the Debian 12.1 point release. You are encouraged to update the Debian Containers used in your project to our latest containers release.

Read the Torizon OS 6.4.0 release news for a complete list of updates and highlights for this release.

TorizonCore 6.3.0​

TorizonCore 6.3.0 is a quarterly release from the TorizonCore 6 series.

Read the TorizonCore 6.3.0 release news for a complete list of updates and highlights for this release.

TorizonCore 6.2.0​

TorizonCore 6.2.0 is a quarterly release from the TorizonCore 6 series.

  • All users of the TorizonCore 6 series should update to this release until it is superseded. All previous TorizonCore 6.X releases will not be patched - maintenance releases are based on the latest quarterly.
  • All users of the TorizonCore 5 series can upgrade to TorizonCore 6. Upgrade instructions are available on Upgrading from TorizonCore 5.x to TorizonCore 6.x.
  • The torizon/debian-shell container has been deprecated in TorizonCore 6. The impact should be minimal since the torizon/debian container is an easy-to-migrate replacement, as can be seen in the List of Container Images for Torizon. To migrate, check the packages installed on torizon/debian-shell and install the ones you rely on to your container based on torizon/debian.

Read the TorizonCore 6.2.0 release news for a complete list of updates and highlights for this release.

TorizonCore 6.1.0​

TorizonCore 6.1.0 is the first quarterly release from the TorizonCore 6 series.

  • All users of the TorizonCore 6 series should update to this release until it is superseded. All previous monthly pre-releases will not be patched - maintenance releases are based on the latest quarterly.
  • All users of the TorizonCore 5 series should upgrade to TorizonCore 6. There are available instructions for Upgrading from TorizonCore 5.x to TorizonCore 6.x.
  • Colibri SoMs: the spidev overlay has been disabled by default, due to a conflict with the SPI-to-CAN transceiver on the Colibri Evaluation Board. If you use spidev, you must enable the corresponding overlay. Read the issue TOR-2746 in our issue tracker to learn more.
  • The ecosystem around TorizonCore 6 has limitations. If you have experience with TorizonCore 5, read the release news below to learn what are the limitations.
  • You should not rely on the debian-shell container in TorizonCore 6, as we have deprecated it. The impact should be minimal since the debian container is an easy-to-migrate replacement, as you can check in our List of Container Images for Torizon. To migrate, check the packages installed on debian-shell and install the ones you rely on into your container based on debian.

Read the TorizonCore 6.1.0 news and the TorizonCore 6.0.0-devel-202210 news for a complete list of updates and highlights for this release, as well as why 6.0.0 was not a quarterly release.

TorizonCore 5.7.2​

TorizonCore 5.7.2 is a maintenance release of the 5 series which supersedes 5.7.0.

Read the TorizonCore 5.7.2 release news for a complete list of updates and highlights.

TorizonCore 5.7.0​

TorizonCore 5.7.0 is the Latest Quarterly Release of the 5 series.

  • All users of previous versions of the 5 series should update to this version until it is superseded.
  • According to our support strategy, all previous quarterly releases will not be patched - maintenance releases are based on the latest quarterly.
  • The TorizonCore team only tests updating from the immediately previous TorizonCore release. In this case, from 5.6.0 to 5.7.0. If you plan to update from any other previous release, you must validate it, since it is not a supported scenario.

Read the TorizonCore 5.7.0 news for a complete list of updates and highlights.

TorizonCore 5.6.0 and older​

Upgrade notes were released starting from TorizonCore 5.7.0 onward. For older releases, please read the corresponding TorizonCore news on toradex.com:



Send Feedback!