UEFI Adaptation¶

This section provides high level info for the users to adapt to using UEFI. CBoot was used in the prior rel-32 release, and is now replaced with UEFI starting with rel-34 release and onward.

Sources and Compilation¶

UEFI sources and compilation details for this release are available https://github.com/NVIDIA/edk2-nvidia/wiki.

Boot Order Selection¶

Supported Boot Device and the Default Boot Order¶

OS boot is supported from eMMC/SD/UFS/NvME/USB (T194 only). Removable devices (SD/USB) take precedence over non-removable (eMMC/NvME/UFS) devices in the default boot order.

Selecting the Boot Device in the UEFI¶

On the landing page of UEFI menu options, when you are prompted to Press ESCAPE for boot options, navigate to Boot Manager and select an option from this list.

Customizing the Default Boot Order in the Configuration File¶

If the user does not rebuild UEFI from source, change the default boot order in L4TConfiguration.dtbo or change the default boot order in L4TConfiguration.dts in the UEFI source.

Customizing the Default Boot Order in L4TConfiguration.dtbo in the BSP Directory¶

Convert the L4TConfiguration.dtbo file to L4TConfiguration.dts file:

$ cd <top>
$ kernel/dtc -I dtb -O dts -o kernel/dtb/L4TConfiguration.dts kernel/dtb/L4TConfiguration.dtbo

<top> is the pathname of the flash.sh directory, which contains the PDK installation package.

Change the default boot order in L4TConfiguration.dts:

/ {
    overlay-name = "L4T Configuration Settings";

    fragment@0 {
        target-path = "/";
        board_config {
            sw-modules = "uefi";
        };

        __overlay__ {
            firmware {
                uefi {
                  variables {
                        gNVIDIAPublicVariableGuid {
                           ... ... ...
                        };

                        gNVIDIATokenSpaceGuid {
                            DefaultBootPriority {
                                data = "usb,nvme,emmc,sd,ufs";
/*                              data = "Replace above data with your default boot order strings"; */
                                locked;
                            };
                        };
                    };
                };
            };
        };
    };
};

Set the default boot order to the DefaultBootPriority variable and separate the strings by commas. The valid strings are:

"usb"    - USB devices
"sd"     - SD devices
"emmc"   - eMMC devices
"nvme"   - NVMe devices
"ufs"    - UFS devices
"sata"   - SATA devices
"scsi"   - SCSI devices
"pxev4"  - IPv4 PXE boot
"httpv4" - IPv4 HTTP boot
"pxev6"  - IPv6 PXE boot
"httpv6" - IPv6 HTTP boot
"cdrom"  - CD/DVD drives
"boot.img" - Android style boot.img partition

Convert the L4TConfiguration.dts file to L4TConfiguration.dtbo file:

$ cd <top>
$ kernel/dtc -I dts -O dtb -o kernel/dtb/L4TConfiguration.dtbo kernel/dtb/L4TConfiguration.dts

<top> is the pathname of the flash.sh directory, which contains the PDK installation package.

Flash the Jetson device.

Customize the Default Boot Order in the L4TConfiguration.dts in UEFI Source¶

Change the default boot order variable DefaultBootPriority in the L4TConfiguration.dts file in the Silicon/NVIDIA/Tegra/DeviceTree/ UEFI source directory.
Build the UEFI from source and copy the generated L4TConfiguration.dtbo file to the <top>/kernel/dtb/ BSP directory.
Flash the Jetson device.

Overriding the Default Boot Order During Flashing¶

In addition to customizing the default boot order, you can also override the default boot order by providing a DTBO through ADDITIONAL_DTB_OVERLAY environment variable. For example, you can set the NVMe as default boot device for Jetson AGX Orin:

sudo ADDITIONAL_DTB_OVERLAY="BootOrderNvme.dtbo" ./flash.sh jetson-agx-orin-devkit nvme0n1p1

Boot Mode Selection¶

Customizing the Default Boot Mode in the Configuration File¶

Change the default boot mode in L4TConfiguration.dtbo if users do not rebuild UEFI from the source or change the default boot mode in L4TConfiguration.dts in the UEFI source.

Customizing the Default Boot Mode in L4TConfiguration.dtbo in the BSP Directory¶

