Introduction
Introduction
Jetson AGX Xavier continue to power products deployed across industrial automation, robotics, medical systems, transportation, defense, and edge AI applications.
Many of these products are designed for operational lifecycles that can significantly exceed the support lifecycle of the underlying computing platform. Industrial, medical, and transportation systems often remain deployed and maintained for a decade or more, creating challenges when the hardware vendor's support window comes to an end.
As a result, engineering teams often face a different challenge than simply adopting the next hardware generation: maintaining existing deployments while continuing to meet customer, security, and support commitments.
This challenge becomes increasingly relevant as Xavier approaches the later stages of its product lifecycle. NVIDIA has already communicated lifecycle milestones and support timelines for Xavier based platforms, making long term maintenance planning an important consideration for organizations that continue to rely on these devices.
For reference, NVIDIA lifecycle announcements can be found here:
This project documents a practical maintenance path for Xavier based products using a maintained kernel baseline derived from the Civil Infrastructure Platform (CIP) project together with the integration, validation, and documentation work required to keep the platform supportable over time.
Rather than focusing on future hardware migrations, the material in this wiki focuses on helping teams understand how existing Xavier deployments can remain maintainable, secure, and operational throughout the remaining life of the product.
What This Wiki Covers
This wiki is organized around the questions that engineering, product, and business teams commonly ask when evaluating a long term maintenance strategy for Xavier.
Topics covered include:
- The product lifecycle challenges that motivate this work
- Situations where a maintained Xavier platform makes sense
- The maintenance approach provided by RidgeRun
- Platform capabilities and subsystem status
- Validation activities and support evidence
- Build, installation, and integration guidance
- Known limitations and support boundaries
The objective is to provide enough context to understand the maintenance strategy before moving into the implementation details.
Suggested Reading Path
Readers approaching the project from a product, program management, or business perspective may want to start with:
Readers interested in the technical scope of the solution can continue with:
The remaining sections provide the technical material behind the project, including subsystem status, validation results, build procedures, integration notes, and maintenance boundaries.