EDK II UEFI Driver Writer's Guide
EDK II UEFI Driver Writer's Guide
EDK II UEFI Driver Writer's Guide
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.2 Other Testing

There are other tests that can be performed from within the UEFI shell. These are not testing a specific protocol, but are testing functionality and for other coding practices.

Table 41-Other Shell Testing Procedures

Shell Command Sequence

What it tests

Shell> Memmap Shell> Dh Shell> Load DriverName.efi Shell> Memmap Shell> Dh Shell> Unload DriverHandle Shell> Memmap Shell> Dh

Tests for incorrectly matched up DriverEntryPoint and Unload() functions. This catches memory allocation that is not unallocated, and catches protocols that are installed and not uninstalled, etc.

Shell> Memmap Shell> Connect DeviceHandle DriverHandle Shell> Memmap Shell> Disconnect DeviceHandle DriverHandle Shell> Memmap Shell> Reconnect DeviceHandle Shell> Memmap

Tests for incorrectly matched up Driver Binding Start() and Stop() functions. This catches memory allocation that is not unallocated.

Shell> dh Shell> Connect DeviceHandle DriverHandle Shell> dh Shell> Disconnect DeviceHandle DriverHandle Shell> dh Shell> Reconnect DeviceHandle Shell> dh

Tests for incorrectly matched up Driver Binding Start() and Stop() functions. This catches protocols that are installed and not uninstalled.

Shell> OpenInfo DeviceHandle Shell> Connect DeviceHandle DriverHandle Shell> OpenInfo DeviceHandle Shell> Disconnect DeviceHandle DriverHandle Shell> OpenInfo DeviceHandle Shell> Reconnect DeviceHandle Shell> OpenInfo DeviceHandle

Tests for incorrectly matched up Driver Binding Start() and Stop() functions. This catches protocols that are opened and not closed.

Previous
31.3.1 Testing Specific Protocols
Next
31.3.3 Loading UEFI drivers
Last updated 3 months ago
Edit on GitHub