Secure Boot

Applies to the Jetson Orin NX and Nano series, Jetson AGX Orin series, the Jetson Xavier NX series, and the Jetson AGX Xavier series.

NVIDIA^® Jetson™ Linux provides boot security. Secure Boot prevents execution of unauthorized boot codes through the chain of trust. The root-of-trust is an on-die BootROM code that authenticates boot codes such as BCT, Bootloader, and warm boot vector using Public Key Cryptography (PKC) keys stored in write-once-read-multiple fuse devices. On Jetson platforms that support Secure Boot Key (SBK), you can use it to encrypt Bootloader images.

NVIDIA SoCs contain multiple fuses that control different items for security and boot.

The Jetson BSP package contains program scripts/tools and instructions to provide security services during the booting.

The root-of-trust that uses the NVIDIA SoCs fuses to authenticate boot codes ends at the Bootloader. After this, the current Bootloader (UEFI) will use UEFI’s Security Keys scheme to authenticate its payloads

To enable UEFI Secureboot, refer to UEFI Secureboot.

Overall Fusing and Signing Binaries Flow

The Secure Boot process with PKC and SBK requires you to:

Generate a PKC key pair.
Prepare an SBK key.
Prepare KEK keys.
Prepare the Fuse Configuration file.
Burn fuses using odmfuse.sh script with a Fuse Configuration file.
Flash the device with secured images (using flash.sh with -u -v options).

Prerequisites Secure Boot

An X86 host running Ubuntu 18.04 LTS, or 20.04 LTS.
libftdi-dev for USB debug port support.
openssh-server package for OpenSSL.
Full installation of the latest Jetson Linux release on the host.
A USB cable connecting the Jetson device to the host.
If necessary, a USB cable that connects the Jetson device’s debug serial port to the host.

Fuses and Security

NVIDIA SoCs contain multiple fuses that control different items for security and boot. Once a fuse bit is set to 1, you cannot change its value back to 0. For example, a fuse value of 1 (0x01) can be changed to 3 (0x03) or 5 (0x05), but not to 4 (0x4) because bit 0 is already programmed to 1.

After the SecurityMode (also known as odm_production_mode) fuse is burned with a value of 0x1, all additional fuse write requests will be blocked.

However, some of the ODM fuses are still writable. For more details, refer to the specific SoC fuses documents.

To burn fuses, you can use the odmfuse.sh script with a fuse configuration file.

The fuse configuration file is an XML file that contains the fuse data to be burned.

Fuse Configuration File

The fuse configuration file, which is an XML file, contains the fuse data, a list of fuses, and the value to be burned in each fuse.

The odmfuse.sh tool uses this XML file to program the fuses.

A fuse configuration file contains a <genericfuse> </genericfuse> tag pair, which contains one <fuse/> tag for each fuse to be burned.

The following template shows the format of the file:

<genericfuse MagicId="0x45535546" version="1.0.0">
    <fuse name="<name>" size="<size>" value="<value>"/>
    <fuse name="<name>" size="<size>" value="<value>"/>
    . . .
</genericfuse>

Where:

<name> is the name of a fuse. Supported fuse names are listed in the SoC’s Reference Fuse Configuration File.

For Orin SoC, refer to Orin Reference Fuse Configuration File

For Xavier SoC, refer to Xavier Reference Fuse Configuration File

<size> is the size of the fuse in bytes.

<value> is the value to be burned into the fuse, with two hexadecimal digits per byte.

MagicId of “0x45535546” is used by the target-binary and must not be changed.

odmfuse.sh script burns fuses in the order that they appear in the fuse configuration file. If two or more fuses’ values are interdependent, the independent fuses must be specified before the dependent one so that they are burned first. That is, if the values that can be burned into fuse Y depend on the value of fuse X, the fuse configuration file must specify fuse X first and then Y. This way, the odmfuse.sh script will burn fuse X first.

Caution

The odmfuse.sh fuse burning tool does not check for dependencies, so specifying a dependent fuse before the fuse it depends on might render the target device inoperable. Check the fuse list’s order carefully before you burn the fuses.

Note

Although the fuse configuration file contains XML tags, it does not need the “<?xml… ?>” prolog defined by the XML standard. Fuse configurations might not have a prolog. If you want to run general purpose XML utilities on such a file, you might have to add a prolog.

Each SoC has its own specific fuses and fuse names.

For details on fuses and fuse names for each SoC, refer to the following documents:

For Jetson Orin series: Jetson Orin Fuse Specification Application Note
For Jetson Xavier series: Jetson AGX Xavier Series Fuse Programming Application Note

Note

These Application Note documents can be found in the following page:

https://developer.nvidia.com/embedded/downloads#?search=fuse

The following sections describe the Fuse Configuration Files for each SoC.

For Jetson Orin SoC, refer to Orin Reference Fuse Configuration File.

For Jetson Xavier SoC. refer to Xavier Reference Fuse Configuration File.

Jetson Orin Fuse Configuration File

Refer to Jetson Orin Fuse Specification Application Note for Jetson Orin Series (AGX, NX, and Nano) for more information about fuses and fuse names for Orin SoC.

Example Orin Fuse Configuration File to Program an RSA-3K Key

Example fuse configuration file to enable Secure Boot with an RSA-3K key:

<genericfuse MagicId="0x45535546" version="1.0.0">
    <fuse name="PublicKeyHash" size="64" value="0x18e984f7d79f7a185039ec413ed2ff86227c8f0be639edde0cf23ab1f7910b759ede8fb0c20d02c68deb04a75226d632f9fe24c71dad4b302acdba13db658130"/>
    <fuse name="BootSecurityInfo" size="4" value="0x1"/>
    <fuse name="SecurityMode" size="4" value="0x1"/>
</genericfuse>

Note

Jetson Orin series targets support RSA-3K key only.

Note

The value above for “PublicKeyHash” is for demonstrations only.

Refer to Generate PublicKeyHash value from a PKC key pair for more information about generating the PublicKeyHash fuse value.

Example Orin Fuse Configuration File to Program an ECDSA P-256 Key

Example fuse configuration file to enable Secure Boot with an ECDSA P-256 key:

<genericfuse MagicId="0x45535546" version="1.0.0">
    <fuse name="PublicKeyHash" size="64" value="0x3c67c6446176bab0a35c09fa77c77c14f2c690dad4f5afcbc6a5ac3c39a0231e192eea1aab469e086ffd42eded658d2317583d6b39bedb2e2ca3c5d0d09bcbea"/>
    <fuse name="BootSecurityInfo" size="4" value="0x2"/>
    <fuse name="SecurityMode" size="4" value="0x1"/>
</genericfuse>

Note

The value above for “PublicKeyHash” is for demonstrations only.

Refer to Generate PublicKeyHash value from a PKC key pair for more information about generating the PublicKeyHash fuse value.

Example Orin Fuse Configuration File to Program an ECDSA P-521 Key + SBK Key + OemK1 Key

The following sample configuration file is used to enable the Secure Boot with an ECDSA P-521 key, an SBK key, and an OemK1 key:

<genericfuse MagicId="0x45535546" version="1.0.0">
    <fuse name="PublicKeyHash" size="64" value="0x9f0ebf0aec1e2bb30c0838096a6d9de5fb86b1277f182acf135b081e345970167a88612b916128984564086129900066255a881948ab83bebf78c7d627f8fe84"/>
    <fuse name="SecureBootKey" size="32" value="0x123456789abcdef0fedcba987654321000112233445566778899aabbccddeeff"/>
    <fuse name="OemK1" size="32" value="0xf3bedbff9cea44c05b08124e8242a71ec1871d55ef4841eb4e59a56b5f88fb2b"/>
    <fuse name="BootSecurityInfo" size="4" value="0x20b"/>
    <fuse name="SecurityMode" size="4" value="0x1"/>
</genericfuse>

Note

The values of PublicKeyHash, SecureBootKey, and OemK1 above are for demonstrations only.

Refer to Generate PublicKeyHash value from a PKC key pair for more information about generating the PublicKeyHash fuse value.

Refer to Prepare an SBK key for more information about generating the SecureBootKey fuse value.

Refer to Prepare K1/K2/KEK keys for more information about generating the OemK1 fuse value.

Orin Reference Fuse Configuration File

The Orin Reference Fuse Configuration file lists all fuses that are supported by the Orin SoC.

All fuse values in the reference configuration file are enclosed in XML comments. To adapt the reference file for fusing, uncomment them and replace their “0xFFFF” placeholder values with the actual values for your target.

Here is the Reference Fuse Configuration File for Jetson Orin devices:

<genericfuse MagicId="0x45535546" version="1.0.0">
    <!-- <fuse name="OdmId" size="8" value="0xFFFFFFFFFFFFFFFF"/> -->
    <!-- <fuse name="OdmInfo" size="4" value="0xFFFF"/> -->
    <!-- <fuse name="ArmJtagDisable" size="4" value="0x1"/> -->
    <!-- <fuse name="DebugAuthentication" size="4" value="0x1F"/> -->
    <!-- <fuse name="CcplexDfdAccessDisable" size="4" value="0x1"/> -->
    <!-- <fuse name="ReservedOdm0" size="4" value="0xFFFFFFFF"/> -->
    <!-- <fuse name="ReservedOdm1" size="4" value="0xFFFFFFFF"/> -->
    <!-- <fuse name="ReservedOdm2" size="4" value="0xFFFFFFFF"/> -->
    <!-- <fuse name="ReservedOdm3" size="4" value="0xFFFFFFFF"/> -->
    <!-- <fuse name="OdmLock" size="4" value="0xF"/> -->
    <!-- <fuse name="ReservedOdm4" size="4" value="0xFFFFFFFF"/> -->
    <!-- <fuse name="ReservedOdm5" size="4" value="0xFFFFFFFF"/> -->
    <!-- <fuse name="ReservedOdm6" size="4" value="0xFFFFFFFF"/> -->
    <!-- <fuse name="ReservedOdm7" size="4" value="0xFFFFFFFF"/> -->
    <!-- <fuse name="SecureProvisionInfo" size="4" value="0x3"/> -->
    <!-- <fuse name="OptInEnable" size="4" value="0x1"/> -->
    <!-- <fuse name="SwReserved" size="4" value="0xFFFFFF"/> -->
    <!-- <fuse name="BootDevInfo" size="4" value="0xFFFFFF"/> -->
    <!-- <fuse name="ZeroizeDis" size="4" value="0x1"/> -->
    <!-- <fuse name="PublicKeyHash" size="64" value="0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF"/> -->
    <!-- <fuse name="PkcPubkeyHash1" size="64" value="0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF"/> -->
    <!-- <fuse name="PkcPubkeyHash2" size="64" value="0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF"/> -->
    <!-- <fuse name="EndorseKey" size="68" value="0x1FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF"/> -->
    <!-- <fuse name="SecureBootKey" size="32" value="0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF"/> -->
    <!-- <fuse name="Kdk0" size="32" value="0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF"/> -->
    <!-- <fuse name="PscOdmStatic" size="4" value="0xFFFFFFFF"/> -->
    <!-- <fuse name="OemK1" size="32" value="0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF"/> -->
    <!-- <fuse name="OemK2" size="32" value="0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF"/> -->
    <!-- <fuse name="BootSecurityInfo" size="4" value="0xFFFFFFFF"/> -->
    <!-- <fuse name="SecurityMode" size="4" value="0x1"/> -->
</genericfuse>

Note

Although the size of the “OdmInfo” fuse is 4, only the last two bytes are programmable.

Jetson Xavier NX and Jetson AGX Xavier Fuse Configuration Files

For details on hardware fuses and fuse names, refer to the following documents:

For Jetson Xavier NX series: Jetson Xavier NX Fuse Specification Application Note
For Jetson AGX Xavier series: Jetson AGX Xavier Series Fuse Programming Application Note

Example Xavier Fuse Configuration File to Program the RSA-2K Key

The following sample configuration file is used to enable Secure Boot with RSA-2K key:

 <genericfuse MagicId="0x45535546" version="1.0.0">
     <fuse name="PublicKeyHash" size="32" value="0x3cd0ac90ca94ca6edf8b131befa93799022e8bb5edd0a523ce78d46a3b4ce433"/>
     <fuse name="BootSecurityInfo" size="4" value="0x01"/>
     <fuse name="SecurityMode" size="4" value="0x1"/>
</genericfuse>

Note

Jetson AGX Xavier series and Jetson Xavier NX series targets support both RSA-2K and RSA-3K key.

Note

The value above for PublicKeyHash is for demonstrations only.

Refer to Generate PublicKeyHash value from a PKC key pair for more information about generating the PublicKeyHash fuse value.

Example Xavier Fuse Configuration File to Program the RSA-3K Key + SBK Key + KEK Key

The following sample configuration file is used to enable Secure Boot with RSA-3K key, SBK key and KEK keys:

