hello flixr,
it seems like a bug in the r35.5.0 UEFI, and it’s been address in the r36.5.0
unfortunately, JP-5 is reaching EOL, JetPack 5 upcoming End-of-Life notice.
so.. we should check whether BootChainFwNext is present before staging the capsule, the capsule flow can abort with 6163; let’s have a software workaround to clear it first avoids the conflict.
Before a bootloader capsule update on r35.5.0, make sure there is no pending boot-chain switch state:
– delete BootChainFwNext if present
– preferably also avoid carrying over stale BootChainFwStatus
– then copy the capsule, set OsIndications
– reboot