FSKP Fuse Burn: USB Write Timeout

Is this still an issue to support? Any result can be shared?

Hey,

Yes, the issue is still present. I’ve run an additional test and attached the latest logs for reference.

The following command executes successfully:

sudo ./fskp_fuseburn.py --board-spec orin-agx-board-spec-fixed.txt \
    --fusefile /mnt/l4t/JetsonKeys/nvidia_fskp/fuse_config_presecure.xml \
    --skipfskpkey \
    --chip 0x23 \
    --board /mnt/l4t/Linux_for_Tegra/jetson-agx-orin-devkit.conf \
    --outdir ./out_fuseblob \
    --test

Attached:

fuse_test_nokey_host.txt (3.2 KB)

fuse_test_nokey_target.txt (105.4 KB)

Any guidance or next steps would be greatly appreciated.

Hi again,

I reviewed all configurations and found that the paths to fskp_ak.bin and fskp_ek.bin were incorrect. After fixing them, the fuse burn completed with partial success on the target side.

The logs show an error during the burn, but the process still programmed the PKC key and BootSecurityInfo. I’m still unsure about the status of SBK, 0emK1, and 0emK2.

Logs attached:

complete-fuse-log-0212-host.txt (36.2 KB)

flash-read-info.txt (34.1 KB)

burn-fuse-target-0212.txt (7.1 KB)

My fuse_config_presecure.xml contents are:

<genericfuse MagicId="0x45535546" version="1.0.0">
    <!-- PKC: public key hash generated from your OEM public key -->
    <fuse name="PublicKeyHash" size="64" value="<PKC>"/>

    <!-- SBK: 128-bit AES key for boot image encryption -->
    <fuse name="SecureBootKey" size="32" value="<SBK>"/>

    <fuse name="OemK1" size="32" value="<0EMK1>"/>
    <fuse name="OemK2" size="32" value="<0EMK2>"/>

    <!-- BootSecurityInfo: must preserve pre-burned bits (0x1E0 factory value) by applying bitwise OR with desired flags.
         Example: new_value = 0x1E0 | desired_bits.
         This ensures reserved bits [8:4] remain intact and avoids PSC validation or USB timeout errors during FSKP fuse burn. -->
    <!-- 0x1E0 (factory) | 0x8 (SBK enable, bit 3) | 0x1 (PKC 3k RSA, bits [2:0]) | 0x200 (ODM Key Valid, bit 9) = 0x3E9 -->
    <fuse name="BootSecurityInfo" size="4" value="0x3E9"/>

    <!-- SecurityMode = 0x0 keeps Secure Boot unenforced for testing -->
    <fuse name="SecurityMode" size="4" value="0x0"/>
</genericfuse>

If the burn was successful, my next step would be to rerun it with SecurityMode enabled in the XML config. However, I’m concerned that the partial burn may now prevent other fuses from being written.

Any help or guidance would be appreciated a lot!