<genericfuse MagicId="0x45535546" version="1.0.0">
    <fuse name="PublicKeyHash" size="32" value="0x999585e628c285a5dfdd2bd201fa878d8e62e6c4eb842d81d1a026b22cd6e8f0"/>
    <fuse name="Kek0" size="16" value="0x112233445566778899AABBCCDDEEFF00"/>
    <fuse name="Kek1" size="16" value="0x123456789ABCDEF0FEDCBA9876543210"/>
    <fuse name="SecureBootKey" size="16" value="0x123456789ABCDEF0FEDCBA9876543210"/>
    <fuse name="BootSecurityInfo" size="4" value="0x06"/>
    <fuse name="SecurityMode" size="4" value="0x1"/>
</genericfuse>

Note

The values above of PublicKeyHash, SecureBootKey, Kek0 and Kek1 are for demonstrations only.

Refer to Generate PublicKeyHash value from a PKC key pair for more information about generating the PublicKeyHash fuse value.

Refer to Prepare an SBK key for more information about generating the SecureBootKey fuse value.

Refer to Prepare K1/K2/KEK keys for more information about generating the Kek0 and Kek1 fuse values.

Xavier Reference Fuse Configuration File

The Xavier Reference Fuse Configuration file lists all fuses that are supported by Xavier SoC.

All fuse values in the reference configuration file are enclosed in XML comments. To adapt the reference file for fusing, uncomment them and replace their “0xFFFF” placeholder values with the actual values for your target.

Following shows the Xavier Reference Fuse Configuration file for Jetson Xavier NX and Jetson AGX Xavier devices:

<genericfuse MagicId="0x45535546" version="1.0.0">
    <!-- <fuse name="OdmId" size="8" value="0xFFFFFFFFFFFFFFFF"/> -->
    <!-- <fuse name="Odm_info" size="4" value="0xFFFF"/> -->
    <!-- <fuse name="ReservedOdm0" size="4" value="0xFFFFFFFF"/> -->
    <!-- <fuse name="ReservedOdm1" size="4" value="0xFFFFFFFF"/> -->
    <!-- <fuse name="ReservedOdm2" size="4" value="0xFFFFFFFF"/> -->
    <!-- <fuse name="ReservedOdm3" size="4" value="0xFFFFFFFF"/> -->
    <!-- <fuse name="OdmLock" size="4" value="0xF"/> -->
    <!-- <fuse name="ReservedOdm4" size="4" value="0xFFFFFFFF"/> -->
    <!-- <fuse name="ReservedOdm5" size="4" value="0xFFFFFFFF"/> -->
    <!-- <fuse name="ReservedOdm6" size="4" value="0xFFFFFFFF"/> -->
    <!-- <fuse name="ReservedOdm7" size="4" value="0xFFFFFFFF"/> -->
    <!-- <fuse name="JtagDisable" size="4" value="0x1"/> -->
    <!-- <fuse name="SwReserved" size="4" value="0xFFFFFF"/> -->
    <!-- <fuse name="BootDevInfo" size="4" value="0xFFFFFF"/> -->
    <!-- <fuse name="SecureProvisionInfo" size="4" value="0x3"/> -->
    <!-- <fuse name="EndorsementKey" size="32" value="0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF"/> -->
    <!-- <fuse name="DebugAuthentication" size="4" value="0x1F"/> -->
    <!-- <fuse name="CcplexDfdAccessDisable" size="4" value="0x1"/> -->
    <!-- <fuse name="Kek0" size="16" value="0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF"/> -->
    <!-- <fuse name="Kek1" size="16" value="0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF"/> -->
    <!-- <fuse name="Kek2" size="16" value="0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF"/> -->
    <!-- <fuse name="Kek256" size="32" value="0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF"/> -->
    <!-- <fuse name="PublicKeyHash" size="32" value="0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF"/> -->
    <!-- <fuse name="SecureBootKey" size="16" value="0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF"/> -->
    <!-- <fuse name="BootSecurityInfo" size="4" value="0xFFFF"/> -->
    <!-- <fuse name="SecurityMode" size="4" value="0x1"/> -->
</genericfuse>

Note

Although the size of the “Odm_info” fuse is 4, only the last two bytes are programmable.

Generate A PKC Key Pair

Jetson Orin series targets support the PKC of RSA 3K, ECDSA P-256, and ECDSA P-521.

Jetson Xavier series targets support the PKC of RSA 2K and RSA 3K keys.

Note

The 2048-bit RSA key option is no longer supported on Jetson Orin series.

Enter one of the following commands to generate a PKC key pair:

To generate an ECDSA P-256 key:

$ openssl ecparam -name prime256v1 -genkey -noout -out ecp256.pem

To generate an ECDSA P-521 key:

$ openssl ecparam -name secp521r1 -genkey -noout -out ecp521.pem

To generate an RSA 2K key:

$ openssl genrsa -out rsa_priv.pem 2048

To generate an RSA 3K key:

$ openssl genrsa -out rsa_priv.pem 3072

Rename and save the key file.

The key file is used to burn fuses and sign boot files for Jetson devices.

Caution

The security of your device depends on how securely you keep the key file.

Note

To generate a truly random number key, use the Hardware Security Module (HSM).

Generate `PublicKeyHash` value from a PKC key pair

Instead of fusing the public key of a PKC key pair, only the hash of the public key is burned to the PublicKeyHash fuse field.

To generate the PublicKeyHash value, use the tegrasign_v3.py program:

$ ./tegrasign_v3.py --pubkeyhash <pkc.pubkey> <pkc.hash> --key <pkc.pem>

Where:

<pkc.pem> is the input pkc key pair (.pem file) file.

<pkc.pubkey> is the output public key of the ``<pkc.pem> key pair

<pkc.hash> is the output public key hash of the ``<pkc.pem> key pair

The hexadecimal value shown on the screen after tegra-fuse format (big-endian): can be used directly as the PublicKeyHash fuse data of a Fuse Configuration file.

Here are some sample outputs after running tegrasign_v3.py to generate PublicKeyHash for an ECDSA P-521 key:

$ ./tegrasign_v3.py --pubkeyhash ecp521.pubkey ecp521.hash --key ecp521.pem
  Valid ECC key. Key size is 521
  Valid ECC key. Key size is 521
  Saving public key in ecp521.pubkey for ECC
  Sha saved in pcp.sha
  tegra-fuse format (big-endian): 0x9f0ebf0aec1e2bb30c0838096a6d9de5fb86b1277f182acf135b081e345970167a88612b916128984564086129900066255a881948ab83bebf78c7d627f8fe84

Here are some sample outputs after running tegrasign_v3.py to generate PublicKeyHash for an RSA 3k key:

$ ./tegrasign_v3.py --pubkeyhash rsa3k.pubkey rsa3k.hash --key rsa3k.pem
Key size is 384 bytes
Key size is 384 bytes
Saving pkc public key in foo.pubkey
Sha saved in pcp.sha
tegra-fuse format (big-endian): 0xad2474627c14e3f7f4944a832bd15d0640938a3dc162f558692458f3d12f9453e11bea2ec75df3f83e8b29c47fc3d2483d528d3e94a5469c4ba1ec61f1584b23

Note

tegrasign_v3.py can only be used to generate PublicKeyHash for the Jetson AGX Orin series, the Jetson Orin NX, and the Nano series.
RSA2K is not supported on the Jetson AGX Orin series, the Jetson Orin NX, and the Nano series.

For an RSA key, you can also use tegrakeyhash program to generate PublicKeyHash value:

./tegrakeyhash --pkc <pkc.pem> --chip <chip_id>

Where:

<pkc.pem> is the RSA key pair (.pem file) file.

<chip_id> is 0x23 for the Jetson Orin series and is 0x19 for the Jetson Xavier series.

The hexadecimal value shown on the screen after tegra-fuse format (big-endian): can be used directly as PublicKeyHash fuse data of a Fuse Configuration file.

Note

tegrakeyhash program generates 64 bytes of PublicKeyHash value for Orin SoC (chip_id of 0x23).

tegrakeyhash program generates 32 bytes of PublicKeyHash value for Xavier SoC (chip_id of 0x19).

Here are some sample outputs after running tegrakeyhash to generate PublicKeyHash:

$ ./tegrakeyhash --pkc rsa_priv-3k.pem --chip 0x23
Key size is 384 bytes
sha512 hash:
bytes:
0x18, 0xe9, 0x84, 0xf7, 0xd7, 0x9f, 0x7a, 0x18,
0x50, 0x39, 0xec, 0x41, 0x3e, 0xd2, 0xff, 0x86,
0x22, 0x7c, 0x8f, 0x0b, 0xe6, 0x39, 0xed, 0xde,
0x0c, 0xf2, 0x3a, 0xb1, 0xf7, 0x91, 0x0b, 0x75,
0x9e, 0xde, 0x8f, 0xb0, 0xc2, 0x0d, 0x02, 0xc6,
0x8d, 0xeb, 0x04, 0xa7, 0x52, 0x26, 0xd6, 0x32,
0xf9, 0xfe, 0x24, 0xc7, 0x1d, 0xad, 0x4b, 0x30,
0x2a, 0xcd, 0xba, 0x13, 0xdb, 0x65, 0x81, 0x30,

tegra-fuse format (big-endian):
0x18e984f7d79f7a185039ec413ed2ff86227c8f0be639edde0cf23ab1f7910b759ede8fb0c20d02c68deb04a75226d632f9fe24c71dad4b302acdba13db658130

fuse bypass format:
FAB_ENTRY(PUBLIC_KEY0, PUBLIC_KEY0, 0xf784e918),
FAB_ENTRY(PUBLIC_KEY1, PUBLIC_KEY1, 0x187a9fd7),
FAB_ENTRY(PUBLIC_KEY2, PUBLIC_KEY2, 0x41ec3950),
FAB_ENTRY(PUBLIC_KEY3, PUBLIC_KEY3, 0x86ffd23e),
FAB_ENTRY(PUBLIC_KEY4, PUBLIC_KEY4, 0x0b8f7c22),
FAB_ENTRY(PUBLIC_KEY5, PUBLIC_KEY5, 0xdeed39e6),
FAB_ENTRY(PUBLIC_KEY6, PUBLIC_KEY6, 0xb13af20c),
FAB_ENTRY(PUBLIC_KEY7, PUBLIC_KEY7, 0x750b91f7),
FAB_ENTRY(PUBLIC_KEY8, PUBLIC_KEY8, 0xb08fde9e),
FAB_ENTRY(PUBLIC_KEY9, PUBLIC_KEY9, 0xc6020dc2),
FAB_ENTRY(PUBLIC_KEY10, PUBLIC_KEY10, 0xa704eb8d),
FAB_ENTRY(PUBLIC_KEY11, PUBLIC_KEY11, 0x32d62652),
FAB_ENTRY(PUBLIC_KEY12, PUBLIC_KEY12, 0xc724fef9),
FAB_ENTRY(PUBLIC_KEY13, PUBLIC_KEY13, 0x304bad1d),
FAB_ENTRY(PUBLIC_KEY14, PUBLIC_KEY14, 0x13bacd2a),
FAB_ENTRY(PUBLIC_KEY15, PUBLIC_KEY15, 0x308165db),

Prepare an SBK key

An SBK key is used to encrypt Bootloader components. The same SBK key has to be fused to the Jetson’s SoC fuses, so the key can be used to decrypt the Bootloader components when the Jetson device boots up.

Note

You can only use the SBK key with the PKC key. The encryption mode that uses these two keys together is called SBKPKC.

The Orin SoC requires an SBK key be of eight 32-bit words (32 bytes). The Xavier SoC requires an SBK key be four 32-bit words (16 bytes).

The SBK key file is stored in big-endian hexadecimal format.

Here is an example of a 16-byte SBK key file:

0x12345678 0x9abcdef0 0xfedcba98 0x76543210

This type of file format is used in flash.sh command with -v option.

The same SBK representation used in the “SecureBootKey” fuse value field of a Fuse Configuration XML file is:

0x123456789abcdef0fedcba9876543210

Note

Hexadecimal numbers must be presented in big-endian format. The leading 0x or 0X can be omitted. The Jetson Secure Boot software converts the big-endian hexadecimal format to the format that the Jetson device expects. All standard OpenSSL utilities output in big-endian format.

We recommend that you use the Hardware Security Module (HSM) to generate a truly random number for an SBK key.

Caution

The security of your device depends on how securely you keep the key file.

Prepare K1/K2/KEK keys

The K1/K2/KEK keys are used for other security application, such as disk encryption/decryption, you must prepare these keys and other ODM fuse bits as described in the documentation for the other security application.

For Jetson Orin SoC, the fuse key names are OemK1 and OemK2, and the key length is 32 bytes.

For Jetson Xavier SoC, the fuse key names are Kek0, Kek1, Kek2, for which the key length is 16 bytes. Kek256 is a combination of Kek0 and Kek1 with a key length of 32 bytes.

These keys must be presented in Hexadecimal numbers and must be in the big-endian format.

Note

The leading 0x or 0X of a hexadecimal number can be omitted. The Jetson Secure Boot software converts the big-endian hexadecimal format to the format that the Jetson device expects.

These keys consist of eight (or four) 32-bit words stored in a file in the big-endian hexadecimal format.

Here is an example of an OemK1 key file:

0x11223344 0x55667788 0x99aabbcc 0xddeeff00 0xffeeddcc 0xbbaa9988 0x77665544 0x33221100

The same key representation in the OemK1 fuse value field in the Fuse Configuration XML file is:

