Problems with follow up OTA update after JP5->JP6 OTA update

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
1

Hi reagrding the closed topic Problems with follow up OTA update after JP5->JP6 OTA update

I was away and missed your response. The problem still persists.

Below is copied from old topic:

We have the following case:

The devices at the customer have:

  • a custom carrier board
  • a custom kernel
  • are flashed with 35.5.0
  • we used ROOTFS_AB=1

We updated the devices to 36.4.0 with an OTA update containing a new bootloader and rootfs. That works fine.
However if we make a new update OTA from (also containing bootloader since we have to update the second bootchain) the update fails and we go back to the previous bootslot or are left with a bricked device.

On the other hand if we flash JP6 directly to a board we can update it. so it seems to be related to the bootloader updat failing.

  • R35-to-R36 ota update command: sudo -E BASE_BSP=download/R35_5_base_bsp_dir ROOTFS_AB=1 build/Linux_for_Tegra/tools/ota_tools/version_upgrade/l4t_generate_ota_package.sh --external-device nvme0n1 -S 25GiB jetson-orin-nano-devkit R35-5

    • JP5 to JP6 ota command for reference

  • R36-to-R36 ota update command (rootfs and bootloader): sudo -E BASE_BSP=build/Linux_for_Tegra ROOTFS_AB=1 build/Linux_for_Tegra/tools/ota_tools/version_upgrade/l4t_generate_ota_package.sh --external-device nvme0n1 -S 25GiB jetson-orin-nano-devkit R36-4

    • Building JP6->JP6 update with bootloader and rootfs
    • This update updates the bootloader after reboot
    • After updating the bootloader it attempts and failes multiple times to boot into the new bootslot
    • Returns to previous bootslot after
    • JTAG_bootloader_rootfs_log.txt (308.8 KB)

  • R36-to-R36 ota update command (bootloader only): sudo -E BASE_BSP=build/Linux_for_Tegra ROOTFS_AB=1 build/Linux_for_Tegra/tools/ota_tools/version_upgrade/l4t_generate_ota_package.sh --external-device nvme0n1 -S 25GiB -b jetson-orin-nano-devkit R36-4

    • Building JP6->JP6 update with bootloader only
    • This update updates the bootloader after reboot
    • After updating the bootloader it hangs while trying to boot (I waited for 12 hours)
    • Is in a unbootable state after
    • JTAG_bootloader_only_log.txt (77.3 KB)
3

Hi,

Do you mean update OTA from 35.5.0 will fail, but update from r36.x (r36.3.0) will succeed?

Thanks

4

Difference is what was flashed initially.
Initial flash with 35.5.0 → update from 35.5.0 to 36.3.0 → update from 36.3.0 to 36.x fails.
Initial flash with 36.3.0 → update from 36.3.0 to 36.x works.

So at the moment we could update customer devices to JP6 but then any follow up updates wouldnt work.

5

Hi,

Thank you for your clarify.
Do you confirm this issue also happened on our dev kit ?

Thanks