hello kyoungh,
it seems some contradiction with your step-3 and step-4. it should not burning fuses due to the variable (i.e. BootSecurityInfo) has a mismatch, it shows PKC key hash of your step-3 although you did not given the key to the script, and you’re able to re-flash without given keys.
generally, once you’ve fused a target, you’ll need to provide the exactly same keys for running flash command-line. otherwise, it’ll abort the flashing process.
there’s Boot Rom communication in the early stage.
for instance, it’ll report the errors like below and abort the process if you did not given keys to the fused target.
Error: Either RSA key file is not provided or SBK key file is provided for PKC protected target board.
did you have any UART logs for reference?
since it’s only checking PKC/SBK for Boot Rom communication, let’s narrow down this by having only those two keys to re-flash your target.
for instance, $ sudo ./flash.sh -u ecp256.pem -v sbk-32.key jetson-agx-orin-devkit mmcblk0p1
BTW, please refer to similar forum topics, such as.. Topic 330828, Topic 335952 as see-also.