Orinnx 16G fuse error

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
1

JP: 5.13
Hardware: Orinnx 16G

I run test fusing command :
sudo ./odmfuse.sh --test -X keys/sbkpkc_keys/fuse.conf -i 0x23 jetson-orin-nano-devkit

The serial port log:
Start BootSecurityInfo burn Tried to set fuse bit 0 from 1 to 0 Error =
0x17173402 in tegrabl_fuse_write
Failed to burn BootSecurityInfo Fail to burn fuses as per fuse info
FSKP: Failed to burn fuse.
Task 0x0 failed(err: 0x62173402)
Top caller module: FSKP, error module: FUSE, reason: 0x02, aux_info: 0x34
Busy Spin

I check the BootSecurityInfo by run “sudo nv_fuse_read.sh”

find:
boot_security_info: 0x000001e0

is not same as others’ default value
boot_security_info: 0x00000000

1, Why the boot_security_info default value is 0x000001e0 not the
0x00000000?
Does the boot_security_info has any other default value except “0x00000000” or “0x000001e0” ?

2, The boot_security_info in Our fuse config file is config 0x209 and I use it to burn keys into our board and it failed but I can get PKChash, how to recovery it.

3, Our many boards have burt boot_security_info as 0x209, but now the orinnx has defaut 0x000001e0 , that let us can’t burn 0x209. We don’t want our fuse config file has different values, how to change the boot_security_info
from 0x000001e0 to 0x00000000 to burn 0x209.

pls help us to check it.

3

it looks duplicated, please refer to Topic 336014.

4

1、I want to know why there are different default values for FUSE_BOOT_SECURITY_INFO_0?
2、The default value of the old module is 0. We have already burned it. How can we change it?
3、Currently, the incoming materials have both 0 values and 0x1e0. How can we distinguish and be compatible with the burning process?

5

hello Zhang.Sir,

if you’re having the modules around the beginning of 2025. the BOOT_SECURITY_INFO was burned (by manufacturing) to 0x1E0 as default value.

as mentioned, please update your fuse configuration file, especially the BootSecurityInfo.
for instance, please fuse devices (both new and old modules) with a BootSecurityInfo value by doing an OR with 0x1E0.

6

How to update both new and old modules？Is it also suitable for those that have already been burned?
Tools is？If value is 0x1e0, the current tool will report errors when burning and cannot burn.

7

all right, let me re-cap again…