Custom UEFI and BIOS utilities for Aptio and AMIBIOS simplify the development and debug experience. AMI's Aptio firmware offers an easy transition to the Unified Extensible Firmware Interface (UEFI) specification, giving developers all the advantages of UEFI - modularity, portability, C-based coding - while retaining easy-to-use tools that facilitate manufacturing and enhance productivity. AMI's rich set of utilities for BIOS ROM image customization without rebuilding the firmware provide a clear advantage in reducing both time and cost.
AMI Firmware Update (AFU) is a scriptable command line utility for DOS, Microsoft Windows®, Linux, FreeBSD and the UEFI shell. Utilized for factory or field BIOS updates, AFU is flexible enough to update the entire Flash part or only a portion. It programs the main BIOS image, boot block or OEM configurable ROM regions.
The AMI BIOS Configuration Program (AMIBCP) for Aptio enables customers to modify parameters in a BIOS ROM without rebuilding from source. Melcohny. Developers can modify default values for BIOS setup parameters, modify default boot order in BIOS setup, view and edit sign-on and setup strings, and edit SMBIOS string data.
AMI BIOS Configuration Program (AMIBCP) The AMI BIOS Configuration Program (AMIBCP) for Aptio enables customers to modify parameters in a BIOS ROM without rebuilding from source. Developers can modify default values for BIOS setup parameters, modify default boot order in BIOS setup, view and edit sign-on and setup strings, and edit SMBIOS.
AMISCE is a command line tool which provides an easy way to update NVRAM variables, extract variables directly from the BIOS, change settings using either a text editor or a setup program and update the BIOS. AMISCE produces a script file that lists all setup questions on the system being modified by AMISCE. The user can then modify the script file and use it as input to change the current NVRAM setup variables.
AMISDE is a command line tool for exporting setup data from an Aptio ROM image, including spreadsheet applications such as Microsoft Excel®. It generates a helpful summary report of BIOS setup parameters and default values that enhances productivity in testing and manufacturing.
AMISLP allows the insertion of Microsoft System Locked Pre-Installation (SLP) key files into the BIOS image. SLP keys are used for OEM activation of Microsoft Windows® 7 and Vista®. For Windows® 8.1 and Windows® 10, the OEM Activation 3.0 eModule is used in conjunction with AFU v2.35 or greater.
AMIUCP is a utility that is used to pre-configure the Aptio Flash Utility (AFU). Users can insert and exchange the default command string and ROM image used in AFU to create a customized version of the utility. AMIUCP supports AFU v2.35 or AFUWINGUI v1.12 or later.
ChangeLogo allows developers to easily change logos displayed by Aptio at boot. The full screen 'splash' logo and small logos appearing on the main screen during POST can be replaced with custom logos. Nuclear bike game free download. ChangeLogo also allows logos to be extracted from existing Aptio ROM files.
DMIEdit is a scriptable command line utility for DOS, Microsoft Windows®, Linux and the UEFI shell. The Desktop Management Interface Editor for Aptio enables developers to modify strings associated with platform SMBIOS tables (System, Base Board, Chassis, OEM string, etc). In manufacturing, use DMIEdit to embed platform serial numbers, UUID and license keys into the SMBIOS table, which identifies platforms to management software.
The AMIKM utility program can write PK, KEK and signature database information to the target system. Please note that the SMI Variable module is required in order to use AMIKM.
Aptio's Module Management Tool (MMTool) allows developers to manage firmware file modules contained within an Aptio firmware ROM image. Use MMTool to extract, replace and insert binary components such as modules, Option ROMs, microcode patches and ROM holes using its graphical or command line interface. With MMTool, developers can also create reports on the contents of an opened ROM image.
The AMIRDT utility makes it easy for developers to dissect a UEFI ROM and produce related reports on ROM status and size. This powerful tool can dissect ROMs down to section level, dissect NVRAM Variables, compare two ROMs and search the GUIDs of a given FFS to provide a summary of their sizes from ROM.
Please contact AMI Sales for more information.
2> Open “vbios.dat” with notepad and look for the first string “Intel(R)”: just before it, there must be a number between 1034 and 1054. This number represents the version of the original vBIOS. Take note and close without saving.—记下这串数字，例如1039
3> Open the previously saved “vbios.dat” file with the Intel BMP program, using as a script file (.bsf) that of the corresponding version taken from the SKLKBL folder (in this example it is 1039).
Once opened, save the settings from: “BIOS Settings” -> “Save All” by naming the “transfer” file with the extension .ssf. We have thus saved the settings of the original vBIOS that will be transferred to the new one. Close the program.
Open “transfer.ssf” with notepad and remove ALL the line that starts with “STRING $ Signon Intel (R) …”. Save the file and close it (Doing this you have removed the old vBIOS description).—搜索字符串“STRING$ Signon INtel(R)”,移除所有以这个字符串开头的字符行
4> Open the “skl_1054.dat” file and the corresponding .bsf file in the SKLKBL folder with the Intel BMP program.
Apply the original settings to the new vBIOS with: “BIOS Settings” -> “Apply All” by selecting “transfer.ssf”. After a few moments of processing the file is ready. Save the file as new_vbios.dat and close the program.
5> Now you need to replace the OROM in the original BIOS. Open the BIOS with the UEFITool program (it is also located in the UBU folder). Using the “Search …” function (File menu) in the GUID tab, enter the first part of the values noted in step 1. (Section GUID), select “Header only” and confirm.
The result of the search with the address should appear below (Messages). Double-clicking on the line in the “Messages” window highlights a line in the “structure” window. Double-click on this line.
6> (OPTIONAL) to verify that the correct OROM portion will be replaced, from “Action” -> “Section” -> select “extract body”, choose the name vbios1.dat and save. Check with an editor (for example HxD) that vbios1.dat and vbios.dat are identical.—可选步骤，可跳过
7>with the line selected in step 5, from “Action” -> “Section” -> “replace body” and select the file new_vbios.dat. Confirm, then save the file (Save image file) with a new name and exit UEFITool. Now the BIOS has a vBIOS updated to version 1054.
The main menu of UBU appears, where some BIOS attributes are shown. If the vBIOS update has been carried out, the VBIOS version -1054 will appear.
By choosing option 2, the GOP Driver update is updated (updated version 9.0.1074), confirm by pressing 1. The GOP Driver is updated automatically. Pressing a button returns to the main menu, with the updated driver.
Choose option 7 (CPU Microcode) to proceed to the last step. A new window opens with the available Microcodes and the available options. Depending on the type and size of the BIOS there will be two microcodes (BIOS of 8 MB) or three or more (BIOS of 16 MB).
IMPORTANT NOTE: UBU can save a maximum of two microcodes even if originally there are more. This means that if you want compatibility with Coffee Lake, you need to “sacrifice” the present Kaby Lake microcode.
To proceed select option 1. The update has two successive phases: first the microcode is requested for Kaby Lake.
To enable a Coffee Lake processor select the last value (72): that will insert the relevant microcode.
UBU also asks to upgrade the Skylake microcode. I recommend that you select the BE value. The program automatically proceeds and updates the two microcodes: in the table that will appear there should be both.
Press any key and then exit with 0. Choose the name that will be given to the BIOS (it will probably be renamed as the original to have it accepted by the update module).