What Problem this Solves
What Problem this Solves
The Jetson Xavier platforms remain part of active products that still need maintenance, security attention, validation, and customer support.
For these products, the problem is not that newer hardware exists. The problem is that an immediate platform migration can be expensive, risky, and difficult to justify while the current AGX Xavier or Xavier NX-based product is still working in the field.
A hardware transition can affect much more than the compute module. It may require driver changes, device tree updates, userspace adaptation, regression testing, manufacturing updates, and customer requalification. In regulated or long-lifecycle markets, those activities can be larger than the kernel work itself.
Product Lifecycle Challenge
Many products based on AGX Xavier or Xavier NX were built around a specific hardware and software setup.
Over time, this setup becomes part of the product. It is reflected in test procedures, release notes, factory images, customer documentation, support training, and validation records.
When official support for the original platform reaches End-of-Life (EoL), teams usually have three options:
- Continue using the existing software baseline, even as maintenance risks increase.
- Migrate the product to a newer platform.
- Maintain the existing Xavier platform through a controlled kernel support path.
This project focuses on the third option for Xavier-based products.
Migration Cost
Moving to a newer Jetson platform can be the right long-term decision, but it is not always a quick alternative to maintaining Xavier.
A migration may require:
- Hardware redesign
- BSP and driver updates
- Device tree updates
- Userspace integration
- Product regression testing
- Certification or requalification work
- Updated support and deployment documentation
For a product that is already deployed or generating revenue, these activities may cost more than the hardware itself.
Maintaining Xavier can give teams more time to plan and evaluate a migration without immediately replacing the current platform.
Maintenance Need
A maintained kernel baseline gives teams a documented way to support existing Xavier products.
It provides a base that can be built, validated, and documented. This is more reliable than depending on local patches or one-time fixes that only one engineer understands.
The goal is not to make Xavier behave like a newer Jetson platform. It is to provide a practical maintenance foundation for products that already depend on Xavier.
Product Value
The main benefit is continuity.
A maintained Xavier platform can help customers continue supporting an existing product while reducing dependence on an unmanaged software baseline. It gives engineering and product teams a clearer long-term support path and more time to plan a future hardware transition.
This approach is most relevant when the product is already deployed, the Xavier hardware is still needed, and the software requires a support path that can be explained, maintained, and validated.