AGX Orin EOL Risk and Upgrade Path

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
1

Hello everyone!

We are considering designing a new product based on the NVIDIA Jetson AGX Orin.

From what I understand, the industrial version of AGX Orin has an expected EOL around 2032–2033. If we start development toward the end of this year, with an estimated time-to-market of 2–3 years, that would leave us with roughly 2–4 years of product lifetime before EOL. Our product life 10-15 years.

This raises a few concerns:

  1. Should this relatively short remaining lifecycle be a concern for a new design?

  2. Does NVIDIA typically provide a clear upgrade path or pin-compatible successor that allows relatively smooth migration when a module reaches EOL?

  3. Is there already any information about a successor to AGX Orin?

  4. Has anyone here migrated a project from one Jetson module to another (for example, from AGX Xavier to AGX Orin)? If so:

    • How significant was the effort?

    • What were the main challenges?

  5. What design practices would you recommend to mitigate risks related to future module replacement (e.g., carrier board design, abstraction layers, BSP considerations)?

Any insights or real-world experience would be greatly appreciated.

Cheers!

2

*** Please note that this reply is generated by LLM automatically ***

The concerns you’ve raised about the relatively short remaining lifecycle of the NVIDIA Jetson AGX Orin module are valid, especially considering your product’s expected lifespan of 10-15 years. I’ll address your questions and provide insights to help mitigate risks related to future module replacement.

Concerns about the remaining lifecycle:

While 10 years might seem like a long time, it’s essential to consider the potential risks and challenges associated with a module reaching its End-of-Life (EOL). As you’ve mentioned, the industrial version of AGX Orin has an expected EOL around 2032-2033, which would leave you with roughly 2-4 years of product lifetime before EOL. This relatively short remaining lifecycle could be a concern, especially if you’re planning a long-term product.

Upgrade path and pin-compatible successor:

NVIDIA typically provides a clear upgrade path or pin-compatible successor to allow for relatively smooth migration when a module reaches EOL. However, the specifics of the upgrade path or successor are usually not publicly disclosed until closer to the EOL date.

In the past, NVIDIA has provided upgrade paths for their Jetson modules, such as from Jetson TX1 to Jetson TX2, and from Jetson Xavier to Jetson Orin. These upgrades often involve changes to the carrier board design, BSP, and software. While the effort required for migration can vary, it’s essential to design your product with flexibility and modularity in mind to minimize the impact of future changes.

Successor to AGX Orin:

There is no publicly available information about a successor to AGX Orin at this time. NVIDIA typically announces new products and modules through their official channels, such as press releases, developer blogs, or conferences.

Migration from one Jetson module to another:

Several developers have migrated projects from one Jetson module to another, such as from AGX Xavier to AGX Orin. The effort required for migration can vary depending on the specific use case, software, and hardware changes.

In general, the main challenges when migrating from one Jetson module to another include:

  1. Carrier board design changes: The new module may require changes to the carrier board design, such as updates to the power delivery, memory, or peripherals.
  2. BSP and software updates: The new module may require updates to the BSP, kernel, or software frameworks, which can impact the overall system performance and functionality.
  3. Pin compatibility: The new module may not be pin-compatible with the previous one, requiring changes to the carrier board design or the use of adapters.

To mitigate these risks, it’s essential to design your product with flexibility and modularity in mind. Here are some design practices to consider:

  1. Carrier board design: Design your carrier board with flexibility in mind, using modular components and connectors to facilitate future upgrades or changes.
  2. Abstraction layers: Use abstraction layers in your software to decouple the application logic from the underlying hardware. This can help minimize the impact of changes to the module or BSP.
  3. BSP considerations: Consider using a BSP that provides a high degree of flexibility and customization, such as the NVIDIA Jetson Linux BSP.
  4. Modular design: Design your system with modularity in mind, using separate modules or components for different functions. This can help facilitate future upgrades or changes.
  5. Future-proofing: Consider future-proofing your design by using components or technologies that are likely to remain relevant in the future.

In summary, while the relatively short remaining lifecycle of the NVIDIA Jetson AGX Orin module is a concern, it’s essential to design your product with flexibility and modularity in mind to minimize the impact of future changes. By following the design practices outlined above, you can help mitigate risks related to future module replacement and ensure a smoother migration path for your product.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

1 Like
4

You can refer to Jetson FAQ | NVIDIA Developer, also can find the Interface Comparison and Migration Application Note from Jetson Download Center | NVIDIA Developer as referebce to upgrad the current module to a newer one.