Hi Kevin,
Thanks for reply.
Are you trying to create a capsule payload of R35.3.1 and upgrade this package on the same board?
Yes
Can the update progress work w/o this change?
No, I copy this package to the EFI/UpdateCapsule
directory in the esp
partition.
And set the bit2 of the OsIndications
UEFI variable.
Normally, it will show a progress bar on logs like this (Which I use TEGRA_BL.Cap):
sudo rebotot
[ 2604.397687] watchdog: watchdog0: watchdog did not stop!
[ 2604.922285] Trying to unregister non-registered hwtime source
[ 2605.161418] arm-smmu 8000000.iommu: disabling translation
[ 2605.167407] arm-smmu 10000000.iommu: disabling translation
[ 2605.173159] arm-smmu 12000000.iommu: disabling translation
[ 2605.179675] reboot: Restarting system
Jetson UEFI firmware (version 3.1-32827747 built on 2023-03-19T14:56:32+00:00)
Jetson UEFI firmware (version 3.1-32827747 built on 2023-03-19T14:56:32+00:00)
ESC to enter Setup.
F11 to enter Boot Manager Menu.
Enter to continue boot.
Update Progress - 5% **++++++++++++++++++++++++++++++++++++++++++++++++Update Progress - 6% ***+++++++++++++++++++++++++++++++++++++++++++++++Update Progress - 7% ***+++++++++++++++++++++++++++++++++++++++++++++++Update Progress - 8% ****++++++++++++++++++++++++++++++++++++++++++++++Update Progress - 9% ****++++++++++++++++++++++++++++++++++++++++++++++Update Progress - 10% *****+++++++++++++++++++++++++++++++++++++++++++++Update Progress - 11% *****+++++++++++++++++++++++++++++++++++++++++++++Update Progress - 12% ******++++++++++++++++++++++++++++++++++++++++++++Update Progress - 13% ******++++++++++++++++++++++++++++++++++++++++++++Update Progress - 14% *******+++++++++++++++++++++++++++++++++++++++++++Update Progress - 15% *******+++++++++++++++++++++++++++++++++++++++++++Update Progress - 65% ********************************++++++++++++++++++Update Progress - 66% *********************************+++++++++++++++++Update Progress - 67% *********************************+++++++++++++++++Update Progress - 68% **********************************++++++++++++++++Update Progress - 69% **********************************++++++++++++++++Update Progress - 70% ***********************************+++++++++++++++Update Progress - 95% ***********************************************+++Update Progress - 100% **************************************************Jetson UEFI firmware (version 3.1-32827747 built on 2023-03-19T14:56:32+00:00)
Jetson UEFI firmware (version 3.1-32827747 built on 2023-03-19T14:56:32+00:00)
ESC to enter Setup.
F11 to enter Boot Manager Menu.
Enter to continue boot.
** WARNING: Test Key is used. **
…L4TLauncher: Attempting Direct Boot
EFI stub: Booting Linux Kernel…
EFI stub: Using DTB from configuration table
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services and installing virtual address map…
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd421]
[ 0.000000] Linux version 5.10.104-tegra (buildbrain@mobile-u64-6289-d7000) (aarch64-buildroot-linux-gnu-gcc.br_real (Buildroot 2020.08) 9.3.0, GNU ld (GNU Binutils) 2.33.1) #1 SMP PREEMPT Sun Mar 19 07:55:28 PDT 2023
[ 0.000000] OF: fdt: memory scan node memory@80000000, reg size 16,
But when I use TEGRA_KL.Cap, it doesn’t show any progress bar, just a normal boot log.
After boot done, I use nvbootctl to check status.
Success:
nvidia@nvidia-ubuntu:~$ sudo nvbootctrl dump-slots-info
[sudo] password for nvidia:
Current version: 35.3.1
Capsule update status: 1
Current bootloader slot: B
Active bootloader slot: B
num_slots: 2
slot: 0, status: normal
slot: 1, status: normal
Fail:
nvidia@nvidia-ubuntu:~$ sudo nvbootctrl dump-slots-info
[sudo] password for nvidia:
Current version: 35.3.1
Capsule update status: 0
Current bootloader slot: B
Active bootloader slot: B
num_slots: 2
slot: 0, status: normal
slot: 1, status: normal
I noticed that Cap file in UpdateCapsule disappeared after fail update.
Normally it will still in the folder if the update process is not executed,
so I think it do have executed update process, but something went wrong.
Here’s full log:
Good.txt (123.2 KB)
Bad.log (122.0 KB)