Convert the L4TConfiguration.dtbo file to L4TConfiguration.dts file:

$ cd <top>
$ kernel/dtc -I dtb -O dts -o kernel/dtb/L4TConfiguration.dts kernel/dtb/L4TConfiguration.dtbo

<top> is the pathname of the flash.sh directory, which contains the PDK installation package.

Change the default boot mode in the L4TConfiguration.dts:

/ {
    overlay-name = "L4T Configuration Settings";
     fragment@0 {
        target-path = "/";
        board_config {
            sw-modules = "uefi";
        };

        __overlay__ {
            firmware {
                uefi {
                    variables {
                        gNVIDIAPublicVariableGuid {
                            QuickBootEnabled {
                                data = [00];
                                non-volatile;
                            };

                             ... ... ...

                            L4TDefaultBootMode {
                                data = [01 00 00 00];
/*                              data = "Replace above data with your default boot mode value"; */
                                runtime;
                                non-volatile;
                            };
                        };

                        gNVIDIATokenSpaceGuid {
                           ... ... ...
                        };
                    };
                };
            };
        };
    };
};

Set the default boot mode to the L4TDefaultBootMode variable. The valid values are:

[ 00 00 00 00 ]  - Boot GRUB
[ 01 00 00 00 ]  - Boot normal kernel and DTB in filesystem
[ 02 00 00 00 ]  - Boot normal kernel and DTB in partitions
[ 03 00 00 00 ]  - Boot recovery kernel and DTB in partitions

Convert the L4TConfiguration.dts file to L4TConfiguration.dtbo file:

$ cd <top>
$ kernel/dtc -I dts -O dtb -o kernel/dtb/L4TConfiguration.dtbo kernel/dtb/L4TConfiguration.dts

<top> is the pathname of the flash.sh directory, which contains the PDK installation package.

Flash the Jetson device.

Customizing the Default Boot Mode in L4TConfiguration.dts in the UEFI Source¶

Change the L4TDefaultBootMode default boot mode variable in the L4TConfiguration.dts file in the Silicon/NVIDIA/Tegra/DeviceTree/ UEFI source directory.
Build the UEFI from source and copy the generated L4TConfiguration.dtbo file to the <top>/kernel/dtb/ BSP directory.
Flash the Jetson device.

Customized Logo:¶

How to customize BMP?

For NVIDIA^® Jetson AGX Orin™

To change the logo displayed during UEFI boot, edit the files in edk2-nvidia/Silicon/NVIDIA/Assets. If you add/remove files or change names the files info can be updated in Platform/NVIDIA/NVIDIA.fvmain.fdf.inc. The relevant section is as shown below:
FILE FREEFORM = gNVIDIAPlatformLogoGuid {
   SECTION RAW = Silicon/NVIDIA/Assets/nvidiagray480.bmp
   SECTION RAW = Silicon/NVIDIA/Assets/nvidiagray720.bmp
   SECTION RAW = Silicon/NVIDIA/Assets/nvidiagray1080.bmp
}
Customers can replace the NVIDIA provided logo files with their own files and ensure the UEFI binary with the logo file(s) do not exceed the UEFI partition size (3.5MB) in the partition XML file. The partition XML files for various platforms are located in the ./bootloader/t186ref/cfg/ directory.

DTB Support¶

Selection Order

UEFI chooses the DTB for kernel in the following order:

1. FDT tag in /boot/extlinux/extlinux.conf file in rootfs can specify the DTB to be passed to the
   kernel.
2. If 1. is absent or cannot be used, DTB for kernel is loaded from the respective A/B kernel-dtb
   partition on boot device.
3. If both 1. and 2. are absent or cannot be used, UEFI passes the DTB used by UEFI itself to kernel.

How to customize
User can specify a custom DTB for kernel by modifying the FDT tag in /boot/extlinux/extlinux.conf file in rootfs. User can also uncomment backup boot option in the same file for adding an entirely new OS boot option.
DTB Overlays
DTB in use by UEFI and/or kernel can be updated using overlays that are applied during boot based on platform parameters like board-id/odm-data/fuse-info/sw-module. Criteria for applying an overlay can be specified in board_config node and if every criteria in the node matches, the overlay is applied on base DTB.

An example structure of an overlay device tree file is as shown below:

