Hi, Yet another question about a fuse burning. This looks like the post , but whose link marked as a solution does not exist or I can not access. TX2 carrier board, L4T 32.2.3 This has happened as follows. KEK0 was burned with PKC $ echo "0x000000000000000000000000abcd0001" > abcd0008_kek0.txt …

Hi, We have this supported in r32.5. Please first do this: sudo ./odmfuse.sh -i 0x18 -k <PKC key> -S <SBK file> -p --test jetson-tx2 If it works, remove the “–test” in the command line and odmfuse.sh will really do the burning.

Hi, Please share the information of executing tegrafuse.sh After runing with -p, the key should be invisible. Also please try to set BOARDID=3310 FAB=C04 in executing odmfuse.sh

[image] DaneLLL: Please share the information of executing tegrafuse.sh Hi, here’s the result. It’s still visible. $ sudo ./tegrafuse.sh [sudo] password for nvidia: Unsupported fuse: device_key Unsupported fuse: jtag_disable odm_lock : 0x00000000 odm_production_mode : 0x00000000 Unsupport…

[image] DaneLLL: Also please try to set BOARDID=3310 FAB=C04 in executing odmfuse.sh I didn’t make a difference. $ sudo BOARDID=3310 FAB=C04 ./odmfuse.sh -j -i 0x18 -c PKC -k ../abcd0008.pem --KEK0 ../abcd0008_kek0.txt -p jetson-tx2 [sudo] password for tsato: ./tegraflash.py --chip 0x18 --a…

Hi, We have checked status of tegrafuse. It looks like the TX2 is in a condition not being considered. We will see if we can handle it in odmfuse.sh. Will update.

[image] DaneLLL: It looks like the TX2 is in a condition not being considered. We will see if we can handle it in odmfuse.sh. Will update. I see, thanks for checking.

Hi, I have the same issue. I have managed to burn necessary keys without odm_production (details in this post ). Now I try to burn only odm_production fuse: sudo ./odmfuse.sh -j -i 0x18 -c PKC -p jetson-tx2 but get this error: [ 0.0052 ] RCM 0 is saved as rcm_0.rcm [ 0.0058 ] RCM 1 is saved…

Hi, [image] nazaraa: Could anybody confirm the success of burning fuses with R32.3.1 ? I succeed only with R32.2.1 . I have confirmed it won’t succeed with 32.3.1 as described in my another post .

Hi @TakenoriSato For more information, do you touch odmfuse.sh? Or use default one in r32.2.3?

Fuse burning failure after a successful KEK0

Robotics & Edge Computing Jetson Systems Jetson TX2

TakenoriSato March 31, 2020, 11:51pm 14

As described here, the patch was applied when executing odmfuse.sh. Without it, the odmfuse.sh process always gets stuck and nothing happens on TX2.

Topic		Replies	Views
Unable to burn fuses (dev kit) / no more output (serial/hdmi) / bricked? Jetson AGX Xavier security , nvbugs	92	7722	May 26, 2020
KEK Fuse burn failed on Jetson Xavier R32.3.1 Jetson AGX Xavier security , nvbugs	9	1932	May 20, 2020
How to burn ODM fuse bits (TX2)? Jetson TX2 security	29	3107	May 3, 2020
Secure Boot odmfuse programming step fail on 32.2.1 Jetson TX2	19	2986	February 6, 2020
Problems with burning Jetson TX2 keys Jetson TX2	13	1856	March 16, 2021
Concerns about fuse burning on TX2 Jetson TX2 security , nvbugs	31	4131	September 1, 2021
Secure Boot TX2i Jetson TX2 security	3	1423	March 12, 2021
Odmefuse.sh not burning SBK key Jetson TX2 security , nvbugs	40	1957	April 16, 2024
TX2NX fuse noburn doesn't generate public key in odmfuse_pck.xml Jetson TX2 security	3	693	November 10, 2022
How to burn ODM fuse bits? Jetson Nano	22	4794	April 20, 2020

Fuse burning failure after a successful KEK0

Related topics