I have downloaded and unpacked the nvidia-l4t-jetson-orin-nano-qspi-updater_36.4.4-20250616085344_arm64.deb Debian. I am trying to find out how this QSPI update mechanism works.
I can see that after checking the prerequisite it eventually calls the bootloader_updater.sh script with the capsule update payload that gets put in nvme0n1p11 in /boot/efi/EFI/UpdateCapsule/jetson-orin-nano-devkit.Cap
My fist question is: What is in the capsule payload (jetson-orin-nano-devkit.Cap), is it just the exact bytes that are to be loaded onto the QSPI. Is it the same as the UEFI bin in Linux_for_Tegra/bootloader/uefi_jetson.bin in the BSP
My second question is: Is there a way to generate my own .Cap raw binary blob file?
My Final question is why do we set bit 2 of the OsIndications UEFI variable:
Any help would be greatly appreciated
Many thanks,
Matt