Determine what partitions are updated during a bootloader update using UEFI capsule

Hi,

I’m currently working on a custom OTA solution for AGX Orin based on JetPack 6.1. I included the UEFI capsule tegra-bl.cap, the kernel image, the kernel dtb, and the rootfs image in my OTA package. I was able to trigger the bootloader update and boot into the updated slot.

Flashing the kernel, kernel-dtb, and APP partitions seems pretty straightforward, but I’m wondering what partitions on the SPI flash does the UEFI updater flash using the update capsule - does it update all partitions on the SPI flash? Does it update any partition on the eMMC? There doesn’t seem to be much information on this in Update and Redundancy — NVIDIA Jetson Linux Developer Guide 1 documentation.

Thanks!

Hi shihuac,

Are you using the devkit or custom board for AGX Orin?

Do you mean the capsule update or image-based OTA update?

Hi Kevin,

I’m using a custom board and developing a Yocto image based on JetPack 6.1 (L4T 36.4.0). I mean the capsule update (by putting the capsule in the esp partition on the eMMC and setting the OsIndications UEFI variable). I’d like to know what contents does the UEFI capsule contain, and which partitions on the SPI flash & the eMMC does the UEFI write to during a bootloader update. The UEFI capsule was generated from this recipe

Thanks!

Sorry that we don’t verify and maintain yocto project currently, but it seems some users have similar expeirence.
You can perform capsule update with L4T first and you would see(from log) that it includes the partitions in QSPI(e.g. BCT, mb1, mb2, bpmp-fw, cpu-bootloader…etc).

Thanks Kevin, I will try it.

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