Is OTA update from 35.4 to 35.5 possible for the Orin Nano?

Issue Overview

The discussion revolves around the possibility of performing an Over-The-Air (OTA) update from version 35.4 to 35.5 on the Nvidia Jetson Orin Nano. Users have reported conflicting information regarding the support for OTA updates, specifically whether it is applicable to the Orin Nano or limited to other models like the Jetson Xavier or AGX.

Symptoms and Errors

• Users are uncertain if OTA updates are feasible for their specific configurations.
• Confusion arises regarding the necessary settings, such as disk encryption and root filesystem redundancy.

Context

This issue typically occurs during the update process, particularly when users attempt to transition from version 35.4 to 35.5 while using either the development kit or custom boards.

Hardware and Software Specifications

• Hardware: Orin Nano Devkit with disk encryption and root filesystem redundancy enabled.
• Software: Users are operating on JetPack versions around 35.x.

Frequency and Impact

The issue appears to be common among users attempting OTA updates, leading to frustration and potential downtime in development projects.

Possible Causes

1. Hardware Incompatibilities: Some configurations may not support OTA updates due to specific hardware setups.

   • Explanation: Certain features like disk encryption or root filesystem redundancy must be correctly configured for OTA updates to work.

2. Software Bugs or Conflicts: There may be inconsistencies in the software documentation regarding OTA support.

   • Explanation: Documentation might not clearly state which versions or configurations are supported.

3. Configuration Errors: Incorrect settings related to disk encryption or redundancy could prevent successful updates.

   • Explanation: Users must ensure that both features are enabled prior to attempting an update.

4. Driver Issues: Potential driver incompatibilities could hinder the update process.

   • Explanation: Outdated or improperly configured drivers might not support new software features.

5. User Errors: Misunderstandings about required settings could lead to failed updates.

   • Explanation: Users may overlook essential configurations that enable OTA functionality.

Troubleshooting Steps, Solutions & Fixes

1. Confirm Configuration Settings:

   • Ensure that both disk encryption and root filesystem redundancy (A/B) are enabled before attempting the update.
   • Command to check settings:

     sudo cat /boot/extlinux/extlinux.conf | grep "disk-encryption"
     sudo cat /boot/extlinux/extlinux.conf | grep "rootfs"
     

2. Performing the OTA Update:

   • If configurations are confirmed, proceed with the image-based OTA update:

     sudo apt-get update && sudo apt-get upgrade
     

3. Check for Secure Boot Compatibility:

   • Verify if Secure Boot is enabled and compatible with your setup:
     • Secure Boot is supported, but UEFI Secure Boot is not.
     • Ensure you can specify PKC/SBK keys during OTA package generation.

4. Testing Different Configurations:

   • If issues persist, consider testing with different hardware configurations or revert back to version 35.4 if necessary.

5. Referencing Documentation:

   • Review Nvidia’s official documentation for any updates regarding OTA support for the Orin Nano:
     • Look for specific release notes associated with JetPack versions.

6. Best Practices:

   • Regularly back up your system before performing updates.
   • Keep your JetPack SDK updated to avoid compatibility issues.

7. Unresolved Aspects:

   • Further clarification may be needed on specific configurations that allow for successful OTA updates across different setups.

By following these structured troubleshooting steps, users can effectively diagnose and resolve issues related to OTA updates on their Nvidia Jetson Orin Nano devices.