about fskp_fuseburn.sh

In the “VibranteSDK/vibrante-t186ref-foundation/utils/scripts/fuseburn”, the “fskp_fuseburn.sh” is used to fuse the px2. The usage is shown below

# ./fskp_fuseburn.sh -h
./fskp_fuseburn.sh <args>
--help/-h             : Display help
--fusefile/-f <file>  : Provide fuse xml file
--burnfuse/-b         : Burn fuse on target
--skipconfirmation/-s : skip confirmation message while fuse burning
--test/-t             : perform dummy operation, do not burn fuses on target
--key/-k <key file>   : Provide FSKP key file
--keyindex/-i <index> : Key index to burn
--rpmb/-r             : RPMB Key Provisioning
--outdir/-g <Path>    : Generate blob at <Path> only and do not burn
--prebuilt/-P <Path>  : Pick prebuild blob from <Path> and do not generate
--verbose/-v          : enable verbose prints

I want to know what does the “keyindex” mean? Any documentation illustrates it?

I set the keyindex to 0, and try to fuse the px2 and the output is shown below. What’s wrong?

test@test:dir$./fskp_fuseburn.sh -f sample_fskp_fuse_1.xml -b -k rsa_private_key.pem -i 0 -v
Burning Fuses option is selected for 0, this operation is permanent and irreversible
Do you want to continue? [y/N]y
FSKP Burning activity started
Bus 003 Device 006: ID 0955:7018 NVidia Corp.
s_BR_CID=BR_CID: 0x818010016419f105000000000a018280
MagicId=0x46555345 version=0x1
node: name=SecureBootKey size=16
'/home/test/VibranteSDK/vibrante-t186ref-foundation/utils/scripts/fuseburn/../../../firmware/t186/fskpboot/fskp.bin' -> './fskp.bin'
size of FSKP binary 56492
size of Fuse Blob 48
File saved as fskp_updated.bin
RCM 0 is saved as rcm_0.rcm
RCM 1 is saved as rcm_1.rcm
List of rcm files are saved in rcm_list.xml
PKC key in Open SSL format
Saving public key  in pub_key.key
Downloading FSKP blob
Bootrom returned error 22
Boot Rom communication failed

Dear merlinwu,

Can I know what you want to do with it?
Besides, if you are using “VibranteSDK”, it is old PDK. Thanks.

I want to fuse some specific fuses such as “secure_boot_key”, “boot_security_info” and so on