Skip to main content

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 Toradex supported 32-bit i.MX-based SoMs (that is, NXP i.MX 6, i.MX 6ULL, and i.MX 7 based modules) come to life with the mainline/upstream Linux kernel, for example, mainline kernel v6.0 for BSP 6.0.

Downstream-Based​

Newly introduced NXP-based modules use the NXP downstream BSP when required to support their feature set. Some of Verdin SoMs based on NXP SoCs (Verdin iMX8M Mini and Verdin iMX8M Plus as example) also have upstream-based BSP variants as an alternative to the downstream-based builds.

The TI-based modules use a TI downstream-based kernel, with support available on versions 6.4 and later of the BSP for AM623 and AM625 and on 7.0 and later for AM69/TDA4.

Check the specific versions of U-Boot and Linux Kernel in the Release Matrix Article.

For more information, see the blog post 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 the Toradex Linux offerings: Yocto Project and Linux Kernel.

Check the lifecycle of the Toradex BSP Layers for Yocto in the following table. It does not define the lifecycle dates or support status of Torizon OS 8.

VersionStateInitial Release DateProjected EOLExtended EOLRelease Periodicity
BSP 8Coming SoonNovember 20262030Contact usMonthly
BSP 7ActiveOctober 20242028Contact usQuarterly
BSP 6MaintenanceOctober 20222026Contact usNo Releases
BSP 5EOLOctober 20202024Contact usNo Releases
BSP 3EOLJune 20192023Contact usNo Releases
BSP 2.8EOLDecember 20172021Contact usNo Releases

During a 3-state lifecycle - active, maintenance and EOL (End-of-Life) - Toradex delivers a series of releases.

For BSP 8, Toradex Embedded Linux release follows a simplified sequential versioning scheme. Except for BSP 8, 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 following graphic demonstrates how Toradex transitions between states. It does not represent a commitment to dates or future software releases.

Embedded Linux Lifecycle

Active​

This is when Toradex develops the most up-to-date software releases - the recommended ones to use. During the active state, Toradex delivers:

  • Production releases, meant to be used in production. The BSP 8 follows monthly production release cadence. For other BSP versions and Torizon OS, production releases have quarterly cadence.
  • Pre-releases builds 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, Toradex delivers 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.

End-of-Life (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. This means that fixes and security patches are delivered through subsequent maintenance or regular production releases within the same major version, with no breaking changes expected.

Debian Containers Support​

Toradex maintains Debian Containers for Torizon as application base images for Torizon OS. Each Torizon major version is paired with a specific Debian stable release; a change to the Debian major release occurs only with a new Torizon major release.

Support for each container major version ends at the earlier of the corresponding Torizon EOL or the end of security support for the paired Debian release, including Debian Long Term Support (LTS). Debian package security fixes depend on upstream availability and support coverage.

Application maintainers are responsible for incorporating available updates into their container images and assessing CVE applicability to their products.

To check which Debian release each Torizon OS major version uses, see Debian Release Mapping. For security update procedures and CVE guidance, see Support and Security Updates.

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 the Toradex issue tracker for each software. Also, Toradex highly recommends 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​

Monthly Releases (For BSP 8)​

  • Typical Content: latest feature set, bug fixes, and security fixes
  • Release Cycle: during active state, typically at the start of each month
  • Maintenance Duration: 1 month after the release. During this period, critical fixes can be delivered by bringing forward the next production release, which advances the minor version (for example, 8.2 to 8.3). There are no separate patch versions.

Quarterly Releases (For Torizon and BSP 7 and earlier)​

  • Typical Content: latest feature set, bug fixes, 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, Toradex 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: until the next regular release. During this period, Toradex can deliver critical fixes through patch releases.

Pre-Releases​

Engineering Pre-Releases​

  • Typical Content: early silicon enablement, upstream BSP integrations, experimental features, and initial support for new kernels and hardware accelerators
  • Release Cycle: irregular, coupled with upstream SoC vendor updates and development milestones
  • Maintenance Duration: short-term availability with no guaranteed maintenance, updates, or continuity1

Nightly 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 Pre-Releases​

This release type does not apply to BSP 8, which provides monthly production releases during active development.

  • Typical Content: new features and bug fixes
  • Release Cycle: typically every month
  • Maintenance Duration: not maintained. For patches, use nightly builds

Footnotes​

  1. Engineering pre-releases follow a short-term, non-supported lifecycle and are provided as-is, with no guarantee of continuous updates, maintenance, or security fixes. Breaking changes across kernel, BSP layers, and userspace are expected, and forward compatibility or upgrade paths are not guaranteed. Validation, qualification, and certification remain the customer’s responsibility. Production systems should use Toradex-supported BSP releases. ↩

Send Feedback!