0x112233445566778899aabbccddeeff00ffeeddccbbaa99887766554433221100

Note

We recommend that you use the HSM to generate a truly random number for KEK keys.

Caution

The security of your device depends on how securely you keep these key files.

Prepare the Fuse Configuration file

To modify the SoC’s Reference Fuse Configuration file, uncomment the fuses you need, and enter information in the correct fuse data fields for your target Jetson device.

The next section provides information about how to burn fuses with the prepared Fuse Configuration file.

Caution

The security of your device depends on how securely you keep the Fuse Configuration file.

Burn Fuses with the Fuse Configuration file

After the Fuse Configuration file is prepared, you can burn fuses using odmfuse.sh (-X option) script with the Fuse Configuration file:

sudo ./odmfuse.sh -X <fuse_config> -i <chip_id> <target_config>

If a Jetson board was previously burned with a PKC key <pkc.pem>, and the board needs to have additional fuses burned, run the following odmfuse.sh command with -k option:

sudo ./odmfuse.sh -X <fuse_config> -i <chip_id> -k <pkc.pem> <target_config>

Where:

<fuse_config> is the fuse configuration XML file.

<chip_id> is 0x23 for Jetson Orin and is 0x19 for Jetson Xavier.

<pkc.pem> is the RSA key pair (.pem file) that was fused to the board before.

<target_config> is the name of the configuration for your Jetson device and carrier board; see the table in Jetson Modules and Configurations.

Note

Fuse burning operations are high-risk because they cannot be reversed. NVIDIA strongly recommends that you use the --test option to verify fuse burning operations before you perform them.

When you add --test to an odmfuse.sh command, the command performs pre-burn processing and verification, but it does not actually burn the fuse. If the command reports the results you want, you can re-enter the command without --test and burn the fuse with greater confidence that you are doing it correctly.

Read Fuses through the Linux kernel

To read the fuse values through the Linux kernel, run the /usr/sbin/nv_fuse_read.sh script.

To display the script usage, run the following command:

sudo nv_fuse_read.sh -h

To list the supported fuses in this script, run the following command:

sudo nv_fuse_read.sh -l

To read the value of a fuse, run the following command:

sudo nv_fuse_read.sh <fuse name>

For example, the following command can be used to get the ECID of the Jetson board:

sudo nv_fuse_read.sh ecid

To read all fuse values, run the following command:

sudo nv_fuse_read.sh

Sign and Flash Secured Images

The procedures described in this section use the following placeholders in their commands:

<pkc_keyfile> is an RSA 2K or 3K key file.
<sbk_keyfile> is an SBK key file.
<target_config> is the name of the configuration for your Jetson device and carrier board; see the table in Jetson Modules and Configurations.

Sign and Flash Secured Images in One Step

For Jetson Orin and Xavier series

Navigate to the directory where you installed Jetson Linux.
Place the Jetson device into Recovery mode.

Enter the following command:

$ sudo ./flash.sh -u <pkc_keyfile> [-v <sbk_keyfile>] <target_config> mmcblk0p1

Note

If the -v command option is specified, the -u command option also must be specified.

If the -v command option is omitted, all images flashed to the Jetson device are not encrypted.

If the -u command option is omitted, all images flashed to the Jetson device are not signed.

Caution

None of the PKC key file and SBK key file can be placed under the bootloader directory.

For example,

To flash a PKC-fused Jetson AGX Orin target:
$ sudo ./flash.sh -u <pkc_keyfile> jetson-agx-orin-devkit mmcblk0p1
To flash an SBKPKC-fused Jetson AGX Orin target:
$ sudo ./flash.sh -u <pkc_keyfile> -v <sbk_keyfile> jetson-agx-orin-devkit mmcblk0p1
To flash an SBKPKC-fused Jetson AGX Xavier target:
$ sudo ./flash.sh -u <pkc_keyfile> -v <sbk_keyfile> jetson-agx-xavier-devkit mmcblk0p1

Sign and Flash Secured Images in Separate Steps

Sign/encrypt the boot files:
```
$ sudo ./flash.sh --no-flash -u <pkc_keyfile> [-v <sbk_keyfile>] <target_config> mmcblk0p1
```
Note

If -v command option is specified, -u command option must be specified also.

If -v command option is omitted, all images flashed to the Jetson device are not encrypted.

If -u command option is omitted, all images flashed to the Jetson device are not signed.

Flash the generated encrypted/signed images:

$ cd bootloader
$ sudo bash ./flashcmd.txt

Note

Ensure that you place the Jetson device into Recovery mode before executing flashcmd.txt command.

Revocation of the PKC Keys

Applies only to the Jetson Orin NX series, the Jetson Orin Nano series, and the Jetson AGX Orin series.

The Orin SoC supports three PKC public keys and provides a revoking mechanism if a key is compromised after the product is shipped.

Here is some information about these keys:

These PKC keys must be of the same type and strength.
These keys are OEM programmable and the SHA2-512 hashes of the keys are burned into the fuses (FUSE_PUBLIC_KEY, FUSE_PK_H1 and FUSE_PK_H2) by the OEM during the manufacturing process. (Use the corresponding fuse name of PublicKeyHash, PkcPubkeyHash1, PkcPubkeyHash2 in the Fuse Configuration XML file.)
To enable ratchet, FUSE_OPT_CUSTOMER_OPTIN_FUSE (Fuse Configuration file XML entry: <fuse name=”OptInEnable” size=”4” value=”0x1” />) must be burned. This is to prevent running an earlier versions of the software, which compromises the revocation effect.
The keys are always active until they are revoked, and SoC will accept images signed with any of the non-revoked keys.
The last key (FUSE_PK_H2) is not revocable, and the system can always boot with images signed with the private key of the last key.
To revoke the first PKC (FUSE_PUBLIC_KEY) key:
1. Add revoke_pk_h0 = <1> to the brbct section of the <br_bct.dts> file of your target board.
2. Use the second PKC private key or the last PKC private key as the sign key in -u option in flash.sh.
To revoke the second PKC (FUSE_PK_H1) key:
1. Add revoke_pk_h1 = <1> to the brbct section of the <br_bct.dts> file of your target board.
2. Use the last PKC private key as the sign key in -u option in flash.sh.
After a key is revoked, it is permanently unusable. It can not be restored even the revoke_pk_h0 or revoke_pk_h1 is set to <0>.
To support PKC keys revocation, all three PKC keys must be fused at device provision.

Note

To find the <br_bct.dts> file of your target board, look for “DEV_PARAMS=” entry of your target board config file.

An Example: Fusing the Three PKC keys

Generate the rsa3k-0.pem, rsa3k-1.pem, and rsa3k-2.pem PKC keys:

$ openssl genrsa -out rsa3k-0.pem 3072

$ openssl genrsa -out rsa3k-1.pem 3072

$ openssl genrsa -out rsa3k-2.pem 3072

Generate the Hash values from the PKC keys:

$ ./tegrasign_v3.py --pubkeyhash rsa3k-0.pubkey rsa3k-0.hash --key rsa3k-0.pem

$ ./tegrasign_v3.py --pubkeyhash rsa3k-1.pubkey rsa3k-1.hash --key rsa3k-1.pem

$ ./tegrasign_v3.py --pubkeyhash rsa3k-2.pubkey rsa3k-2.hash --key rsa3k-2.pem

Create a Fuse Configuration file (fuse_rsa3k.xml):
1. Enter the hexadecimal public key hash that was generated from rsa3k-0.pem to the value field of the “PublicKeyHash” fuse name.
2. Enter the hexadecimal public key hash that was generated from rsa3k-1.pem to the value field of the “PkcPubkeyHash1” fuse name.
3. Enter the hexadecimal public key hash that was generated from rsa3k-2.pem to the value field of the “PkcPubkeyHash2” fuse name.

Note

Refer to Generate PublicKeyHash value from a PKC key pair for more information about generating the PublicKeyHash fuse value.

Here is an example Fuse Configuration file:

<genericfuse MagicId="0x45535546" version="1.0.0">
   <fuse name="SecureBootKey" size="32" value="0x123456789abcdef0fedcba987654321023456789abcdef01edcba9876543210f"/>
   <fuse name="PublicKeyHash" size="64" value="0xad2474627c14e3f7f4944a832bd15d0640938a3dc162f558692458f3d12f9453e11bea2ec75df3f83e8b29c47fc3d2483d528d3e94a5469c4ba1ec61f1584b23"/>
   <fuse name="PkcPubkeyHash1" size="64" value="0xd87796fb510d79738f8509c98511be0bb79dcc17d204a2f0f0bea9680b91bd1273ee2ae7a8a6bdb8b95deb0f421e72404939ae20d12c82649712283027201f39"/>
   <fuse name="PkcPubkeyHash2" size="64" value="0x99a5b6eac64dfb29698cb684165529e5d8650c1aab0e18b677c5d5f0998af53f8a8a1f09ad1d79368bc500e57eb199e9108fc7b1499995d869b028fec3f367db"/>
   <fuse name="OptInEnable" size="4" value="0x1"/>
   <fuse name="BootSecurityInfo" size="4" value="0x9"/>
   <fuse name="SecurityMode" size="4" value="0x1"/>
</genericfuse>

Burn the fuses with the Fuse Configuration file (fuse_rsa3k.xml):

$ sudo ./odmfuse.sh -X fuse_rsa3k.xml -i 0x23 jetson-agx-orin-devkit

Note

In the following examples, the sbk key is stored in file sbk-32.key with content:

0x12345678 0x9abcdef0 0xfedcba98 0x76543210 0x23456789 0xabcdef01 0xedcba987 0x6543210f

An Example: Revoking the First PKC key (rsa3k-0.pem)

Add revoke_pk_h0 = <1> to tegra234-br-bct-p3767-0000-l4t.dts:

/dts-v1/;

/ {
    brbct {
        . . .
        revoke_pk_h0 = <1>;
        bf_bl_allbits {
            . . .
        }
    };
};

Flash with rsa3k-1.pem or rsa3k-2.pem:

Option 1: rsa3k-1.pem

$ sudo ./flash.sh -u rsa3k-1.pem -v sbk-32.key jetson-agx-orin-devkit mmcblk0p1

Option 2: rsa3k-2.pem

$ sudo ./flash.sh -u rsa3k-2.pem -v sbk-32.key jetson-agx-orin-devkit mmcblk0p1

Use the UEFI Capsule update to revoke the first PKC key.
1. Generate the Capsule payload with the modified dts file. Refer to Generating the Capsule Update Payload for more information.
  
  Option 1: Generate the Capsule payload signed by the second PKC key rsa3k-1.pem
```
$ sudo ./l4t_generate_soc_bup.sh -u rsa3k-1.pem -v sbk-32.key -e t23x_agx_bl_spec t23x
$ ./generate_capsule/l4t_generate_soc_capsule.sh -i bootloader/payloads_t23x/bl_only_payload -o ./TEGRA_BL.Cap t234
```
  Option 2: Generate the Capsule payload signed by the third PKC key rsa3k-2.pem
```
$ sudo ./l4t_generate_soc_bup.sh -u rsa3k-2.pem -v sbk-32.key -e t23x_agx_bl_spec t23x
$ ./generate_capsule/l4t_generate_soc_capsule.sh -i bootloader/payloads_t23x/bl_only_payload -o ./TEGRA_BL.Cap t234
```
2. Trigger a Capsule update. Refer to Manually Trigger the Capsule Update for more information.

An Example: Revoking the Second PKC key (rsa3k-1.pem)

Add revoke_pk_h1 = <1> to tegra234-br-bct-p3767-0000-l4t.dts:

/dts-v1/;

/ {
    brbct {
        . . .
        revoke_pk_h1 = <1>;
        bf_bl_allbits {
            . . .
        }
    };
};

Flash with rsa3k-2.pem:

$ sudo ./flash.sh -u rsa3k-2.pem -v sbk-32.key jetson-agx-orin-devkit mmcblk0p1

Use the UEFI Capsule update to revoke the second PKC key.
1. Generate the Capsule payload with the modified dts file. Refer to Generating the Capsule Update Payload for more information.
$ sudo ./l4t_generate_soc_bup.sh -u rsa3k-2.pem -v sbk-32.key -e t23x_agx_bl_spec t23x $ ./generate_capsule/l4t_generate_soc_capsule.sh -i bootloader/payloads_t23x/bl_only_payload -o ./TEGRA_BL.Cap t234
1. Trigger a Capsule update. Refer to Manually Trigger the Capsule Update for more information.

Legacy Support of Secure Boot for Xavier SoC

Applies to the Jetson Xavier NX series and the Jetson AGX Xavier series only.

The following sections describe the legacy support for the Jetson Xavier NX and the Jetson AGX Xavier series only.

The following table describes user-programmable fuses that are related to Secure Boot for Xavier Soc.

Software and configuration fuses related to Secure Boot for NVIDIA^® Jetson Xavier™ NX series and NVIDIA^® Jetson AGX Xavier™ series
Bit size	Name	Default value set by `odmfuse.sh`
1	odm_production_mode	0x1.
256	public_key_hash	RSA public key hash.
128	secure_boot_key*	Secure Boot Key (SBK): AES encryption key for encrypting bootloader.
128	KEK0*	Four 32-bit register named KEK00 through KEK03.
128	KEK1*	Four 32-bit registers named KEK10 through KEK13.
256	KEK256	Not a distinct fuse; addresses KEK0 and KEK1 as a single 256-bit fuse.
128	KEK2*	Four 32-bit registers named KEK20 through KEK23.
* You can use `secure_boot_key` or the three Key Encryption Keys with different combinations of width as a key seed to encode keys. For example, KEK2 can be used as a key seed to encrypt and decrypted the Encrypted Key Blob (EKB) when TOS is enabled.

Here are the fuses that are handled by the user:

Bit size	Name	Default value set by odmfuse.sh
1	jtag_disable	0x0: JTAG is enabled (the default). 0x1: JTAG is disabled.
256	odm_reserved	Reserved fuses for the customer use. They are organized as 8 consecutive 32-bit fuses, `odm_reserved0` to `odm_reserved7`. `odm_reserved0` to `odm_reserved3` can be locked individually using corresponding bits in `odm_lock`.
4	odm_lock	Each bit set disables the write for the corresponding 32-bit odm_reserved fuses. For example: 0x2 locks bits 32−63 of `odm_reserved`, which corresponding to `odm_reserved1`.
8	sec_boot_dev_cfg	Depending on `sec_boot_dev_sel`, each bit has a different meaning.
24	sw_reserved	A bit map of configuration options. Bits not described here are reserved. Bits 2-0: `sec_boot_dev_sel`. 0=eMMC, 1=SPI. Meaningful only if `ignore_dev_sel_straps` (Bit 3) is set to 1. Bit 3: `ignore_dev_sel_straps`. 1=Ignore device selection boot straps, and use `sec_boot_dev_sel` (Bits 2-0) to select the boot device. Bit 5: `enable_watchdog`. Bit 23: 1=disable RCM mode

For details on hardware fuses and fuse names, refer to the following documents:

For Jetson Xavier NX series: Jetson Xavier NX Fuse Specification Application Note
For Jetson AGX Xavier series: Jetson AGX Xavier Series Fuse Programming Application Note

The following table describes the fuse name aliases that are recognized by tegraflash..

Fuse Name Aliases Recognized by tegraflash for Jetson Xavier NX series and Jetson AGX Xavier series
Name	tegraflash Alias and Notes
odm_production_mode	SecurityMode
public_key_hash	PublicKeyHash
secure_boot_key	Secure BootKey
Security_info	BootSecurityInfo
Key_encryption_key_0	Kek0
Key_encryption_key_1	Kek1
Key_encryption_key_256	Kek256
Key_encryption_key_2	Kek2
jtag_disable	JtagDisable
odm_reserved0, odm_reserved1,… odm_reserved7	`ReservedOdm0`, `ReservedOdm1`,… `ReservedOdm7` Customer programmable fuses; remain programmable after `FUSE_SECURITY_MODE` has been programmed. Default value (when no reserved ODM fuses have been programmed) is all zeros. One intended application of these fuses is software version revocation. You may use them for other purposes at your discretion.
odm_reserved8,… odm_reserved11	`ReservedOdm8`,… `ReservedOdm11` Reserved for use by NVIDIA. Do not use these fuses. Customer programming of these can result in boot failures and unexpected behavior.
odm_lock	`OdmLock` Each bit disables further changes to one of the `ReservedOdm` fuses. Only the first four `ReservedOdm` fuses can be disabled by this means. `OdmLock[0]` disables `ReservedOdm0` `OdmLock[1] disables` `ReservedOdm1` `OdmLock[2]` disables `ReservedOdm2` `OdmLock[3]` disables `ReservedOdm3`
sec_boot_dev_cfg	`SecBootDeviceSelect`
sw_reserved	`SwReserved`

Burning PKC, KEK, and SBK Fuses

To burn the PKC, KEK and SBK fuses by using a private key file PEM format:

Navigate to the host directory where you installed Jetson Linux.
Put the Jetson device into Force Recovery Mode.
Burn the fuse using the script odmfuse.sh. See odmfuse.sh Option Usage for illustrations of common operations.

Note

odmfuse.sh uses OpenSSL to burn PKC fuses.

odmfuse.sh Options

For fuses other than PKC key and odm_production_mode fuses, odmfuse.sh allows you to program ODM fuses that are completely at your discretion. Skip this topic if you do not plan to modify these fuses.

These are the odmfuse.sh command line options that blow ODM fuses:

Option	Description
-d 0xXXXX	Sets `sec_boot_dev_cfg=<value>&0x3fff.` For detail, see the Technical Reference Manual for your device’s processor.
-disable-jtag	Disables JTAG. Use this option to block use of the JTAG debugger.
-l 0xX	Sets `odm_lock` to the specified value. Setting each bit locks (makes read-only) the corresponding 32-bit word in the `odm_reserved` field. For example, setting `odm_lock` to 0x1 locks the first 32-bit word of `odm_reserved`. Setting `odm_lock` to 0x5 locks the first and third 32-bit words of `odm_reserved`, and so on.
–odm_reserved[0:7]	Sets `odm_reserved[n]` to the specified value. The value must be a quoted 32-bit (eight-digit) hexadecimal number in the form `0xnnnnnnnn`.
-p	Sets production mode.
-r 0xXX	Sets `sw_reserved=0xXX`. The bit definitions are: Bits 7-6: Reserved. Bit 5: Enable_watchdog. Bit 4: Reserved. Bit 3: `ignore_dev_sel_straps`: Ignore device selection boot straps. Bits 2-0: `sec_boot_dev_sel`: Boot device: 0=eMMC, 1=SPI.
-S <SBK_file>	Sets the Secure Boot key used to encrypt Bootloader and the TOS. The content of `<SBK_file>` must be four 32-bit big-endian numbers in hexadecimal format. This key must be used along with PKC key.
–noburn	Prepares the fuse blob to be used repeatedly on the factory floor. This option generates `Linux_for_Tegra/fuseblob.tbz2`, which can be downloaded and untarred in the `Linux_for_Tegra/` directory of a factory host. After `fuseblob.tbz2` is untarred in the `Linux_for_Tegra/` directory, `Linux_for_Tegra/bootloader/fusecmd.sh` is used to burn fuses repeatedly instead of the standard `odmfuse.sh`.
–KEK0 –KEK1 –KEK2 <path>	Pathname of the key encryption key file that other security applications are to use to encrypt and decrypt keys. The content of the file must be a single 128-bit big-endian number in hexadecimal format.
–KEK256 <path>	Pathname of the 256-bit Key Encryption Key file that the high-level security application will use to encrypt the application keys. The content of the file must be a single 256-bit big-endian number in hexadecimal format.
–auth <status>	Indicates the board’s current authentication status. Possible <status> values are: `NS`: not fused with PKC or SBKPKC, `PKC`: previously fused with PKC only, `SBKPKC`: previously fused with PKC and SBK. This option is only used when running `odmfuse.sh` with no boards connected (i.e. in offline mode) to generate a fuse blob for manufacturing. To run `odmfuse.sh` in offline mode: Use the command line option `--noburn`. Specify the carrier board by setting these environment variables on the command line. You can get the appropriate values from the Jetson module’s EEPROM as described in the “EEPROM Layout” topic for your Jetson device. `BOARDID`: Use the value of the “Board number” field. `FAB`: Use the value of the “FAB number” field. `BOARDSKU`: Use the value of the “SKU number” field. `BOARDREV`: Use the values of the “major revision” and “minor revision” fields, separated by a period. Examples: For a board that has not been fused with PKC and SBK keys: $ sudo FAB=400 BOARDID=2888 BOARDSKU=0006 \ BOARDREV=B.0 ./odmfuse.sh --noburn -i 0x19 \ --auth NS -p -k <pkc> --KEK2 <kek2> \ -S <sbk> jetson-xavier-devkit where, –auth NS: means no PKC or SBK keys burned -k <pkc>: to burn `PublicKeyHash` fuse -S <sbk>: to burn `SecureBootKey` fuse -p: to burn production mode fuse —KEK2 <kek2>: to burn `Kek2` fuse For a board that has PKC and SBK keys previously fused: $ sudo FAB=400 BOARDID=2888 BOARDSKU=0006 \ BOARDREV=B.0 ./odmfuse.sh --noburn -i 0x19 \ --auth SBKPKC -p -k <pkc> --KEK2 <kek2> \ -S <sbk> jetson-xavier-devkit where, –auth SBKPKC: means PKC and SBK keys were burned previously -k <pkc>: `PublicKeyHash` fuse was previously burned with <pkc> key -S <sbk>: `SecureBootKey` fuse was previously burned with <sbk> key -p: to burn production mode fuse —KEK2 <kek2>: to burn `Kek2` fuse
–test	Prevents the script from actually burning fuses. Pre-burn processing and tests are performed as usual. This option is normally used for fuse burning tests, since fuse values cannot be changed once they are burned.

Non-Destructive Testing for Fuse Burning Operations

Fuse burning operations are high-risk because they cannot be reversed. NVIDIA strongly recommends that you use the --test option to verify fuse burning operations before you perform them.

When you add --test to an odmfuse.sh command, the command performs pre-burn processing and verification, but it does not actually burn the fuse. If the command reports the results you want, you can enter the command again without --test and burn the fuse with greater confidence that you are doing it correctly.

odmfuse.sh Option Usage

To fuse PKC HASH from the .pem file with JTAG enabled:

$ sudo ./odmfuse.sh -i <chip_id> -p -k <key.pem> --KEK[0-2] <KEK file> -S <SBK_file> <target_config>

To fuse PKC HASH from the .pem file with JTAG disabled:

$ sudo ./odmfuse.sh -i <chip_id> -p -k <key.pem> --KEK[0-2] <KEK file> -S <SBK_file> --disable-jtag <target_config>

To burn a secure fuse with PKC, SBK, and KEK2:

$ sudo ./odmfuse.sh -i <chip_id> -p -k <PKC file> -S <SBK file> --KEK2 <KEK2 file> <target_config>

To burn a secure fuse with PKC and KEK2:

$ sudo ./odmfuse.sh -i <chip_id> -p -k <PKC file> --KEK2 <KEK2 file> <target_config>

Where:

<chip_id> is 0x19
<target_config> is the name of the configuration for the Jetson device and carrier board you are using, as shown in the Jetson Modules and Configurations table.

Signing and Flashing with initrd Using the l4t_initrd_flash.sh Script

Place the Jetson device into Force Recovery mode.
To sign the image, run the command:
```
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash -u <pkc_keyfile> [-v <sbk_keyfile>] <target_config> <rootdev>
```
Where (in addition to the placeholders described in Placeholders Used in the Procedures):
- <target_config> is the name of the configuration for that Jetson device and carrier board, specified by the environment variable BOARD. (See the table in Jetson Modules and Configurations
- <rootdev> specifies the device on which the root file system is located, as described in the topic Basic Flashing Script Usage.

To flash the target device, run the following command:

$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only -u <pkc_keyfile> [-v <sbk_keyfile>] <board_name> <rootdev>

Where <board_name> and <rootdev> are the same as in step 2, above.

UEFI Secureboot

UEFI Secureboot uses digital signatures (RSA) to validate the authenticity and integrity of the codes that it loads.

UEFI Secureboot implementations use PK, KEK, and db keys:

Platform Key (PK) : Top-level key, is used to sign KEK.

Key Exchange Key (KEK) : Keys used to sign Signatures Database.

Signature Database (db) : Contains keys to sign UEFI payloads.

Before enabling UEFI Secureboot, users have to prepare their own PK, KEK and db keys.

Then, users can enable Secureboot either:

At flashing time; Or,

At the target from Ubuntu prompt.

The following diagram illustrates how PK/KEK/db keys are used to sign and validate UEFI’s payloads:

How PK/KEK/db keys are used in UEFI Secureboot

Enroll PK, KEK, and db keys in the form of UEFI authenticated variable.
Sign UEFI payloads such as L4tLauncher (as OS Loader), kernel, kernel-dtb with private key and flash signed images (on Host).
UEFI loads signed images.
UEFI Verifies image signature by using the associated certificate/public key, and verifies the certificate/public key existing in db but not in dbx.

Here is a high-level process to enable UEFI Secureboot:

Prepare the PK, the KEK, and the db keys on the host.

Generate the PK, the KEK, and the db keypairs and the certificates.

Create a UEFI keys config file.

Run the gen_uefi_default_keys_dts.sh script to generate UefiDefaultSecurityKeys.dtbo and all key’s auth files.

Generate signed UEFI payloads on the host.

If you are enabling Secureboot at flashing time, the flashing utility will automatically generate signed UEFI payloads.

If you are enabling Secureboot at running time from Ubuntu prompt, you have to manually generate the signed UEFI payloads.

Enable UEFI Secureboot at flashing time.

Use option –uefi-keys <keys_conf> to provide signing keys and enable UEFI secure boot.

Enable UEFI Secureboot through UEFI utilities running from Ubuntu prompt

Download the PK, the KEK, and the db auth files from the host.

Enroll the KEK and the db keys.

Download and write the signed UEFI payloads.

Enroll the PK key.

Note

When UEFI Secureboot is enabled during the flashing process, it cannot be disabled unless you flash again.

However, if UEFI Secureboot is enabled through UEFI utilities running from the Ubuntu prompt, you can disable it by accessing the UEFI Menu and selecting Reset Secure Boot Keys, provided you have the necessary permissions. UEFI Secureboot can also be disabled by enrolling noPK.auth at runtime. Assuming only an admin has access to noPK.auth, they can disable UEFI Secureboot on next boot by running the kernel utility efi-updatevar with noPK.auth.

This section provides information about how to use Capsule to update the KEK, the db, the and dbx keys after enabling the UEFI Secureboot. Here is the high-level process to update UEFI Secureboot keys:

Prepare the update keys.

Generate the KEK, the db, and the dbx keys auth file for update.

Create a UEFI update keys config file with the generated keys auth file.

Generate the UefiUpdateSecurityKeys.dtbo file.

Generate the Capsule payload with UEFI Secureboot enabled.

Trigger a Capsule update.

Check and verify update keys.

Check the UEFI Secureboot status.

Check the updated KEK.

Check the updated db.

Check the updated dbx.

Prerequisites

Ensure that the following utilities are installed in your host:

openssl
device-tree-compiler
efitools
uuid-runtime

References

https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface/Secure_Boot#Implementing_Secure_Boot

https://www.rodsbooks.com/efi-bootloaders/controlling-sb.html

Prepare the PK, KEK, db Keys

Generate the PK, KEK, db RSA keypairs and certificates

To generate the PK, KEK, and db RSA keypairs and certificates, run the following commands:

$ cd to <LDK_DIR>
$ mkdir uefi_keys
$ cd uefi_keys

### Generate PK RSA keypair and certificate
$ openssl req -newkey rsa:2048 -nodes -keyout PK.key  -new -x509 -sha256 -days 3650 -subj "/CN=my Platform Key/" -out PK.crt

### Generate KEK RSA keypair and certificate
$ openssl req -newkey rsa:2048 -nodes -keyout KEK.key  -new -x509 -sha256 -days 3650 -subj "/CN=my Key Exchange Key/" -out KEK.crt

### Generate db_1 RSA keypair and certificate
$ openssl req -newkey rsa:2048 -nodes -keyout db_1.key  -new -x509 -sha256 -days 3650 -subj "/CN=my Signature Database key/" -out db_1.crt

### Generate db_2 RSA keypair and certificate
$ openssl req -newkey rsa:2048 -nodes -keyout db_2.key  -new -x509 -sha256 -days 3650 -subj "/CN=my another Signature Database key/" -out db_2.crt

Caution

The generated .crt files are self-signed certificates and are used for demonstration purposes only. For production, follow your official certificate generation procedure.

Create a UEFI Keys Config File

To create a UEFI keys config file with the generated keys, run the following command:

$ vim uefi_keys.conf

Insert the following lines to uefi_keys.conf file:

UEFI_PK_KEY_FILE="PK.key";
UEFI_PK_CERT_FILE="PK.crt";
UEFI_KEK_KEY_FILE="KEK.key";
UEFI_KEK_CERT_FILE="KEK.crt";
UEFI_DB_1_KEY_FILE="db_1.key";
UEFI_DB_1_CERT_FILE="db_1.crt";
UEFI_DB_2_KEY_FILE="db_2.key";
UEFI_DB_2_CERT_FILE="db_2.crt";

Note

The UEFI_DB_2_XXX entries are optional.
Microsoft has two DB certificates and one KEK certificate, and these certificates can be used based on your requirement. Refer to Microsoft’s certificates for more information.
The UEFI revocation list file, which is used to update the Secure Boot Forbidden Signature Database (dbx). Download the revocation list file from UEFI Revocation List File for arm64.
For a system installed with a UEFI option ROM, and that is signed with a Microsoft db, you must enroll the Microsoft db, the KEK, and the UEFI dbx certificates. Assign the corresponding key esl files to the variable UEFI_APPEND_KEK_ESL_FILE_0 (up to 1), the UEFI_APPEND_DB_ESL_FILE_0 (update to 1), and the UEFI_DBX_ESL_FILE_0 (up to 1) in the uefi_keys.conf file.

Generate UefiDefaultSecurityKeys.dtbo and the Auth Files

To enable UEFI Secureboot at flashing time, the UEFI default security keys need to be flashed to target. The UEFI default security keys are embedded in UefiDefaultSecurityKeys.dtbo and are used during flashing.

Also, the PK, KEK and db’s auth files are used to enroll the PK, KEK and db Keys from target when enabling UEFI Secureboot through UEFI utilities running from Ubuntu prompt.

UefiDefaultSecurityKeys.dtbo and the auth files are generated by using the gen_uefi_default_keys_dts.sh script.

Run the following commands:

$ cd ..
$ sudo tools/gen_uefi_default_keys_dts.sh uefi_keys/uefi_keys.conf
$ sudo chmod 644 uefi_keys/_out/*.auth

Note

Users can also run the gen_uefi_keys_dts.sh script to generate the UefiDefaultSecurityKeys.dtbo file by using a config file with the UEFI_DEFAULT_PK_ESL, the UEFI_DEFAULT_KEK_ESL_0 (up to 2), the UEFI_DEFAULT_DB_ESL_0 (up to 2), the UEFI_DB_1_KEY_FILE, the UEFI_DB_1_CERT_FILE, and the optional UEFI_DEFAULT_DBX_ESL_0 (up to 2) settings.
The gen_uefi_default_keys_dts.sh script will be deprecated in future releases.

Generate Signed UEFI Payloads

All UEFI payloads have to be signed using UEFI security keys. If the –uefi-keys option is specified during flashing, the UEFI payloads are signed automatically by the flash.sh script. To enable UEFI Secureboot at runtime from Ubuntu prompt, the UEFI payloads have to be signed from the host and then you can download the signed payloads to target.

The UEFI payloads are:

extlinux.conf
initrd
kernel images (in rootfs, and in kernel and recovery partitions)
kernel-dtb images (in rootfs, and in kernel-dtb and recovery-dtb partitions), and
BOOTAA64.efi.

Note

The following steps assume that you have copied the required unsigned UEFI payloads to the uefi_keys/ folder. Also, db.crt and db.key can be replaced with db_1.* or db_2.* key.

To sign extlinux.conf using db:

$ openssl cms -sign -signer db.crt -inkey db.key -binary -in extlinux.conf -outform der -out extlinux.conf.sig

To sign initrd using db:

$ openssl cms -sign -signer db.crt -inkey db.key -binary -in initrd -outform der -out initrd.sig

To sign Image (the kernel) of rootfs using db:

$ cp Image Image.unsigned
$ sbsign --key db.key --cert db.crt --output Image Image

To sign kernel-dtb of rootfs using db:
```
$ openssl cms -sign -signer db.crt -inkey db.key -binary -in kernel_tegra234-p3701-0004-p3737-0000.dtb -outform der -out kernel_tegra234-p3701-0004-p3737-0000.dtb.sig
```
Note

The command above uses Concord’s SKU 4 kernel-dtb filename and should be replaced with the appropriate kernel-dtb filename of your target.

To sign boot.img of kernel partition using db:

$ ../bootloader/mkbootimg --kernel Image --ramdisk initrd --board <rootdev> --output boot.img --cmdline <cmdline_string>
$ cp boot.img boot.img.unsigned
$ openssl cms -sign -signer db.crt -inkey db.key -binary -in boot.img -outform der -out boot.img.sig
$ truncate -s %2048 boot.img
$ cat boot.img.sig >> boot.img

where <cmdline_string>, when generated in flash.sh to flash eMMC/SD, is:
Xavier Series:
root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0
Orin Series:
root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 console=ttyAMA0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0
and the <cmdline_string>, when generated in l4t_initrd_flash.sh to flash NVMe, is:
Xavier Series:
root=/dev/nvme0n1p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0
Orin Series:
root=/dev/nvme0n1p1 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 console=ttyAMA0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0
Note

The Image inside boot.img must also be signed. Use the Image signed by the step 3 above.

To sign kernel-dtb of kernel-dtb partition using db:

$ cp tegra234-p3701-0004-p3737-0000.dtb tegra234-p3701-0004-p3737-0000.dtb.unsigned
$ openssl cms -sign -signer db.crt -inkey db.key -binary -in tegra234-p3701-0004-p3737-0000.dtb -outform der -out tegra234-p3701-0004-p3737-0000.dtb.sig
$ truncate -s %2048 tegra234-p3701-0004-p3737-0000.dtb
$ cat tegra234-p3701-0004-p3737-0000.dtb.sig >> tegra234-p3701-0004-p3737-0000.dtb

Note

The commands above use Concord’s SKU 4 kernel-dtb filename and should be replaced with the appropriate kernel-dtb filename of your target.

To sign recovery.img of recovery partition using db:
```
$ ../bootloader/mkbootimg --kernel Image --ramdisk ../bootloader/recovery.ramdisk --output recovery.img --cmdline <rec_cmdline_string>
$ cp recovery.img recovery.img.unsigned
$ openssl cms -sign -signer db.crt -inkey db.key -binary -in recovery.img -outform der -out recovery.img.sig
$ truncate -s %2048 recovery.img
$ cat recovery.img.sig >> recovery.img
```
where <rec_cmdline_string> is:

Xavier Series:
“root=/dev/initrd rw rootwait console=ttyTCU0,115200n8 fbcon=map:0 net.ifnames=0 video=tegrafb no_console_suspend=1 earlycon=tegra_comb_uart,mmio32,0x0c168000 sdhci_tegra.en_boot_part_access=1”

Orin Series:
“root=/dev/initrd rw rootwait mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0”

Note

The Image inside recovery.img must also be signed. Use the Image signed by the step 3 above.

To sign recovery kernel-dtb of recovery-dtb partition using db:

$ cp tegra234-p3701-0004-p3737-0000.dtb.rec tegra234-p3701-0004-p3737-0000.dtb.rec.unsigned
$ openssl cms -sign -signer db.crt -inkey db.key -binary -in tegra234-p3701-0004-p3737-0000.dtb.rec -outform der -out tegra234-p3701-0004-p3737-0000.dtb.rec.sig
$ truncate -s %2048 tegra234-p3701-0004-p3737-0000.dtb.rec
$ cat tegra234-p3701-0004-p3737-0000.dtb.rec.sig >> tegra234-p3701-0004-p3737-0000.dtb.rec

Note

The commands above use Concord’s SKU 4 kernel-dtb filename and should be replaced with the appropriate kernel-dtb filename of your target. The commands in steps 5 to 8 above sign images that are stored in partition. The signing appends certificate and signature to the original image (after first being aligned to 2K boundary).

To sign BOOTAA64.efi using db:

$ cp BOOTAA64.efi BOOTAA64.efi.unsigned
$ sbsign --key db.key --cert db.crt --output BOOTAA64.efi BOOTAA64.efi

Enabling UEFI Secureboot at Flashing Time

Using option –uefi-keys <keys_conf> to Provide Signing Keys and Enabling UEFI Secure Boot

Note

Although UEFI secure boot can be independently enabled from a low-level bootloader secure boot, we strongly recommended that users enable bootloader secure boot so that the root-of-trust can start from the BootROM.

Issue the following commands with --uefi-keys <keys.conf> option:

For the Jetson AGX Orin series, the Jetson Xavier NX series, and the Jetson AGX Xavier series:
```
$ sudo ./flash.sh -u <pkc_keyfile> [-v <sbk_keyfile>] --uefi-keys uefi_keys/uefi_keys.conf <target> mmcblk0p1
```
Where <target> is one of the following options:
- For the Jetson AGX Orin: jetson-agx-orin-devkit
- For the Jetson Xavier NX series: jetson-xavier-nx-devkit-emmc
- For the Jetson AGX Xavier series: jetson-agx-xavier-devkit

For the Jetson Orin NX series and the Orin Nano series:

$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -u <pkc_keyfile> [-v <sbk_keyfile>] --uefi-keys uefi_keys/uefi_keys.conf -p "-c ./bootloader/t186ref/cfg/flash_t234_qspi.xml" -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-orin-nano-devkit nvme0n1p1

Refer to Sign and Flash Secured Images for more information about the pkc_keyfile and the sbk_keyfile.

Once flashing is finished, your target has UEFI Secureboot enabled.

Enabling UEFI Secureboot through UEFI Utilities by Running from an Ubuntu Prompt

Applies to the Jetson Orin series and the Jetson Xavier NX series.

This section is for the targets that were not flashed with UEFI Secureboot enabled.

Prerequisites

Install UEFI utilities: efitools and efivar:
$ apt update
$ apt install efitools
$ apt install efivar
Ensure that Secureboot is not enabled:
$ efivar -n 8be4df61-93ca-11d2-aa0d-00e098032b8c-SecureBoot
Note

The above command should return with a value of 0. If it returns with a value of 1, you cannot continue.

Outline of steps (all steps are performed in the target):

Download the PK, KEK and db auth files from the host
Enroll the KEK, db keys
Download and write the signed UEFI payloads
Enroll the PK key

Detail steps

Download the PK, KEK and db auth files from the host

To get the PK, KEK, and db auth files, run the following commands:
```
$ mkdir /uefi_keys
$ cd /uefi_keys
$ scp <host_ip>:<LDK_DIR>/uefi_keys/_out/*.auth .
```

Enroll the KEK, db keys

To enroll the KEK and db, run the following commands:

$ efi-updatevar -f /uefi_keys/db.auth db
$ efi-updatevar -f /uefi_keys/KEK.auth KEK

Download and write the signed UEFI payloads

Download the signed UEFI payloads from the host to the payloads’ corresponding target’s folder as per the following table

Filename from host’s <LDK_DIR>/uefi_keys/ folder	Target’s folder	Type
extlinux.conf and extlinux.conf.sig	/boot/extlinux/	rootfs
initrd and initrd.sig	/boot/	rootfs
initrd and initrd.sig	/boot/	rootfs
kernel_tegra234-p3701-0004-p3737-0000.dtb, and kernel_tegra234-p3701-0004-p3737-0000.dtb.sig (for Concord SKU 4)	/boot/dtb/	rootfs
Image	/boot/	rootfs
BOOTAA64.efi	/uefi_keys/	esp partition
boot.img	/uefi_keys/	A/B_kernel partition
tegra234-p3701-0004-p3737-0000.dtb (for Concord SKU 4)	/uefi_keys/	A/B_kernel-dtb partition
recovery.img	/uefi_keys/	recovery partition
tegra234-p3701-0004-p3737-0000.dtb.rec (for Concord SKU 4)	/uefi_keys/	recovery-dtb partition

Note

You might want to save copies of the original files.

For the UEFI payload files with the rootfs type, the target’s folder listed in the table are their final destinations. The other files need to be copied to their destination partitions. To copy a file to its destination partition, copy the file to a block device that is mapped to that partition.

To find out a block device mapped to a particular partition, use blkid:

$ sudo blkid | grep <part_name>

where <part_name> is:

   - esp
   - A_kernel
   - B_kernel
   - A_kernel-dtb
   - B_kernel-dtb
   - recovery
   - recovery-dtb

Note

If there are multiple block devices mapped to a partition, choose the one that is the boot device.

3.1 To write the signed BOOTAA64.efi to esp partition:

### Ex: esp partition is mapped to /dev/mmcblk0p10
$ mount /dev/mmcblk0p10 /mnt
$ cp /uefi_keys/BOOTAA64.efi /mnt/EFI/BOOT/BOOTAA64.efi
$ sync
$ umount /mnt

3.2 To write the signed boot.img to A_kernel partition:

### Ex: A_kernel partition is mapped to /dev/mmcblk0p2
$ dd if=/uefi_keys/boot.img of=/dev/mmcblk0p2 bs=64k

3.3 To write the signed boot.img to B_kernel partition:

### Ex: B_kernel partition is mapped to /dev/mmcblk0p5
$ dd if=/uefi_keys/boot.img of=/dev/mmcblk0p5 bs=64k

3.4 To write the signed kernel-dtb to A_kernel-dtb partition:

### Ex: A_kernel-dtb partition is mapped to /dev/mmcblk0p3
$ dd if=/uefi_keys/tegra234-p3701-0004-p3737-0000.dtb of=/dev/mmcblk0p3 bs=64k

3.5 To write the signed kernel-dtb to B_kernel-dtb partition:

### Ex: B_kernel-dtb partition is mapped to /dev/mmcblk0p6
$ dd if=/uefi_keys/tegra234-p3701-0004-p3737-0000.dtb of=/dev/mmcblk0p6 bs=64k

3.6 To write the signed recovery.img to recovery partition:

### Ex: recovery partition is mapped to /dev/mmcblk0p8
$ dd if=/uefi_keys/recovery.img of=/dev/mmcblk0p8 bs=64k

3.7 To write the signed recovery kernel-dtb to recovery-dtb partition:

### Ex: recovery-dtb partition is mapped to /dev/mmcblk0p9
$ dd if=/uefi_keys/tegra234-p3701-0004-p3737-0000.dtb.rec of=/dev/mmcblk0p9 bs=64k

Enroll the PK key

To enroll the PK key last to enable UEFI Secureboot:
```
$ efi-updatevar -f /uefi_keys/PK.auth PK
```

Check if UEFI Secureboot is enabled

Reboot the target and run the efivar command to verify:

$ efivar -n 8be4df61-93ca-11d2-aa0d-00e098032b8c-SecureBoot

.. note::
   The command above should return with a value of 01.

Update the db/dbx Keys with a Capsule Update

When UEFI Secureboot is enabled, you can use Capsule update to update the KEK, the db, and the dbx keys. Refer to Generating the Capsule Update Payload for more information about Capsule update.

Prepare the Update Key Auth Files

You must provide the KEK/db/dbx keys certificates in signed the esl (.auth) format, and you can update one, two, or all three key types.

The next section is an example that shows you how to generate self-signed certificates to test updates to the all three types of keys.

Note

In a production environment, complete your official certificate generation procedure.

Generate the KEK, the db, and the dbx Key Auth Files for an Update

To generate the KEK, the db, and the dbx key auth files:

Run the following commands to prepare to generate the update keys:
```
$ cd to <LDK_DIR>/uefi_keys
$ GUID=$(uuidgen)
```

Run the following commands to generate the KEK RSA keypair and certificate for the update:

$ openssl req -newkey rsa:2048 -nodes -keyout update_kek_0.key  -new -x509 -sha256 -days 3650 -subj "/CN=Update KEK 0/" -out update_kek_0.crt
$ cert-to-efi-sig-list -g "${GUID}" update_kek_0.crt update_kek_0.esl
$ sign-efi-sig-list -a -k PK.key -c PK.crt KEK update_kek_0.esl update_kek_0.auth

Note

This step is needed only when a KEK update is required.
The PK.key and PK.crt are the PK private key and PK certificate that were generated when you enrolled the default keys in Generate the PK, KEK, db RSA keypairs and certificates.

Run the following commands to generate the db RSA keypair and certificate for the update:

$ openssl req -newkey rsa:2048 -nodes -keyout update_db_0.key  -new -x509 -sha256 -days 3650 -subj "/CN=Update DB 0/" -out update_db_0.crt
$ cert-to-efi-sig-list -g "${GUID}" update_db_0.crt update_db_0.esl
$ sign-efi-sig-list -a -k update_kek_0.key -c update_kek_0.crt db update_db_0.esl update_db_0.auth

Note

The signing private key (update_kek_0.key) and the certificate (update_kek_0.crt) are generated by running the previous command. They can also be the KEK private key and certificate when you enroll the default keys in Generate the PK, KEK, db RSA keypairs and certificates.

Run the following commands to generate another db RSA keypair and certificate for the update:

$ openssl req -newkey rsa:2048 -nodes -keyout update_db_1.key  -new -x509 -sha256 -days 3650 -subj "/CN=update DB 1/" -out update_db_1.crt
$ cert-to-efi-sig-list -g "${GUID}" update_db_1.crt update_db_1.esl
$ sign-efi-sig-list -a -k KEK.key -c KEK.crt db update_db_1.esl update_db_1.auth

Run the following commands to generate db_2 auth for the dbx update:

$ cert-to-efi-sig-list -g "${GUID}" db_2.crt db_2.esl
$ sign-efi-sig-list -a -k update_kek_0.key -c update_kek_0.crt dbx db_2.esl dbx_db_2.auth

Note

The db_2 certificate is generated when you enroll the default keys in Generate the PK, KEK, db RSA keypairs and certificates.

Caution

The generated .crt files are self-signed certificates and are used for demonstration purposes only. In a production environment, complete your official certificate generation procedure.

Create a UEFI Update Keys Config File

To create a UEFI keys config file with the generated key auth files:

Run the following command to create the uefi_update_keys.conf file:
```
$ vim uefi_update_keys.conf
```

Add the following lines to the uefi_update_keys.conf file:

UEFI_DB_1_KEY_FILE="update_db_0.key";  # UEFI payload signing key
UEFI_DB_1_CERT_FILE="update_db_0.crt"; # UEFI payload signing key certificate
UEFI_UPDATE_PRE_SIGNED_KEK_0="update_kek_0.auth"
UEFI_UPDATE_PRE_SIGNED_DB_0="update_db_0.auth"
UEFI_UPDATE_PRE_SIGNED_DB_1="update_db_1.auth"
UEFI_UPDATE_PRE_SIGNED_DBX_0="dbx_db_2.auth"

Note

The UEFI_DB_1_KEY_FILE and UEFI_DB_1_CERT_FILE are used to sign UEFI payloads such as L4TLauncher, kernel, and kernel-dtb. If the UEFI payloads are resigned with update_db_x key, which is shown in this example, you can use the same signing key (db_1.key and db_1.crt) that was used when you initially enabled UEFI secure boot or the update key update_db_x that was defined in this update key conf.
Users can specify up to 50 UEFI_UPDATE_PRE_SIGNED_KEK_n, UEFI_UPDATE_PRE_SIGNED_DBX_n, or UEFI_UPDATE_PRE_SIGNED_DB_n.
If the following standard keys are not enrolled yet, they can be used here according to your requirement:
- Microsoft’s certificates (two DB certificates and one KEK certificate). Refer to the Microsoft’s certificates for more information.
- The UEFI revocation list file, which is used to update the Secure Boot Forbidden Signature Database (dbx). Download the revocation list file from UEFI Revocation List File for arm64. To update the revocation list file to dbx, assign the arm64_DBXUpdate.bin file to the UEFI_UPDATE_PRE_SIGNED_DBX_n variable in uefi_update_keys.conf.

Generate the UefiUpdateSecurityKeys.dtbo File

To update the UEFI Secureboot keys, the update UEFI security keys auth files are embedded in the UefiUpdateSecurityKeys.dtbo file, which is generated by using the gen_uefi_keys_dts.sh script.

Run the following commands:

$ cd ..
$ sudo tools/gen_uefi_keys_dts.sh uefi_keys/uefi_update_keys.conf
$ sudo chmod 644 uefi_keys/*.auth

Note

Users can also run the gen_uefi_keys_dts.sh script to generate the UefiDefaultSecurityKeys.dtbo file by using a config file with the UEFI_DEFAULT_PK_ESL, the UEFI_DEFAULT_KEK_ESL_0 (up to 2), the UEFI_DEFAULT_DB_ESL_0 (up to 2), the UEFI_DB_1_KEY_FILE, the UEFI_DB_1_CERT_FILE, and the optional UEFI_DEFAULT_DBX_ESL_0 (up to 2) settings.

Generate a Capsule Payload with UEFI Secureboot Enabled

The UefiUpdateSecurityKeys.dtbo generated above is packed into Capsule payload with cpu-bootloader.Refer to Generating the Capsule Update Payload for more information.

To generate a Capsule payload, complete one of the following tasks:

- Generate a Capsule payload for the Jetson AGX Orin devkits.
  $ sudo ./l4t_generate_soc_bup.sh -e t23x_agx_bl_spec -p "--uefi-keys uefi_keys/uefi_update_keys.conf" t23x
  $ ./generate_capsule/l4t_generate_soc_capsule.sh -i bootloader/payloads_t23x/bl_only_payload -o ./TEGRA_AGX.Cap t234

- Generate a Capsule payload for the Jetson AGX Orin Industrial.
  $ sudo ./l4t_generate_soc_bup.sh -e t23x_agx_ind_bl_spec -p "--uefi-keys uefi_keys/uefi_update_keys.conf" t23x
  $ ./generate_capsule/l4t_generate_soc_capsule.sh -i bootloader/payloads_t23x/bl_only_payload -o ./TEGRA_AGX_IND.Cap t234

- Generate a Capsule payload for the Jetson Orin Nano devkits.
  $ sudo ./l4t_generate_soc_bup.sh -e t23x_3767_bl_spec -p "--uefi-keys uefi_keys/uefi_update_keys.conf" t23x
  $ ./generate_capsule/l4t_generate_soc_capsule.sh -i bootloader/payloads_t23x/bl_only_payload -o ./TEGRA_Nano.Cap t234

- Generate a Capsule payload for the Jetson Xavier NX devkits.
  $ sudo ./l4t_generate_soc_bup.sh -b jetson-xavier-nx-devkit -p "--uefi-keys uefi_keys/uefi_update_keys.conf" t19x
  $ ./generate_capsule/l4t_generate_soc_capsule.sh -i bootloader/payloads_t19x/bl_only_payload -o ./TEGRA_NX.Cap t194

- Generate a Capsule payload for the Jetson AGX Xaviver devkits.
  $ sudo ./l4t_generate_soc_bup.sh -b jetson-agx-xavier-devkit -p "--uefi-keys uefi_keys/uefi_update_keys.conf" t19x
  $ ./generate_capsule/l4t_generate_soc_capsule.sh -i bootloader/payloads_t19x/bl_only_payload -o ./TEGRA_Xavier.Cap t194

Trigger a Capsule Update

To trigger a Capsule update, complete the steps in Manually Trigger the Capsule Update

Note

After the Capsule update is complete, the system boots from the newly updated slot.

Check and Verify the Update Keys

After the Capsule update is complete, to check and verify the update keys:

Run the following commands to install mokutil on the target device:

$ sudo dhclient eth0      # If the ethernet has not yet been enabled, enable it now.
$ sudo apt-get update
$ sudo apt-get install mokutil

Run the following command to check the UEFI Secureboot status:
```
$ mok --sb-state
```

Note

The command should output “SecureBoot enabled”.

Run the following command to check the updated KEK:
```
$ mokutil --kek
```

Note

The update_kek_0.crt file is in the output key list.

Run the following command to check the updated db:
```
$ mokutil --db
```

Note

The update_db_0.crt and update_db_1.crt files are in the output key list.

Run the following command to check the updated dbx:
```
$ mokutil --dbx
```

Note

The db_2.crt file is in the output key list.

UEFI Payload Encryption

The UEFI Payload Encryption encrypts UEFI payloads with a user encryption key, and this key is stored in EKB, which is flashed to the EKS partition. When the system boots to OPTEE, the user key PTA extracts this key, and when the system boots to UEFI, the L4tLauncher (OS Loader) calls the TA to decrypt and loads the encrypted UEFI payloads.

Note

UEFI Payload Encryption can be enabled only when UEFI SecureBoot is enabled.

The UEFI payloads are:

initrd
kernel images in the rootfs and in the kernel and the recovery partitions.
kernel-dtb images in the rootfs and in the kernel-dtb and the recovery-dtb partitions.

The UEFI Payload Encryption implementation includes the user encryption key, the EKB, and the TA:

User Key: User-defined encryption key.
EKB: The encrypted key blob used to store the encrypted user keys.
Trusted Application (TA): Used to decrypt and authenticate the UEFI payloads.

To enable UEFI Payload Encryption, users must prepare their own UEFI payload encryption key and then generate their own EKB.

Here is a high-level process to enable UEFI Payload Encryption:

Prepare the User Key
Generate the EKB
Enabling UEFI Payloads Encryption at Flashing Time

The following flow chart illustrates how the encrypted payloads are decrypted and loaded:

Prepare the User Encryption Key

Generate a random user encryption key with random number generator and write it to user_encryption.key in the big-endian hex format.
- For T194, the key is 128 bits long.
- For T234, the key is 256 bits long.

Generate the EKB

Generate the EKB (refer to EKB Generation for more information).
Copy the EKB to the <Linux For Tegra>/bootloader folder.

Enabling UEFI Payload Encryption at Flashing Time

The --uefi-enc <user_encryption.key> option is used to provide the user encryption key and enable UEFI Payload Encryption.

To enable UEFI Payload Encryption, you must simultaneously enable UEFI secure boot. In this condition, the ---uefi-keys and the --uefi-enc option are specified, and the flashing utility will generate the signed and encrypted UEFI payloads and flash them to board.

Using the `--uefi-enc <user_encryption.key>` Option to Provide the User Encryption Key and Enable UEFI Payloads Encryption

Note

Although UEFI secure boot can be independently enabled from a low-level bootloader secure boot, we strongly recommended users enable bootloader secure boot so that the root-of-trust can start from the BootROM.

Issue the following command with the --uefi-enc <user_encryption.key> option:

For the Jetson AGX Orin series, the Jetson Xavier NX series, and the Jetson AGX Xavier series:
```
$ sudo ./flash.sh -u <pkc_keyfile> [-v <sbk_keyfile>] --uefi-keys uefi_keys/uefi_keys.conf --uefi-enc user_encryption.key <target> mmcblk0p1
```
Where <target> is one of the following options:
- For the Jetson AGX Orin: jetson-agx-orin-devkit
- For the Jetson Xavier NX series: jetson-xavier-nx-devkit-emmc
- For the Jetson AGX Xavier series: jetson-agx-xavier-devkit

For the Jetson Orin NX series and the Orin Nano series:

$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -u <pkc_keyfile> [-v <sbk_keyfile>] --uefi-keys uefi_keys/uefi_keys.conf --uefi-enc user_encryption.key -p "-c ./bootloader/t186ref/cfg/flash_t234_qspi.xml" -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-orin-nano-devkit nvme0n1p1

where <user_encryption.key> is the pathname to a file that contains the user encryption key in the <Linux_for_tegra>/ folder.

Refer to Sign and Flash Secured Images for more information about the pkc_keyfile and the sbk_keyfile.

After flashing is complete, your target will have UEFI Secureboot and UEFI Payloads Encryption enabled.

UEFI Variable Protection

The UEFI Variable Protection protects the UEFI variables from tampering. A UEFI variable authentication key is required, and this key is a user key stored in EKB, which is flashed to the EKS partition.

When the system boots to OPTEE, the user key PTA extracts this key from EKB.
when the system boots to UEFI, UEFI will call TA to use the UEFI variable authentication key to calculate the measurement.

The measurement authenticates the UEFI variables, and tampering with UEFI variables will be detected.

The UEFI Variable Protection implementation includes the UEFI, user key, and the TA:

UEFI: Compares the measurements and aborts the boot if an attack is detected.
User Key: A user-defined UEFI variable authentication key that is stored in EKB.
Trusted Application (TA): Calculates measurements against the UEFI variables using the UEFI variable authentication key.

To enable UEFI Variable Protection, users must prepare their own UEFI variable authentication key and then generate their own EKB.

Here is a high-level process to enable UEFI variable protection:

Prepare the user key
Generate the EKB
Enable UEFI Variable Protection at flashing time

Prepare the UEFI Variable Authentication Key

Generate a random UEFI variable authentication key with random number generator and write it to user_authentication.key in the big-endian hex format.

For T194 and T234, the key is 128 bits long.

Generate the EKB

Generate the EKB (refer to EKB Generation for more information).
Copy the EKB to the <Linux For Tegra>/bootloader folder.

Enabling UEFI Variable Protection at Flashing Time

Note

Although UEFI variable protection can be independently enabled, we strongly recommended that users enable bootloader secure boot and UEFI secure boot so that the root-of-trust can start from the BootROM.

Issue the following command:

For the Jetson AGX Orin series, the Jetson Xavier NX series:
```
$ sudo ./flash.sh -u <pkc_keyfile> [-v <sbk_keyfile>] --uefi-keys uefi_keys/uefi_keys.conf <target> mmcblk0p1
```
Where <target> is one of the following options:
- For the Jetson AGX Orin: jetson-agx-orin-devkit
- For the Jetson Xavier NX series: jetson-xavier-nx-devkit-emmc

For the Jetson Orin NX series and the Orin Nano series:

$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -u <pkc_keyfile> [-v <sbk_keyfile>] --uefi-keys uefi_keys/uefi_keys.conf -p "-c ./bootloader/t186ref/cfg/flash_t234_qspi.xml" -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-orin-nano-devkit nvme0n1p1

Refer to Sign and Flash Secured Images for more information about the pkc_keyfile and the sbk_keyfile.

After flashing is complete, your target will have UEFI Secureboot and UEFI Variable Protection enabled.

UEFI Platform Vendor Key Feature

The UEFI platform vendor (PV) key feature allows PVs to deploy UEFI that is signed and encrypted by PV-owned keys without involving the solution providers.

NVIDIA® Jetson™ devices use a PKC key to verify the signature of boot component during device boot:

The component at stage N verifies the components at stage N+1.
The component at stage N+1 verifies the components at stage N+2, and so on.

With this feature, the UEFI owner, or the PV, can use a PV’s private key to sign UEFI, and can also deliver the public key to the solution provider, who was the owner of the boot components before UEFI. The public key is now built into the component (MB2) that loads in UEFI during boot.

During the secure boot process, the signature of the components before UEFI will be verified/authenticated by solution provider’s fused PKC. For UEFI, MB2 uses the built-in public key to verify PV authenticate key for key verification and signature authentication. As a result, the platform vendor, who does not own the fused PKC, can still independently sign and update the UEFI image.

In Jetson devices that use the T234 processor (NVIDIA® Jetson Orin™ NX series and NVIDIA® Jetson AGX Orin™ series), the PV key sign/authenticate UEFI is supported when secure boot is enabled.

Platform Vendor Key Signed/Authenticate UEFI

This section describes how to use a tool to sign UEFI by the PV and to authenticate it by the solution provider.

The PV can sign UEFI by the key it owns. Here is a high-level overview of the process:

The PV provides the PV authentication key file to the solution provider.
The solution provider builds boot images with the PV authentication key that is built into MB2.
The solution provider sends the results from step 2 to the PV.
The PV creates the combined boot images and completes one of the following tasks:
- Sends the images to the factory floor to build the device.
- Sends the images to the OTA server for the update.

Before you enable UEFI PV key sign/authenticate feature, the RSA 3K authentication scheme fuse must be burned.

Note

Currently, only RSA-3072 is supported for UEFI PV key signing.

Platform Vendor Procedure

To generate the PV authentication key and sign UEFI:

Generate the rsa-3072 private key and call it rsa_priv-3k-pv.pem.:
```
$ openssl genrsa -out rsa_priv-3k-pv.pem 3072
```

Create a certificate signing request and call it pub_key.csr.:

$ openssl req -key rsa_priv-3k-pv.pem -new -out pub_key.csr

Create a self-signed certificate and call it pv_key.crt.:

$ openssl x509 -signkey rsa_priv-3k-pv.pem -in pub_key.csr -req -days 3650 -out pv_key.crt

Provide the pv_key.crt file to the solution provider.
Get bootloader.tar.gz from the solution provider, place it in the Linux_for_Tegra/ folder, and untar it.:
```
$ tar -xzvf bootloader.tar.gz
```
Gather the BOARDID, FAB, BOARDSKU, and BOARDREV environment information from the solution provider.

Generate the signed UEFI image with the rsa_priv-3k-pv.pem PV private key .:

$ sudo BOARDID=<board_id> FAB=<fab> BOARDSKU=<sku_number> BOARDREV=<reversion> ./flash.sh --no-flash -u rsa_priv-3k-pv.pem -k A_cpu-bootloader jetson-agx-orin-devkit mmcblk0p1

Flash the device with the following commands:

$ boardctl -t topo recovery
$ cd bootloader/
$ sudo bash ./flashcmd.txt

Solution Provider Procedure

After the solution provider receives the PV authentication key, to enable the PV sign/authenticate UEFI feature, complete the following steps:

Place the pv_key.crt file in the Linux_for_Tegra/ folder.

Generate the signed boot images with the board-fused PKC key file (rsa_priv-3k.pem) and the PV key certificate (pv_key.crt) file.:

$ sudo BOARDID=<board_id> FAB=<fab> BOARDSKU=<sku_number> BOARDREV=<reversion> ./flash.sh --no-flash -u rsa_priv-3k.pem --pv-crt pv_key.crt jetson-agx-orin-devkit mmcblk0p1

Package Linux_for_Tegra/bootloader/ folder.:

$ tar -czvf bootloader.tar.gz ./bootloader

Send the bootloader.tar.gz file to the PV.

PV Key Encrypt/Decrypt UEFI

This section describes how to use the tool to encrypt UEFI by using a key owned by the PV and to decrypt it by the solution provider at MB2.

The mechanism is that the key encrypts UEFI is the PV-owned encryption key instead of the default SBK key. The PV will encrypt UEFI with its owned PV encryption key in one of the following ways:

The PV provides a fuse blob so that the PV encryption key can be burned into the fuse.

The PV provides the PV encryption key to the solution provider who can then inject the key into MB2 by using the tool.

Before enabling the UEFI PV key encrypt/decrypt feature, the SBK key and the encryption mode fuse must be burned. Refer to Fuse handling for more information.

Fuse Solution

To provide a higher level of protection to the PV encryption key, the PV can burn the PV encryption key into the OEM_K2 fuse. Now, MB2 can decrypt PV encrypted UEFI by using OEM_K2 through Security Engine without knowing the actual key, and here are the decryption steps:

The PV generates a fuse blob, which includes the PV encryption key, and that will be burned into OEM_K2 fuse.
The PV encrypts the UEFI image with the PV encryption key.
The solution provider generates its own fuse blob that includes the SBK key fuse and the encryption mode enable fuse.
The solution provider builds the boot images with the SBK key.
The solution provider sends the results from steps 3 and 4 to the PV.
The PV generates UEFI image, combines the boot images generated by the solution provider and the encrypted UEFI image generated by PV, and completes one of the following tasks:

Sends the images to the factory floor to build the device.

Sends the images to the OTA server for the OTA update.

Platform Vendor Procedure

This procedure generates the PV encryption key, generates the signing PV key, and encrypts and signs UEFI:

Generate the AES-256 key and call it pv_enc.key.:
```
$ openssl rand -hex 32 > pv_enc.key
```
Manually reformat pv_enc.key into eight 32-bit words big-endian hexadecimal.

For example, original content of pv_enc.key is 112233445566778899aabbccddeeff00ffeeddccbbaa99887766554433221100, and after the reformat, it changes to 0x11223344 0x55667788 0x99aabbcc 0xddeeff00 0xffeeddcc 0xbbaa9988 0x77665544 0x33221100.
Generate the rsa-3072 private key and call it rsa_priv-3k-pv.pem.:
```
$ openssl genrsa -out rsa_priv-3k-pv.pem 3072
```
Note

If the PV signing key and its certificates have been previously generated, you can skip this text.

Create a certificate signing request and call it pub_key.csr.:

$ openssl req -key rsa_priv-3k-pv.pem -new -out pub_key.csr

Create a self-signed certificate and call it pv_key.crt.:

$ openssl x509 -signkey rsa_priv-3k-pv.pem -in pub_key.csr -req -days 3650 -out pv_key.crt

Provide the pv_key.crt file to the solution provider.
Get bootloader.tar.gz from the solution provider, place it in the Linux_for_Tegra/, and untar it.:
```
$ tar -xzvf bootloader.tar.gz
```
Gather the BOARDID, FAB, BOARDSKU, and BOARDREV environment information from the solution provider.

Generate the signed and encrypted UEFI image with the PV private key (rsa_priv-3k-pv.pem) and the PV encryption key (pv_enc.key).:

$ sudo BOARDID=<board_id> FAB=<fab> BOARDSKU=<sku_number> BOARDREV=<reversion> ./flash.sh --no-flash -u rsa_priv-3k-pv.pem --pv-enc pv_enc.key -k A_cpu-bootloader jetson-agx-orin-devkit mmcblk0p1

Get the fuse blob from the solution provider and provide the solution provider’s fuse blob and the PV’s fuse blob to the factory to burn fuses.
Burn the fuse.

Run the following commands to flash the device:

$ boardctl -t topo recovery
$ cd bootloader/
$ sudo bash ./flashcmd.txt

Solution Provider Procedure

After the solution provider receives the PV authentication key, complete the following steps:

Set CONFIG_ENABLE_CPUBL_OEMK2_KDK=yes, rebuild MB2, and follow the instructions in the MB2 source release package to replace mb2_t234.bin.
Place the pv_key.crt file in the same folder as the flash.sh script.

Generate the signed and encrypted boot images by using the PKC key (rsa_priv-3k.pem), the SBK key, and the PV authentication key certificate (pv_key.crt):

$ sudo BOARDID=<board_id> FAB=<fab> BOARDSKU=<sku_number> BOARDREV=<reversion> ./flash.sh --no-flash -u rsa_priv-3k.pem -v <sbk.key> --pv-crt pv_key.crt jetson-agx-orin-devkit mmcblk0p1

Package the Linux_for_Tegra/bootloader/ folder.:
```
$ tar -czvf bootloader.tar.gz ./bootloader
```
Send the bootloader.tar.gz file to the PV.

Fuse handling

Before you execute the above flashing command, the device fuses must be burned with the fuse blobs that are provided by the PV and the solution provider.

Here is an example of a fuse blob (1) provided by the PV:

<genericfuse MagicId="0x45535546" version="1.0.0">
    <fuse name="PscOdmStatic" size="4" value="0x00000060"/>
    <fuse name="OemK2" size="32" value="0x112233445566778899aabbccddeeff00ffeeddccbbaa99887766554433221100"/>
</genericfuse>

Here is an example of a fuse blob (2) provided by the solution provider:

<genericfuse MagicId="0x45535546" version="1.0.0">
    <fuse name="PscOdmStatic" size="4" value="0x00000060"/>
    <fuse name="OemK1" size="32" value="0xf3bedbff9cea44c05b08124e8242a71ec1871d55ef4841eb4e59a56b5f88fb2b"/>
    <fuse name="PublicKeyHash" size="64" value="0xdc6632e495c7976659a94668a98d6ba7e22a2d9438a555ec64c0c1cc59e533067bfe64f454c1f30c63ad7627fb0cfa2f556aff45818254387016745ccf713081"/>
    <fuse name="SecureBootKey" size="32" value="0x123456789abcdef0fedcba987654321023456789abcdef01edcba9876543210f"/>
    <fuse name="BootSecurityInfo" size="4" value="0x209"/>
    <fuse name="SecurityMode" size="4" value="0x1"/>
</genericfuse>

You must ensure that in the fuse burning sequence, the fuse blob 1 burned first.

Note

The fuses specified in the PV’s fuse blob and the fuses specified in solution provider cannot be overlapped.
The fuse blob provided by the PV must be burned first because, after the “SecurityMode” that is specified in the solution provider’s fuse blob fuse is burned, fuse burning except ODM fuses is blocked.

Non-Fuse Solution

To encrypt UEFI by using the PV encryption key, the PV can provide the key to the solution provider who can then inject the key into MB2 for UEFI decryption on the device. Here are the steps:

The PV generates a PV encryption key and provides the key to the solution provider.
The solution provider injects the PV encryption key into MB2 and encrypts boot images with the SBK key.
The solution provider sends the results from the step 2 to the PV.
The PV combines boot images and completes one of the following tasks:

Sends them to the factory floor to build the device.

Sends them to the OTA server for the OTA update.

Platform Vendor Procedure

To generate the PV encryption key, encrypt UEFI, and sign UEFI with PV key:

Generate the AES-256 key and call it pv_enc.key.:
```
$ openssl rand -hex 32 > pv_enc.key
```
Manually reformat pv_enc.key into eight 32-bit words big-endian hexadecimal.

For example, original content of pv_enc.key is 112233445566778899aabbccddeeff00ffeeddccbbaa99887766554433221100 and after being manually reformatted, it changes to 0x11223344 0x55667788 0x99aabbcc 0xddeeff00 0xffeeddcc 0xbbaa9988 0x77665544 0x33221100.
Generate the rsa-3072 private key and call it rsa_priv-3k-pv.pem.:
```
$ openssl genrsa -out rsa_priv-3k-pv.pem 3072
```
Note

The steps for generating PV signing key and its certificate can be skipped if it has been done previously.

Create a certificate signing request and call it pub_key.csr.:

$ openssl req -key rsa_priv-3k-pv.pem -new -out pub_key.csr

Create a self-signed certificate and call it pv_key.crt.:

$ openssl x509 -signkey rsa_priv-3k-pv.pem -in pub_key.csr -req -days 3650 -out pv_key.crt

Provide the pv_key.crt and pv_enc.key file to the solution provider.
Get bootloader.tar.gz from the solution provider, place it in the Linux_for_Tegra/ folder, and untar it.:
```
$ tar -xzvf bootloader.tar.gz
```
Gather the BOARDID, FAB, BOARDSKU, and BOARDREV environment information from the solution provider.

Generate the signed and encrypted UEFI image with the PV authentication key and the PV encryption key and call it rsa_priv-3k-pv.pem and pv_enc.key respectively.:

$ sudo BOARDID=<board_id> FAB=<fab> BOARDSKU=<sku_number> BOARDREV=<reversion> ./flash.sh --no-flash -u rsa_priv-3k-pv.pem --pv-enc pv_enc.key -k A_cpu-bootloader jetson-agx-orin-devkit mmcblk0p1

Run the following commands to flash the device.:

$ boardctl -t topo recovery
$ cd bootloader/
$ sudo bash ./flashcmd.txt

Solution Provider Procedure

After the solution provider receives the PV authentication key and the PV encryption key, complete the following steps:

Get the PV authenticate key (pv_key.crt) and the encryption key (pv_enc.key) from the PV.
Place the pv_key.crt and the pv_enc.key in the same folder as the flash.sh script.
Generate the signed and encrypted images with a board that is fused with the PKC key (rsa_priv-3k.pem), the SBK key, the PV encryption key (pv_enc.key), and the PV authentication key certificate (pv_key.crt).:
```
$ sudo BOARDID=<board_id> FAB=<fab> BOARDSKU=<sku_number> BOARDREV=<reversion> ./flash.sh --no-flash -u rsa_priv-3k.pem -v <sbk.key> --pv-crt pv_key.crt --pv-enc pv_enc.key jetson-agx-orin-devkit mmcblk0p1
```
Package the Linux_for_Tegra/bootloader/ folder.:
```
$ tar -czvf bootloader.tar.gz ./bootloader
```
Send the bootloader.tar.gz file to the PV.

Kernel Module Signing

The kernel module signing facility signs modules during installation and then checks the signature upon loading the module. This allows increased kernel security by disallowing the loading of unsigned modules or modules that were signed with an invalid key.

Here are the kernel configure options for kernel module signing:

To enable kernel module signature verification, in the Enable Loadable Module Support section, enable CONFIG_MODULE_SIG.
To select the kernel module signature verification mode, set the CONFIG_MODULE_SIG_FORCE to one of the following options:
- off: permissive mode.
  - If the module is signed, it must have a trusted signature.
  - if the module is not signed, it can be loaded, and the kernel is marked as tainted.
- on: restrictive mode.
  - Modules can only be loaded if they are signed with a trusted signature.
  - The other modules will generate an error.
To enable automatic kernel module signing at build time, set the CONFIG_MODULE_SIG_ALL.

Note

By default, kernel modules are not signed at build time even if kernel module signature verification is enabled.

To specify your signing keys, set the CONFIG_MODULE_SIG_KEY with your own PEM format private key.
- By default, if CONFIG_MODULE_SIG_KEY=”certs/signing_key.pem” is not changed, the kernel automatically generates the PEM format signing key for the kernel module signing.
- Setting CONFIG_MODULE_SIG_KEY to something other than the certs/signing_key.pem default value disables the auto-generation of signing keys and allows the kernel module to be signed with a key that you select.

Note

The CONFIG_SYSTEM_TRUSTED_KEYS kernel option can also be set to the filename of a PEM-encoded file that contains the additional certificates. It is an X.509 certificate that is compiled into the kernel and used for kernel module verification for modules that are not signed at kernel build time. Refer to Kernel module signing facility for more information.

Secure Boot

Overall Fusing and Signing Binaries Flow

Prerequisites Secure Boot

Fuses and Security

Fuse Configuration File

Jetson Orin Fuse Configuration File

Example Orin Fuse Configuration File to Program an RSA-3K Key

Example Orin Fuse Configuration File to Program an ECDSA P-256 Key

Example Orin Fuse Configuration File to Program an ECDSA P-521 Key + SBK Key + OemK1 Key

Orin Reference Fuse Configuration File

Jetson Xavier NX and Jetson AGX Xavier Fuse Configuration Files

Example Xavier Fuse Configuration File to Program the RSA-2K Key

Example Xavier Fuse Configuration File to Program the RSA-3K Key + SBK Key + KEK Key

Xavier Reference Fuse Configuration File

Generate A PKC Key Pair

Generate PublicKeyHash value from a PKC key pair

Prepare an SBK key

Prepare K1/K2/KEK keys

Prepare the Fuse Configuration file

Burn Fuses with the Fuse Configuration file

Read Fuses through the Linux kernel

Sign and Flash Secured Images

Sign and Flash Secured Images in One Step

For Jetson Orin and Xavier series

Sign and Flash Secured Images in Separate Steps

Revocation of the PKC Keys

An Example: Fusing the Three PKC keys

An Example: Revoking the First PKC key (rsa3k-0.pem)

An Example: Revoking the Second PKC key (rsa3k-1.pem)

Legacy Support of Secure Boot for Xavier SoC

Burning PKC, KEK, and SBK Fuses

odmfuse.sh Options

Non-Destructive Testing for Fuse Burning Operations

odmfuse.sh Option Usage

Signing and Flashing with initrd Using the l4t_initrd_flash.sh Script

UEFI Secureboot

Prerequisites

References

Prepare the PK, KEK, db Keys

Generate the PK, KEK, db RSA keypairs and certificates

Create a UEFI Keys Config File

Generate UefiDefaultSecurityKeys.dtbo and the Auth Files

Generate Signed UEFI Payloads

Enabling UEFI Secureboot at Flashing Time

Using option –uefi-keys <keys_conf> to Provide Signing Keys and Enabling UEFI Secure Boot

Enabling UEFI Secureboot through UEFI Utilities by Running from an Ubuntu Prompt

Prerequisites

Detail steps

Check if UEFI Secureboot is enabled

Update the db/dbx Keys with a Capsule Update

Prepare the Update Key Auth Files

Generate the KEK, the db, and the dbx Key Auth Files for an Update

Create a UEFI Update Keys Config File

Generate the UefiUpdateSecurityKeys.dtbo File

Generate a Capsule Payload with UEFI Secureboot Enabled

Trigger a Capsule Update

Check and Verify the Update Keys

UEFI Payload Encryption

Prepare the User Encryption Key

Generate the EKB

Enabling UEFI Payload Encryption at Flashing Time

Using the --uefi-enc <user_encryption.key> Option to Provide the User Encryption Key and Enable UEFI Payloads Encryption

UEFI Variable Protection

Prepare the UEFI Variable Authentication Key

Generate the EKB

Enabling UEFI Variable Protection at Flashing Time

UEFI Platform Vendor Key Feature

Platform Vendor Key Signed/Authenticate UEFI

Platform Vendor Procedure

Solution Provider Procedure

PV Key Encrypt/Decrypt UEFI

Fuse Solution

Platform Vendor Procedure

Solution Provider Procedure

Fuse handling

Non-Fuse Solution

Platform Vendor Procedure

Solution Provider Procedure

Kernel Module Signing

Generate `PublicKeyHash` value from a PKC key pair

Using the `--uefi-enc <user_encryption.key>` Option to Provide the User Encryption Key and Enable UEFI Payloads Encryption