Inquiry About OTA Upgrade Path from JetPack 5.1.2 (Customized) to JetPack 6.2

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
1

We are currently facing an issue regarding the upgrade path of our customized platform.

Our product is based on Jetson Orin Nano 8GB and currently runs a customized BSP built on JetPack 5.1.2. Recently, our customer has requested an upgrade to JetPack 6.2. Since the customer has performed additional application-level development on the device, we are required to perform the upgrade via OTA.

Based on our current understanding, the upgrade path must first move from JetPack 5.1.2 to JetPack 5.1.3, and then proceed to JetPack 6.2 via OTA.

At the moment, we have customized BSP versions for:

  • JetPack 5.1.2

  • JetPack 6.2

However, we are encountering issues during the 5.1.2 → 5.1.3 upgrade step.

Our questions are as follows:

  1. Is it possible to upgrade from our customized JetPack 5.1.2 to the official JetPack 5.1.3 first, and then upgrade to our customized JetPack 6.2?

  2. If mixing customized and official BSP versions is not recommended, what would be the suggested or supported upgrade path in this scenario?

We would greatly appreciate your guidance on the correct and supported upgrade procedure.

Thank you for your assistance.

3

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

Based on the provided context, I will attempt to address the questions and concerns raised.

Firstly, it’s essential to understand the supported upgrade paths for Jetson Linux. According to the context, image-based OTA updates support updates between versions with different partition layouts that require layout changes during the update. Specifically, it mentions that updates from version 35.5.0 to version 36.4.0 are supported.

Given that your product is based on Jetson Orin Nano 8GB and currently runs a customized BSP built on JetPack 5.1.2, and you need to upgrade to JetPack 6.2, it’s crucial to follow a supported upgrade path.

To answer your questions:

  1. Is it possible to upgrade from your customized JetPack 5.1.2 to the official JetPack 5.1.3 first and then upgrade to your customized JetPack 6.2?

While it’s technically possible to upgrade from a customized BSP to an official BSP, it’s not recommended. Mixing customized and official BSP versions can lead to compatibility issues, and it’s not a supported upgrade path.

  1. If mixing customized and official BSP versions is not recommended, what would be the suggested or supported upgrade path in this scenario?

The recommended approach would be to create a customized BSP for JetPack 5.1.3, which is compatible with your existing customized BSP for JetPack 5.1.2. Once you have a customized BSP for JetPack 5.1.3, you can then upgrade to your customized BSP for JetPack 6.2.

To achieve this, you can follow these steps:

a. Create a customized BSP for JetPack 5.1.3 by modifying the official BSP to match your existing customized BSP for JetPack 5.1.2.

b. Upgrade your device from the customized BSP for JetPack 5.1.2 to the customized BSP for JetPack 5.1.3 using the image-based OTA update mechanism.

c. Once the upgrade to JetPack 5.1.3 is successful, you can then upgrade to your customized BSP for JetPack 6.2 using the image-based OTA update mechanism.

By following this approach, you can ensure a smooth and supported upgrade path for your customized platform.

In summary, while it’s technically possible to upgrade from a customized BSP to an official BSP, it’s not recommended. Instead, create a customized BSP for the intermediate version (JetPack 5.1.3) and then upgrade to the desired version (JetPack 6.2). This approach ensures a supported and compatible upgrade path for your customized platform.

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

5

hello denma0513,

please see-also developer guide, Updating Jetson Linux with Image-Based Over-the-Air Update.
since you’re based-on JP-5.1.2/r35.4.1, you should first upgrade to JP-5.1.3/r35.5.0, and then from r35.5.0 to do OTA update moving forward to the JP-6 public release versions.

it’s suggest to update l4t_generate_ota_package.sh and ota_board_specs.conf for customize board to create OTA payloads.
see-also similar forum topics for reference, Topic 332980, Topic 349289.

7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.