TorizonCore Upgrade Notes
Introduction
In this article, you will learn about the technical details of TorizonCore releases which impact customers when upgrading.
TorizonCore 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 TorizonCore release.
TorizonCore 6.3.0
TorizonCore 6.3.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 are not maintained.
- An alternative method for configuring Wi-Fi Access Point (AP) and hotspot has been introduced due to a bug that prevents NetworkManager instructions to work. Learn how to apply it on Networking with TorizonCore - Wi-Fi access point mode - Method 2: Hostapd.
- Debian Containers for Torizon based on Debian Bookworm are available with the major tag
3. Even though the previous Debian Bullseye containers with the major tag2are expected to work, only the newer ones are supported in TorizonCore 6. Read the article TorizonCore Containers Tags and Versioning for more details on how the compatibility between containers and TorizonCore is defined. Since this is the first release of the Debian Bookworm containers, all of the points below are considered breaking changes between TorizonCore 5 and 6:- A breaking change has been introduced on how to start the Weston and Browser containers. The up-to-date commands are available on Debian Containers for Torizon - Debian With Weston Wayland Compositor, Web Browser / Kiosk Mode with TorizonCore - Running Chromium and Web Browser / Kiosk Mode with TorizonCore - Running Cog.
- The GitHub repository torizon-containers supersedes and unifies all the content from debian-cross-toolchains, debian-docker-images, debian-dotnet-development-images, and rt-validation. With a regular workflow, you will build your own docker images on top of our pre-built images provided on Docker Hub, and thus you won't be affected by this change. Nevertheless, if you have chosen to rebuild our images from source, you must use the new repository from now on.
- GLX support on Xwayland and gst-plugins-base1.0 for i.MX 8/8X/8M Mini/8M Plus has been removed from our Debian packages, as it was done by NXP in their forks of these packages. Glamor support for hardware-accelerated 2D rendering is available and you must plan to switch to using it - though due to the bug xwayland: glamor support broken on iMX8 it is currently falling back to software rendering.
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 are not maintained.
- 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-shellcontainer has been deprecated in TorizonCore 6. The impact should be minimal since thetorizon/debiancontainer 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 ontorizon/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 are not maintained.
- 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-shellcontainer in TorizonCore 6, as we have deprecated it. The impact should be minimal since thedebiancontainer 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 ondebian.
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.
- All users of previous versions of the 5 series should update to this version until it is superseded.
- This release enables bootloader updates and allows users to upgrade from TorizonCore 5 to 6, by using it as a bridge. Learn more on Bootloader updates article.
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 LTS 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 are not maintained anymore.
- 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: