I see exactly the same problem documented here by ncs1. But that thread did not provide solution in the end. After fusing another Jetson Orin from scratch, I found that the issue is caused by the OemKeyValid bit 9 of BootSecurityInfo. Basically, this bit must be marked in the same fusing operation…

hello c.lin, please try with r36.5 to replace odmfuse.func with the attachment, Topic363914_Mar24.zip (9.9 KB) it should unblock MB1 to continue burning fuses.

hello c.lin, please share the very first fuse xml file you’re used to burn fuse. if that’s possible, please also share the logs for reference.

Thanks Jerry, Here are fuse configuration files good_fuse_conf_with_oemkeyvalid.txt (1.2 KB) bad_fuse_conf_without_oemkeyvalid.txt (1.2 KB) The only difference is the bit-9 oemKeyValid bit set or not All PKC keys are RSA-3072. It appears to me that BootROM is in bad state: It requires host to …

hello c.lin, let’s try program the BootSecurityInfo from 0x1e9 to 0x3e9. please refer to Burn Fuses with the Fuse Configuration file . you should use the xml file with below.. <genericfuse MagicId="0x45535546" version="1.0.0"> <fuse name="BootSecurityInfo" size="4" value="0x3e9"/> </generic…

Hi Jerry, Thanks for your support. It seems like we are not in sync with what the problem is. The problem is: I cannot fuse it anymore. The mb1 sent to SOM is rejected. The host side (Linux PC) gets error “"ERROR: might be timeout in USB write.” Here are the detailed log files: log-on-host-side…

hello c.lin, according to BR_CID, this is target burned with 3072-bit RSA PKC, and SBK enabled. [ 0.6331 ] BR_CID: 0x89012344705DF6C70C00000002018080 do you have OEM_K1 burn to this target yet? if not. please try again with below xml file. <genericfuse MagicId="0x45535546" version="1.0.0"> …

Hi Jerry, The OemK1 was burnt to the target earlier. See the bad_fuse_conf_without_oemkeyvalid.txt attached. bad_fuse_conf_without_oemkeyvalid.txt (1.2 KB) To fuse “oem key valid” bit, I tried both cases with/without “OemK1” content in fuse conf. Neither one worked. See the log on both host(Linu…

Hi Jerry, I dig around your(nvidia) tech support forums and found (so far) there 3 other threads (342811, 342924 and 300161) linked below. [image] Cannot use flash cmd after burn fuse Jetson Orin NX 我使用的是Jetpack5.1.5，自制的底板，我在验证secure boot功能我的最终目标是启用secure …

hello c.lin, please refer to previous post #5 , let’s try running with odmfuse script again without given PKC/SBK keys (without -k and -S commands). in other words, just treat the target as a NS board. for instance, $ sudo ./odmfuse.sh -X <fuse_config> -i 0x23 <target_config>

Hi Jerry, Can you please talk to your engineer team who work on BootROM or Fuse? When developers contact Nvidia, they have already exhausted all options that publicly available. Of course, the first thing I tried was to treat the SOM like an NS board (without -k and -S command) since the “securemo…

Hi Jerry, Thanks for something new to try. But did your side try that odmfuse.func you sent? It does not run. It complains about “ECID read failed. The target board must be attached in RCM mode”. But the SOM is in “force recovery mode”. Here is the terminal on Linus host side. (The target side i…

BootROM bug? Seek solution to recover SOM fused with SBKPKC but not OemKeyValid bit

Robotics & Edge Computing Jetson Systems Jetson Orin NX

c.lin March 20, 2026, 3:15pm 9

Hi Jerry,

I dig around your(nvidia) tech support forums and found (so far) there 3 other threads (342811, 342924 and 300161) linked below.

They ALL point to the same problem:

OemKeyValid bit not set in first board and results in the same problem.

OemKeyValid bit set in 2nd board and works well.

There is no solution provided to recover the first board and the thread was closed.

I am seeking a solution to recover the first board. I believe this is an undocumented bug in BootROM. At a minimum, the document is misleading. OemKeyValid bit, by common sense, makes people think it is related to OemK1 & OemK2, and should NOT be related to SBC key.

Topic		Replies	Views
Cannot burn key-type fuses (SecureBootKey, OemK1) incrementally after PublicKeyHash-only fuse burn — FSKP fails with "Could not write Fuse" regardless Jetson Orin Nano security	12	106	July 10, 2026
Jetson Orin NX - board can't flash after partial fuse burn Jetson Orin NX security , nvbugs	53	1516	March 18, 2026
ERROR: might be timeout in USB write after Fuse burning Jetson Orin NX boot , reflash , security	5	2083	August 25, 2023
Orin Nano R36.5 SBKPKC: bootrom RCM rejects HSM-encrypted mb1, no UART output — chain spec verified Jetson Orin Nano security	11	145	June 24, 2026
Help burning fuses after PublicKeyHash fuse was burned Jetson Orin NX reflash , security , nvbugs	13	560	March 7, 2025
Fail to boot with SBK Jetson Orin Nano boot , reflash , security , nvbugs	70	4403	October 30, 2023
Burn ODM Key Valid fuse bit on PKCSBK fused Jetson orin nano Jetson Orin Nano boot , security	22	327	December 11, 2025
Problem with fuse burning Jetson Orin Nano security	24	327	April 13, 2026
Flashing with SBK keyfile failed @ unburn fuse of Orin Nano @ Jetpack 6.2 Jetson Nano boot , security	11	125	February 4, 2026
Secure Boot for Orin NX Jetson Orin NX boot , security	29	4205	October 13, 2023

BootROM bug? Seek solution to recover SOM fused with SBKPKC but not OemKeyValid bit

Related topics