You could just use dd command to write into OsIndications-8be4df61-93ca-11d2-aa0d-00e098032b8c as the guide w/o modifying the original OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c.
Hey @KevinFFF yeah, I was confused by the variable not existing. I tried it with the OsIndications now, but my system does ot attempt to perform any update. What could be causing this?
The nvbootcontrol gives me a status 0, so the update has not been attempted.
As the guide stated I copied the capsule generated with l4t_generate_soc_bup.sh and l4t_generate_soc_capsule-sh to the esp partition in a newly created folder UpdateCapsule and wrote the variable into OsIndications. Nothing happened.
Do we have any updates on this topic? I’m seeing the same issue when trying to update my Tegra Orin on Rel 35.2.1.
I followed the instructions to generate the capsule payload and updated the efivar.
However, after rebooting, nothing seemed happened, and the capsule payload that I placed in the EFI/UpdateCapsule directory is deleted.
Let me update the overall workflow for Capsule Update on AGX Orin devkit with JP5.1.
[Host]
$ sudo ./l4t_generate_soc_bup.sh t23x
$ ./generate_capsule/l4t_generate_soc_capsule.sh -i bootloader/payloads_t23x/bl_only_payload -o ./TEGRA_BL.Cap t234
$ scp TEGRA_BL.Cap <Username>@<IP address>:~/
[Target]
$ sudo su
# ll /dev/disk/by-partlabel/esp
# sudo mount /dev/mmcblk0p10 /mnt/
# cd /mnt/EFI
# mkdir UpdateCapsule
# cd UpdateCapsule/
# cp ${HOME}/TEGRA_BL.Cap .
With QSPI flash:
# printf "\x07\x00\x00\x00\x04\x00\x00\x00\x00\x00\x00\x00" > /tmp/var_tmp.bin
# cd /sys/firmware/efi/efivars/
# dd if=/tmp/var_tmp.bin of=OsIndications-8be4df61-93ca-11d2-aa0d-00e098032b8c bs=12
# reboot
You will see update status in UEFI after reboot
Run the following command to check if update is successful
$ sudo nvbootctrl dump-slots-info
[sudo] password for nvidia:
Current version: 35.2.1
Capsule update status: 1
Current bootloader slot: B
Active bootloader slot: B
num_slots: 2
slot: 0, status: normal
slot: 1, status: normal