Embedded Linux Support Strategy
Introduction
This article presents information about the Embedded Linux Support on Toradex SoMs. It covers the lifecycle, releases, and software alerts adopted by Toradex. It is valid for both Toradex's Torizon OS and Toradex BSP Layers and Reference Images for Yocto Project. To learn more about them, check the Embedded Linux Options for Toradex SoMs article.
For BSP 3.X and 2.X please see Toradex Software Versioning Convention (Legacy).
Upstream Strategy
Starting with BSP 6.0, all our supported 32-bit i.MX-based SoMs (i.e. NXP i.MX6, i.MX6 ULL, and i.MX7 based modules) come to life with the mainline/upstream Linux kernel, for example, mainline kernel v6.0 for BSP 6.0.
The i.MX 8, i.MX 8X, i.MX 8M Mini and i.MX 8M Plus based modules use an NXP downstream-based kernel even for versions 6.0 and later of the BSP. Some of Verdin SoMs based on NXP SoCs (Verdin iMX8M Mini and Verdin iMX8M Plus) also have upstream-based BSP builds as an alternative to the downstream-based builds. The upstream build should be preferred if the supported features match your requirements. Torizon OS is only built for downstream-based BSPs. The TI AM623 and AM625 based modules use a TI downstream-based kernel, with support available on versions 6.4 and later of the BSP.
Check the specific versions of U-Boot and Linux Kernel in the Release Matrix Article.
For more information, please check our Blog: Upstream First - Toradex Mainline Kernel Support is a Reality.
Embedded Linux Lifecycle and Releases
Toradex provides frequent releases for the Embedded Linux Options, including Torizon OS and BSP Layers for Yocto. The releases align with the lifecycle of key building blocks of our Linux offerings: Yocto Project and Linux Kernel.
Check the lifecycle of our BSP Layers for Yocto in the table below - Note that our Torizon OS is built on top of our BSP Layers and their support status are aligned:
| Version | State | Initial Release Date | Projected EOL | Extended EOL | Release Periodicity |
|---|---|---|---|---|---|
| Torizon/BSP 7 | Active | October 2024 | 2028 | Contact Us | Quarterly |
| Torizon/BSP 6 | Maintenance | October 2022 | 2026 | Contact Us | Quarterly |
| Torizon/BSP 5 | Maintenance | October 2020 | 2024 | Contact Us | As needed |
| BSP 3 | EOL | June 2019 | 2023 | Contact Us | No Releases |
| BSP 2.8 | EOL | December 2017 | 2021 | Contact Us | No Releases |
During a 3-state lifecycle - active, maintenance and EOL - we deliver a series of releases. The Toradex Embedded Linux release process follows the Major, Minor and Patch versioning scheme, known as semantic versioning. No breaking changes are supposed to happen between releases with the same major version number. The transition within the major version is expected to be low-effort and low-risk.
The graphic below demonstrates how we transition between states. It does not represent a commitment to dates or future software releases.
Active
This is when we develop the most up-to-date software releases - the default ones to use. During the active state, we deliver:
- Quarterly releases, meant to be used in production
- Monthly and Nightly pre-releases, meant for development and evaluation
Maintenance
While migrating to the latest version isn't feasible, you can continue using your current version as long as it's still in maintenance state. During the maintenance state, we deliver periodic Maintenance Releases, meant to be used in production. They provide security and bug fixes. The start of maintenance state is not fixed and depends on the maturity of the product and justified business needs.
- To ensure Long Term Availability, Toradex fully supports and validates the new hardware versions and does any necessary software backports to support their hardware changes, such as changes caused by components going end-of-life.
- Toradex provides updates for the software components. They consist of fixed versions of the U-Boot boot loader, Linux kernel and OpenEmbedded/Yocto Project components used on a specific Toradex release.
- Those updates are provided as long as the respective version of the component still receives updates. They are typically maintained for 2 - 3 years and are subject to each component's release plan.
- Toradex uses Longterm/Stable Linux kernels for its releases whenever possible. This ensures that Toradex releases receive kernel updates for an extended period.
EOL
After the EOL date, no new releases are expected. It is recommended to upgrade to a version in active state. In case that's not possible, Toradex offers extended support period as a service. Contact Us to discuss your case.
Long-Term Support (LTS)
All the releases of Toradex Embedded Linux have Long-Term Support until they reach EOL.
Supported Modules
Check the Release Matrix to learn which modules are supported by each release.
Live Updates on Software
You can learn the latest status and work progress on our issue tracker for each software. Also, we highly recommend that you sign up for updates on each detailed software page:
Critical software issues get announced via customer information notification emails to customers who purchased affected products.
Release Types
Production Releases
Quarterly Embedded Releases
Typical Content: Latest feature set, bug and security fixes
Release Cycle: During active state, typically at the start of each Quarter, 4 times a year
Maintenance Duration: 3 Months after the release. During this period, we can deliver critical fixes through patch releases.
Maintenance Releases
Typical Content: Feature set of the latest release during active state, plus bug and security fixes
Release Cycle: Typically released during maintenance state, typically at the start of each Quarter, 4 times a year.
Maintenance Duration: 3 Months after the release. During this period, we can deliver critical fixes through patch releases.
Pre-releases
Nightly Embedded Pre-releases
Typical Content: Features and fixes, made that day
Release Cycle: On most nights, before midnight
Maintenance Duration: Not maintained as it is released on most days
Monthly Embedded Pre-releases
Typical Content: New Features and bug fixes
Release Cycle: Typically every month
Maintenance Duration: Not maintained. For patches, use nightly builds