EDK II UEFI Driver Writer's Guide
Search…
EDK II UEFI Driver Writer's Guide
Introduction
Tables
Figures
Examples
Acknowledgements
1 Introduction
2 UEFI Driver Implementation Checklist
3 Foundation
4 General Driver Design Guidelines
5 UEFI Services
6 UEFI Driver Categories
7 Driver Entry Point
8 Private Context Data Structures
9 Driver Binding Protocol
10 UEFI Service Binding Protocol
11 UEFI Driver and Controller Names
12 UEFI Driver Configuration
13 UEFI Driver Diagnostics
14 Driver Health Protocol
15 Driver Family Override Protocol
16 Driver Supported EFI Version Protocol
17 Bus-Specific Driver Override Protocol
18 PCI Driver Design Guidelines
19 USB Driver Design Guidelines
20 SCSI Driver Design Guidelines
21 ATA Driver Design Guidelines
22 Text Console Driver Design Guidelines
23 Graphics Driver Design Guidelines
24 Mass Storage Driver Design Guidelines
25 Network Driver Design Guidelines
26 User Credential Driver Design Guidelines
27 Load File Driver Design Guidelines
28 IPF Platform Porting Considerations
29 EFI Byte Code Porting Considerations
30 Building UEFI Drivers
31 Testing and Debugging UEFI Drivers
31.1 Native and EBC
31.2 Compiler Optimizations
31.3 UEFI Shell Debugging
31.3.1 Testing Specific Protocols
31.3.2 Other Testing
31.3.3 Loading UEFI drivers
31.3.4 Unloading UEFI drivers
31.3.5 Connecting UEFI Drivers
31.3.6 Driver and Device Information
31.3.7 Testing the Driver Configuration Protocol
31.3.8 Testing the Driver Diagnostics Protocols
31.4 Debugging code statements
31.5 POST codes
32 Distributing UEFI Drivers
Appendix A EDK II File Templates
Appendix B EDK II Sample Drivers
Appendix C Glossary
Powered By GitBook
31.3.3 Loading UEFI drivers
The following table lists the UEFI Shell commands that are available to load and start UEFI drivers.

Table 42-UEFI Shell commands for loading UEFI drivers

Command
Description
Load
Loads a UEFI driver from a file. UEFI driver files typically have an extension of .efi. The Load command has one important option, the -nc ("No Connect") option, for UEFI driver developers. When the Load command is used without the -nc option, then the loaded driver is automatically connected to any devices in the system that it is able to manage. This means that the UEFI driver's entry point is executed and then the UEFI Boot Service ConnectController() is called. If the UEFI driver produces the Driver Binding Protocol in the driver's entry point, then the ConnectController() call exercises the Supported() and Start() services of Driver Binding Protocol that was produced. If the -nc option is used with the Load command, then this automatic connect operation is not performed. Instead, only the UEFI driver's entry point is executed. When the -nc option is used, the UEFI Shell command connect can be used to connect the UEFI driver to any devices in the system that it is able to manage. The Load command can also take wild cards, so multiple UEFI drivers can be loaded at the same time. The code below shows the following examples of the Load command: Example 1: Loads and does not connect the UEFI driver image EfiDriver.efi. This example exercises only the UEFI driver's entry point: fs0:> Load -nc EfiDriver.efi Example 2: Loads and connects the UEFI driver image called EfiDriver.efi. This example exercises the UEFI driver's entry point and the Supported() and Start() functions of the Driver Binding Protocol: fs0:> Load EfiDriver.efi Example 3: Loads and connects all the UEFI drivers with an .efi extension from fs0:, exercising the UEFI driver entry points and their Supported() and Start() functions of the Driver Binding Protocol: `fs0:> Load .efi`
LoadPciRom
This command used to simulate the load of a PCI option ROM by the PCI bus driver. It also supports the -nc flag like the Load command, but takes the name of a PCI Option ROM file instead of an .efi file.
Previous
31.3.2 Other Testing
Next
31.3.4 Unloading UEFI drivers
Last modified 2yr ago
Copy link
Contents
Table 42-UEFI Shell commands for loading UEFI drivers