/ {
    fragment@0 {
        target= "<&uartc>";
        delete_prop = "early-print-console-channel";
        board_config {
            ids = "2888-0001-400", "3360-1099-100" ;
            odm-data = "enable-high-speed-uart";
            sw-modules = “kernel”;
        };
        __overlay__ {
            compatible = "nvidia,tegra186-hsuart";
            reset-names = "serial";
        };
    };

    fragment@1 {
        target-path = "/nvenc@154c0000";
        board_config {
            fuse-info = "fuse-disable-nvenc";
    };
        __overlay__ {
            status = "disabled";
        };
    };
};

- ids property in board_config can specify a list of board-id, one of which has to match
  the board IDs read from platform EEPROMs.

- odm-data property in board_config can specify a list of odm data strings that are matched
  against /chosen/odm-data property strings in base DTB to find if there is a match.
  User can specify valid odm data strings for a platform during flash.

- fuse-info property in board_config can specify a list of fuse strings for floor sweeping configuration.

- The sw-modules property in board_config can specify if an overlay needs to be applied to only UEFI DTB,
  kernel DTB or both. If this property is not present, overlay is applied to both kernel as well as UEFI dtb.

Supporting DTBO (Device Tree Blob Overlay) for the camera module (instead of using the prior supported plug-in manager)
Because UEFI boot is enabled in this release, the plugin manager is no longer supported. You must create a device tree overlay (DTB overlay, or .dtbo) file to register the camera module. If your camera module has on-board EEPROM and is programmed with a valid camera ID, you can use the device tree overlay file at to apply the overlay for a specific camera module and update the device tree entries with proper information at run time. Using a device tree overlay with an EEPROM ID allows a single system image to support multiple camera devices. To select a different camera, power down the device, replace the camera module, and then reboot. The new module works automatically.
To create and apply a device tree overlay file:

Add the .dtsi file to the camera configuration .dtsi file.
Set the status of your device tree nodes to “disabled”:
```
imx185_cam0: imx185_a@1a {
    status = "disabled";
};
```

Add the overlay information as fragments below to a new .dts file like this:

<top>/hardware/nvidia/platform/t19x/common/kernel-dts/t19x-common-modules/tegra194-camera-overlay-file.dts

#You can also see the camera DTB overlay files provided with current release for example.

Update the .dts file with proper overlay information and a compatible string:

overlay-name = "Jetson Camera Dual-IMX274";
jetson-header-name = "Jetson AGX Xavier CSI Connector";
compatible = "nvidia,p2822-0000+p2888-0001";

fragment@0 {
   target= “<&imx185_cam0>”;
   board_config {
     ids = "LPRD-dual-imx274-002" ;
     sw-modules = “kernel”;
   };
   __overlay__ {
     status = “okay”;
   };
};
fragment@1 {
   ... ... ...
};

Compile the .dts file to generate a .dtbo file. Move the .dtbo file to flash_folder/kernel/dtb/ before flashing.

Add this line to the <board>.conf file, which is used for flashing the device:

OVERLAY_DTB_FILE=”${OVERLAY_DTB_FILE},tegra194-camera-overlay-file.dtbo”;

# The line causes the following steps to be performed:
# - If a specific camera board is found when the kernel boots, the override data is applied to
    that camera board’s tree nodes.
# - The tree nodes are made available for the system to use.

UEFI Adaptation¶

Sources and Compilation¶

Boot Order Selection¶

Supported Boot Device and the Default Boot Order¶

Selecting the Boot Device in the UEFI¶

Customizing the Default Boot Order in the Configuration File¶

Customizing the Default Boot Order in L4TConfiguration.dtbo in the BSP Directory¶

Customize the Default Boot Order in the L4TConfiguration.dts in UEFI Source¶

Overriding the Default Boot Order During Flashing¶

Customizing the Default Boot Order in the UEFI Menu¶

Boot Mode Selection¶

Customizing the Default Boot Mode in the Configuration File¶

Customizing the Default Boot Mode in L4TConfiguration.dtbo in the BSP Directory¶

Customizing the Default Boot Mode in L4TConfiguration.dts in the UEFI Source¶

Customizing the Default Boot Mode in the UEFI Menu¶

Customized Logo:¶

DTB Support¶