eFuse Configurations#

The following table shows the programmable eFuse (OTP) configuration fields. These configurations can only be done in eFuse (OTP).

S.no Field Description Number of bits Default Setting in OTP Is a security feature?
1 ta_otp_lock_r1

This is a programming lock for the NWP OTP, specifically for the R1 address region (0–127). When the OTP is locked, the user cannot modify the secure boot-related parameters present in the R1 address region.

1: NWP OTP programming is locked

0: NWP OTP programming is not locked

 1 0 Yes
2 "otp_lock_1": {
  "debug_port_opened": 0,
  "section_lock_128_255": 0
}

This is a programmable lock for the NWP OTP, specifically for the R2 address region (128–255). When the OTP is locked, users cannot modify the secure boot-related parameters present in the R2 address region.

1: NWP OTP programming is locked

0: NWP OTP programming is not locked

 1 0 Yes
3 "otp_lock_2": {
  "section_lock_256_767": 0
}

This is a programmable lock for the NWP OTP, specifically for the R3 address region (256–767). When the OTP is locked, users cannot modify the secure boot-related parameters present in the R3 address region.

1: NWP OTP programming is locked

0: NWP OTP programming is not locked

 1 0 Yes
4 "otp_lock_3": {
  "section_lock_768_1023": 0
}

This is a programmable lock for the NWP OTP, specifically for the R4 address region (768–1024). When the OTP is locked, users cannot modify the secure boot-related parameters present in the R4 address region.

1: TA OTP programming is locked

0: TA OTP programming is not locked

 1 0 Yes