FYI, PKC for sign: if PKC is burned, then the KEYFILE users provide is for signing the images. SBK for encryption: if SBK is burned, then the SBKFILE users provide is for encrypting the images. KEKs for encryption keys: they are keys to encrypt your keys. KEK0, KEK1, KEK2 are 128-bit key files; KEK256 is 256-bit key file. please use the commands, --KEK* to determine which key encryption key you’re going to fused.
for Orin series, it supports PKC with RSA-3K only, and 256-bit SBK only;
XML based is validated only for AGX Orin platform. odmfuse uses openssl + tegraopenssl.
you may see-also Topic 266387 for more details of fuse configuration.
you may see-also the binaries under… $OUT/Linux_for_Tegra/bootloader/signed/
it’s tegrasign_v3 for processing, let’s taking mb1 binary as an example,
as you can see… it’ll write A_mb1 partition with the signed/encrypted binary file.
instead of PKC, UEFI uses the PK, the KEK, and the db keys.
BTW, have you also referred to the steps in $OUT/Linux_for_Tegra/tools/README_uefi_secureboot.txt