Platform: Jetson Orin Nano (p3767, SKU 0003), t234 / chip 0x23 · L4T: R39.2.0
Following Quick Start Guide to Enable Secure Boot for Jetson Orin with fskp_fuseburn.py (from host_overlay_fskp_tools_R39.2.0). The guide’s production fuse.xml sets PublicKeyHash / BootSecurityInfo / SecurityMode and does not include Kdk0. We do not use fTPM.
Blob generation fails at the parser:
Exit due to an unsupported configuration: Security_Mode[0] = 0x1 and Kdk0 is absent
Failed to generate fuse info, ErrNum=4
SecurityMode=0x1 alone is the trigger — any XML without it parses fine:
$ cat min.xml
<genericfuse MagicId="0x45535546" version="1.0.0">
<fuse name="SecurityMode" size="4" value="0x1"/>
</genericfuse>
$ ./tegraparser_v2 --chip 0x23 --fuse_info min.xml out.bin
Exit due to an unsupported configuration: Security_Mode[0] = 0x1 and Kdk0 is absent
(The overlay and base-BSP tegraparser_v2 are byte-identical and both do this.)
This contradicts the Quick Start (no Kdk0 in its examples) and prior guidance in the KdK0 fuse thread, where staff say KDK0 is fTPM-only, “we don’t recommend burning this fuse,” and “SBK, PKC, OEM_K1 and OEM_K2 are enough for secure boot.”
Questions:
- On R39.2, is
Kdk0 now required to burn SecurityMode=0x1 without fTPM?
- If not, what is the intended Quick Start flow to burn
SecurityMode (separate stage? a flag? updated tegraparser_v2)?
- If required, what value for a non-fTPM unit, and any side effects?
Thank you for the detailed report and clear reproduction case. You’ve identified an important discrepancy: the R39.2 Quick Start Guide does not mention Kdk0 as a requirement for SecurityMode=0x1, but tegraparser_v2 now rejects this configuration with “Kdk0 is absent.”
This contradicts prior staff guidance (forum post #341385) stating that Kdk0 is fTPM-only and not required for secure boot with SBK/PKC keys.
Your three questions are well-scoped:
- Is
Kdk0 now required on R39.2 to burn SecurityMode=0x1 without fTPM?
- If not, what is the intended Quick Start flow (separate stage, flag, or updated parser)?
- If required, what value for non-fTPM units and any side effects?
This requires engineering clarification on whether the R39.2 tegraparser_v2 behavior changed relative to documentation, or if the Quick Start Guide needs updating. A moderator will follow up with the appropriate team.
hello lander.noterman,
let me have confirmation,
we would like to check all the fuse variable you’ve program onto the module, could you please share the fuse.xml for reference, you may omit the fuse variable values for security concerns.
besides.. please execute flash script with --read-info to have fuse read,
i.e. $ sudo ./flash.sh --read-info -u <pkc> -v <sbk> <target_conf> <rootdev>
I was trying to use the XML example from here: https://docs.nvidia.com/jetson/archives/r39.2/DeveloperGuide/SD/Security/SecureBoot/FuseConfiguration.html#example-jetson-orin-fuse-configuration-file-to-program-an-rsa-3k-key
To keep it simple with only one PKC, but I added the OemK1 key which is needed for disk encryption arriving at this XML:
<genericfuse MagicId="0x45535546" version="1.0.0">
<fuse name="PublicKeyHash" size="64" value="<hash>"/>
<fuse name="BootSecurityInfo" size="4" value="0x201"/>
<fuse name="OemK1" size="32" value="<oemk1>"/>
<fuse name="SecurityMode" size="4" value="0x1"/>
</genericfuse>
sudo ./flash.sh --read-info jetson-orin-nano-devkit internal gives:
Board ID(3767) version(301) sku(0003) revision(H.1)
RAMCODE is 2
Chip SKU(00:00:00:D5) ramcode(2) fuselevel(fuselevel_production) board_FAB(301)
ECID is 0x80012344705E014C280000000DFE8240
==== Fuse Info (/home/lander/l4t-r39.2/Linux_for_Tegra/bootloader/fuse_t234.bin) ====
PublicKeyHash: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PkcPubkeyHash1: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PkcPubkeyHash2: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
BootSecurityInfo: 000001e0
ArmJtagDisable: 00000000
SecurityMode: 00000000
SwReserved: 00000000
DebugAuthentication: 00000000
OdmInfo: 00000000
OdmId: 0000000000000000
OdmLock: 00000000
ReservedOdm0: 00000000
ReservedOdm1: 00000000
ReservedOdm2: 00000000
ReservedOdm3: 00000000
ReservedOdm4: 00000000
ReservedOdm5: 00000000
ReservedOdm6: 00000000
ReservedOdm7: 00000000
Sku: 000000d5
Uid: 4082fe0d000000284c015e7004000000
OptEmcDisable: 0000000c
==== EEPROM content (/home/lander/l4t-r39.2/Linux_for_Tegra/bootloader/cvm.bin) ====
00000000: 02 00 fe 00 00 00 00 00 00 00 00 ff 00 00 00 00 ................
00000010: 00 01 00 01 36 39 39 2d 31 33 37 36 37 2d 30 30 ....699-13767-00
00000020: 30 33 2d 33 30 31 20 48 2e 31 00 00 00 00 00 00 03-301 H.1......
00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000040: b0 48 00 00 3d b0 27 47 bb 4c 31 34 32 33 37 32 .H..=.'G.L142372
00000050: 35 30 37 39 30 30 34 00 00 00 00 00 00 00 00 00 5079004.........
00000060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000090: 00 00 00 00 00 00 4e 56 43 42 00 ff 4d 31 00 00 ......NVCB..M1..
000000a0: 00 00 00 00 00 00 00 00 00 00 00 00 3d b0 27 47 ............=.'G
000000b0: bb 4c 01 00 00 00 00 00 00 00 00 00 00 00 00 00 .L..............
000000c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000000f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e3 ................
It already fails on the host-side though:
sudo ./fskp_fuseburn.py --board-spec orinnano-board-spec.txt \
-f my_fuses.xml --skipfskpkey --test \
-g out/ -c 0x23 -B ~/l4t-r39.2/Linux_for_Tegra/jetson-orin-nano-devkit.conf
FSKP execution started 2026-07-17 08:53:13.817291
fskp_fuseburn.py script version 0.2
Parsing input arguments
FSKP keyslot is skipped
fskp_fuseburn.py script version 0.2
Parsing input arguments
FSKP keyslot is skipped
Setting up default paths
Setup host environment
Creating t234 fuse blob
command /home/lander/l4t-r39.2/Linux_for_Tegra/l4t/tools/flashtools/flash/tegraparser_v2 --chip 0x23 --fuse_info /home/lander/l4t-r39.2/Linux_for_Tegra/l4t/tools/flashtools/fuseburn/out/basalte_fuse_t234_test.xml /home/lander/l4t-r39.2/Linux_for_Tegra/l4t/tools/flashtools/fuseburn/out/fuse_info_t234_test.bin failed, exit-code=4 error =
command /home/lander/l4t-r39.2/Linux_for_Tegra/l4t/tools/flashtools/flash/tegraparser_v2 --chip 0x23 --fuse_info /home/lander/l4t-r39.2/Linux_for_Tegra/l4t/tools/flashtools/fuseburn/out/basalte_fuse_t234_test.xml /home/lander/l4t-r39.2/Linux_for_Tegra/l4t/tools/flashtools/fuseburn/out/fuse_info_t234_test.bin failed.
MagicId=0x54534554 version=0x1
node: name=PublicKeyHash size=64
type 0x2a size 64
value=0xc31f08f75bade958d21efe7368a7366a827eb79b41bffde557e803a57f8fe26a28262ed2faa27fe6358dd3067cb4407bd95fd7dd4b692e43e6b7e6a627f76aed
node: name=OemK1 size=32
type 0x6a size 32
value=0x863c7bab184d41515871d4ee7cd040c6447d4c9fda2238097c0c4caaed7f0df4
node: name=BootSecurityInfo size=4
type 0x0 size 4
value=0x201
node: name=SecurityMode size=4
type 0x1d size 4
value=0x1
Exit due to an unsupported configuration: Security_Mode[0] = 0x1 and Kdk0 is absent
Failed to generate fuse info, ErrNum=4
FSKP execution failed
Traceback (most recent call last):
File "/home/lander/l4t-r39.2/Linux_for_Tegra/l4t/tools/flashtools/fuseburn/./fskp_fuseburn.py", line 143, in <module>
main(sys.argv)
~~~~^^^^^^^^^^
File "/home/lander/l4t-r39.2/Linux_for_Tegra/l4t/tools/flashtools/fuseburn/./fskp_fuseburn.py", line 137, in main
raise e
File "/home/lander/l4t-r39.2/Linux_for_Tegra/l4t/tools/flashtools/fuseburn/./fskp_fuseburn.py", line 132, in main
u.main(commandLineArgs)
~~~~~~^^^^^^^^^^^^^^^^^
File "/home/lander/l4t-r39.2/Linux_for_Tegra/l4t/tools/flashtools/fuseburn/./fskp_fuseburn.py", line 95, in main
h.create_fuse_blob_t234()
~~~~~~~~~~~~~~~~~~~~~~~^^
File "/home/lander/l4t-r39.2/Linux_for_Tegra/l4t/tools/flashtools/fuseburn/fskp_helper.py", line 598, in create_fuse_blob_t234
self.create_test_fuse_blob_t234()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/home/lander/l4t-r39.2/Linux_for_Tegra/l4t/tools/flashtools/fuseburn/fskp_helper.py", line 531, in create_test_fuse_blob_t234
self.run_cmd(cmd)
~~~~~~~~~~~~^^^^^
File "/home/lander/l4t-r39.2/Linux_for_Tegra/l4t/tools/flashtools/fuseburn/fskp_helper.py", line 379, in run_cmd
raise OSError("command " + cmd + " failed.\n" + output)
OSError: command /home/lander/l4t-r39.2/Linux_for_Tegra/l4t/tools/flashtools/flash/tegraparser_v2 --chip 0x23 --fuse_info /home/lander/l4t-r39.2/Linux_for_Tegra/l4t/tools/flashtools/fuseburn/out/basalte_fuse_t234_test.xml /home/lander/l4t-r39.2/Linux_for_Tegra/l4t/tools/flashtools/fuseburn/out/fuse_info_t234_test.bin failed.
MagicId=0x54534554 version=0x1
node: name=PublicKeyHash size=64
type 0x2a size 64
value=0xc31f08f75bade958d21efe7368a7366a827eb79b41bffde557e803a57f8fe26a28262ed2faa27fe6358dd3067cb4407bd95fd7dd4b692e43e6b7e6a627f76aed
node: name=OemK1 size=32
type 0x6a size 32
value=0x863c7bab184d41515871d4ee7cd040c6447d4c9fda2238097c0c4caaed7f0df4
node: name=BootSecurityInfo size=4
type 0x0 size 4
value=0x201
node: name=SecurityMode size=4
type 0x1d size 4
value=0x1
Exit due to an unsupported configuration: Security_Mode[0] = 0x1 and Kdk0 is absent
Failed to generate fuse info, ErrNum=4
Edit: whoops I pasted my OEMK1 key, I’ll generate a new one since nothing’s fused yet
Thank you for the detailed diagnostics. Your issue reveals a discrepancy between the R39.2 Quick Start Guide and the tegraparser_v2 tool behavior that requires engineering review.
Summary of your findings:
- The R39.2 Quick Start Guide example omits
Kdk0 from the fuse.xml
- tegraparser_v2 rejects
SecurityMode=0x1 without Kdk0, returning: “Security_Mode[0] = 0x1 and Kdk0 is absent”
- Prior guidance (forum #341385) states
Kdk0 is fTPM-only and not required for secure boot without fTPM
What we need to clarify:
This appears to be either:
- A documentation gap in the R39.2 Quick Start Guide (should include
Kdk0 requirement)
- A tool version change in R39.2 that introduced a new
Kdk0 requirement
- A legitimate requirement change for R39.2 secure boot
Your reproduction case is minimal and clear. We’re escalating this to the R39.2 secure boot engineering team to clarify the intended workflow and update documentation accordingly.
hello lander.noterman,
according to your fuse read results, your board has not fuse yet.
here’s one thing important,
please refer to Jetson Orin Series Modules Fuse Update Field Services Bulletin .
the fuse value for boot_security_info was burned (by manufacturing) to 0x1e0.
hence.. your fuse.xml BootSecurityInfo=0x201 is incorrect.
you must have an OR (0x1e0) new settings of your FUSE_BOOT_SECURITY_INFO.