Hi, I’m trying to test and validate the process outlined at - Tegra Linux Driver I’ve generated pkc, sbk and kek2 keys. pkc = openssl key generated as mentioned in guide sbk = 4x 8bit hex values, e.g. 0xaaaaaaaa 0xbbbbbbbb 0xcccccccc 0xdddddddd kek2 = 128 bit hex value I first attempted with -…

@DaneLLL Some good news, I was able to flash successfully (on the new devkit) and boot successfully. serial.log (37.6 KB) flash-secure.log (433.9 KB) I’ll reply to the email thread about the bricked jetson, thanks for your help.

Hi, Do you have -p in the odmfuse command? SecurityMode should be present with -p.

ah, ok, I added the -p flag this time and xml file looks good. Proceeded to burn fuse but Boot Rom communication failed error: fuse-burn.log (2.2 KB) (no serial output)

Hi, We will check why the error happens. For information, is the new one also Xavier 16GB?

Thanks, current and new device are both 32GB models.

Hi, It looks like the board has been fused already. [ 0.0358 ] BR_CID: 0xd80219116459e587100000000fff0240 This is result from retrieving CID. The first nibble of d tells us this board is PKC + SBK fused board. For a clean board, the first nibble is expected to be 8.

Hi Dane, Yes, if you recall we burned the fuses a while back, the start of when we had issues. I’m guessing editing the file to remove the keys might of been the issue. Before I burn again, I just want to clarify the exact steps, (cos these boards ain’t cheap and getting them is difficult / timel…

Hi, So fuse-burn.log is from the Xavier that has been fused, and can be flashed, but cannot cold boot. Is my understanding correct? For fusing enable_watchdog in sw_reserved, it should be -r 0x20. The Xavier has been fused with -j -i 0x19 -c PKC -k pkc.pem -S sbk.txt --KEK2 kek2.txt But you woul…

So fuse-burn.log is from the Xavier that has been fused, and can be flashed, but cannot cold boot. Is my understanding correct? Yes To confirm, the official documentation is wrong? docs - it shows as ‘5’, would like to test the watchdog functionality, it may already be enabled but just want t…

@DaneLLL if it helps, on the new device, the watchdog is enabled by default, I’m guessing we don’t need to amend fuses for enable_watchdog. What does -r 0x20 represent?

Hi, The description in README_secureboot.txt: -r 0xXX Sets sw_reserved=0xXX. The name of this fuse field is confusing, but the meaning is as follows: bit[7-6] reserved bit[5 ] enable_watchdog bit[4 ] enable_charger_detect …

Unable to burn fuses (dev kit) / no more output (serial/hdmi) / bricked?

Robotics & Edge Computing Jetson Systems Jetson AGX Xavier

DaneLLL April 28, 2020, 3:07am 88

Hi,
Two watchdog timers listed in document are enabled by default. We are checking what the watchdog is in sw_reserved fuse.

For fusing odm_production_mode on PKC-and-SBK-fused device, we are still working on a solution. Will update once there is a solution.

Xavier doesn't boot after Secure Boot (PKC + SBK + KEK2) flash (JetPack 5.1.5 / L4T R35.6.1)

Topic		Replies	Views
Failed to write Fuses，Fuse burn is not supported Jetson AGX Xavier security , nvbugs	48	2921	October 26, 2023
Fuse burning failure after a successful KEK0 Jetson TX2 nvbugs	10	1634	January 22, 2021
How to burn ODM fuse bits (TX2)? Jetson TX2 security	29	3059	May 3, 2020
KEK Fuse burn failed on Jetson Xavier R32.3.1 Jetson AGX Xavier security , nvbugs	9	1900	May 20, 2020
Secure Boot odmfuse programming step fail on 32.2.1 Jetson TX2	19	2951	February 6, 2020
Concerns about fuse burning on TX2 Jetson TX2 security , nvbugs	31	4050	September 1, 2021
Jetson Xavier NX burn Tegra fuses made the device unbootable Jetson Xavier NX security , nvbugs	23	3191	May 18, 2021
Odmefuse.sh not burning SBK key Jetson TX2 security , nvbugs	40	1912	April 16, 2024
Postmortem: Jetson Xavier AGX will not get past Boot ROM after burning PKC+SBK+KEK256 Jetson AGX Xavier security	8	2152	March 31, 2022
Secure Boot TX2i Jetson TX2 security	3	1417	March 12, 2021

Unable to burn fuses (dev kit) / no more output (serial/hdmi) / bricked?

Related topics