Tegra Migration Guide
This guide helps customers using end-of-life (EOL) Tegra products migrate to recommended hardware and software solutions for their products.
Toradex has a lot of information, tools, and other resources to help with the migration, including future-proof Hardware and Software solutions, our Partner Network, support from our Community, direct contact with Sales and Application Engineers, and a constantly-updated Developer Center.
The following SoMs are covered under this guide:
- Colibri T20
PCN Document: PCN (EOL) Colibri T20 - 2022-12-20
- Colibri T30
PCN Document: PCN (EOL) Colibri T30 - 2022-12-15
- Apalis T30
PCN Document: PCN (EOL) Apalis T30 - 2022-12-16
This guide will be constantly upgraded.
With the EOL of Toradex Tegra products, you will have to:
- Select a replacement module
- Upgrade or migrate the Operating System
- Possibly upgrade or migrate the software stack of your application to work with the selected OS
Toradex provides valuable resources to help you in each step of the migration process.
Operating System Selection
Please keep in mind that this decision may limit your replacement module options.
If you are using Toradex BSP based custom-built Embedded Linux, migration will involve upgrading to the latest BSP version
If you are using Windows Embedded Compact, there are several reasons for migrating to another OSResources
See the Operating System section for detailed information.
Toradex SoM Selection
If continuing to use Windows Embedded Compact is your preferred choice, then you will be limited to i.MX6-based SoMs. Options within the SoM family you are using - Colibri or Apalis - are available. Carefully evaluate the performance constraints to ensure this decision is viable from a performance standpoint
If you decide to use Torizon or Toradex BSP based Custom-built Embedded Linux, then you will also be able to use i.MX8-based SoMsResources
See the Replacement Product section for detailed product comparison.
See the Performance Comparison section to check the performance across different modules.
See the Hardware Compatibility section to learn how to check compatibility.
With a replacement SoM chosen, you may need to check and/or update your carrier board design.
- If you are replacing a current Tegra-based SoM with a module within the same family, you can leverage its pin-compatibility
- When migrating to the Verdin Family, or if the chosen SoM requires changes to your carrier board, you will benefit from our carrier board design resources
See the Hardware Design Update section for detailed information.
Software Stack Update
When migrating to a Linux-based OS, the software stack used to build and run your application will probably require some changes. It is possible to reuse code from your current application. For that reason, the software stack you are currently using will impact your choice of a new software stack. Aspects such as GUI interfaces and Real-time requirements will also play a role in this decision.
This decision is directly impacted by your SoM choice, as it should provide enough hardware resources to support the software stack and ensure good performanceResources
See the Software Stack in Linux section for detailed information.
If you need help in the migration of your software or hardware, we have a great Partner Network.
They can help you with Operating Systems customization, application development and porting. They have great experience migrating applications from WEC to Linux and can save you time and resources.
They can also help you with Carrier Board Design, Production, and configuration of your Operating System to match your custom hardware needs.
Contact Us so we can discuss your case and connect you with a suitable partner.