OTA Update 36.3 Orin Nano with A/B and Disk Encryption enabled

Issue Overview

Users are encountering difficulties when attempting to perform an Over-the-Air (OTA) update on the Jetson Orin Nano Dev board, specifically while trying to push a custom root filesystem (rootfs) image. The issue arises during the deployment of the update package, leading to errors that hinder successful updates. The board is configured with A/B partitions and disk encryption, with Secure Boot enabled. The specific symptoms include failure during the execution of the nv_ota_start.sh script after preparing the OTA payload. The user has confirmed that their L4T version is 36.3 and has set the environment variables correctly, but still experiences issues. This problem appears to be consistent among users attempting similar updates, impacting their ability to utilize the device effectively.

Possible Causes

1. Hardware Incompatibilities or Defects: If there are issues with the custom board’s hardware, it may not support the OTA update process correctly.
2. Software Bugs or Conflicts: There could be bugs in the L4T version 36.3 or conflicts with other installed software that prevent the update from executing properly.
3. Configuration Errors: Incorrect settings in environment variables or command parameters may lead to failures in deploying the update.
4. Driver Issues: Outdated or incompatible drivers may affect the OTA process, especially if they are not aligned with the current L4T version.
5. Environmental Factors: Power supply issues or temperature fluctuations could impact the device’s performance during updates.
6. User Errors or Misconfigurations: Mistakes in following procedures or commands can lead to errors during the OTA update process.

Troubleshooting Steps, Solutions & Fixes

1. Verify L4T Version: Ensure that you are using L4T version 36.3 as intended for your update process. If upgrading from an earlier version (e.g., 35.4.1), first upgrade to 35.5.0 before proceeding to 36.3.

2. Check Environment Variables:

   • Confirm that BASE_BSP and TARGET_BSP are set correctly to point to the same L4T directory.
   • Use the following command to print current environment variables:

     echo $BASE_BSP
     echo $TARGET_BSP
     

3. Review OTA Package Generation Command:

   • Ensure that all parameters in your l4t_generate_ota_package.sh command are correct, particularly those related to encryption and partitioning:

     sudo -E ROOTFS_AB=1 ROOTFS_ENC=1 ./Linux_for_Tegra/tools/ota_tools/version_upgrade/l4t_generate_ota_package.sh -i sym2_t234.key -u rsa.pem -v sbk.key -r --external-device nvme0n1 -S 25GiB jetson-orin-nano-devkit R36-3
     

4. Deploy OTA Package Correctly:

   • Follow these steps carefully after copying the OTA payload:

     sudo mkdir -p /ota
     sudo mv /home/nvidia/ota_payload_package.tar.gz /ota/
     cd /ota
     sudo tar -xpf ota_payload_package.tar.gz
     
     sudo mkdir -p /home/nvidia/ota_work
     export WORKDIR=/home/nvidia/ota_work
     sudo tar -xpf /home/nvidia/ota_tools_R35.4.1_aarch64.tbz2 -C ota_work
     cd ota_work/Linux_for_Tegra/tools/ota_tools/version_upgrade
     
     sudo ./nv_ota_start.sh /ota/ota_payload_package.tar.gz
     

5. Logs and Error Messages:

   • If errors occur during execution, capture logs for further analysis:

     dmesg | tail -n 50
     

   • Review error messages for clues about what might be going wrong.

6. Testing with Different Configurations:

   • If possible, test with a different Jetson Orin Nano board or revert to a previous known working configuration.
   • Consider using a non-encrypted rootfs image for testing purposes.

7. Update Drivers and Firmware:

   • Ensure all drivers and firmware are up-to-date according to NVIDIA’s documentation for Jetson devices.

8. Consult Documentation and Community Forums:

   • Refer to NVIDIA’s official documentation for OTA updates and troubleshooting guides.
   • Engage with community forums for additional insights or similar experiences from other users.

9. Best Practices for Future Updates:

   • Regularly back up configurations and important data before performing updates.
   • Test updates in a controlled environment before deploying them widely.

10. Unresolved Issues:

    • If problems persist after following these steps, further investigation may be required into specific error codes or logs generated during the update process.

By following these structured troubleshooting steps, users should be able to diagnose and potentially resolve issues related to OTA updates on their Jetson Orin Nano Dev boards effectively.