Microsoft ASL compiler
Version 5.0 of the Microsoft ACPI source language (ASL) compiler supports the features in the Advanced Configuration and Power Interface Specification, Revision 5.0 (ACPI 5.0 specification). The ASL compiler is distributed with the Windows Driver Kit (WDK) 8.1. Look for the Asl.exe executable file in the Tools\arm\ACPIVerify, Tools\x86\ACPIVerify, or Tools\x64\ACPIVerify directory of your installed WDK.
The Microsoft ASL compiler supports several command line options. To list the available command line options, run the command "
asl /?" in a Command Prompt window.
The ASL compiler supports the following command line options:
asl /? asl [/nologo] /d <BinFile> asl [/nologo] /u [/Fa=<ASMFile>] [/Fl=<LSTFile>] [/Fn=<NSDFile>] <AMLFile> asl [/nologo] /tab=<TabSig> [/c] [/Fa=<ASMfile>] [/Fl=<LSTFile>] [/Fn=<NSDFile>] asl [/nologo] [/Fo=<AMLFile>] [/Fa=<ASMFile>] [/Fl=<LSTFile>] [/Fn=<NSDFile>] <ASLFile>
|?||Print this help message.|
|nologo||Suppress the logo banner.|
|Fo=<AMLFile>||Override the AML file name in the DefinitionBlock.|
|Fa=<ASMFile>||Generate a .ASM file with the name <ASMFile>.|
|Fl=<LSTFile>||Generate a .LST file with the name <LSTFile>.|
|Fn=<NSDFile>||Generate a NameSpace Dump file with the name <NSDFile>.|
|d||Dump the binary file in text form.|
|u||Unassemble an AML file to a .ASL file (default) or a .LST file.|
|tab=<TabSig>||Unassemble ASL table to a .ASL file (default) or a .LST file. Dump non-ASL table to a .TXT file. If <TabSig> is '*', all tables are dumped to ACPI.TXT. <TabSig> can also be the physical address of the table.|
|c||Create binary files from tables.|
During system development, it is useful to have a way to simulate various ACPI BIOS constructs and test them on the development system. Starting with Windows XP, the Windows operating system allows certain ACPI tables to be loaded from the Windows registry instead of from the PC's BIOS ROM. Use of this feature requires administrator privileges, and also requires that test signing be enabled on the system. For systems that support UEFI Secure Boot, test signing cannot be enabled, and the compiler's table-load feature cannot be used unless UEFI Secure Boot is disabled or the Windows Debug Policy is installed on the system.
To use the table-load feature, the ACPI table to be overloaded must meet the following requirements:
- The table to be overloaded must already be present in the system's BIOS ROM. For instance, the DSDT can be overloaded; however, if the machine does not have an SSDT, you cannot force an SSDT to be loaded from this registry override mechanism.
- The table must contain AML code that is normally consumed by the Windows ACPI interpreter (the Acpi.sys driver).
- The table with the highest version number will be loaded. The table loaded into the registry for testing must have a higher version number than the same table in the BIOS ROM.
- The table to be loaded must be in compiled (AML) format and loaded into the registry in the correct location, with the correct parameters specified. The mechanism described herein is designed to handle all aspects of loading the table and configuring the registry.
To load an ACPI table into the registry for test purposes, the ASL compiler is invoked as follows:
asl.exe /loadtable [-v] [-d] <AMLFile>
where AMLFile is the name of the compiled AML file that contains the table you wish to load into the registry.
Verbose mode. Turns on extra debugging output from the utility.
Delete. Removes a previously loaded AML file from the registry, and deletes all associated registry keys.
- ACPICA Documentation
- ACPI Website
- ACPI Debugging
- Acpi.sys: The Windows ACPI Driver
- Power Management and ACPI