代码拉取完成，页面将自动刷新
UFFAF allows firmware modification as an efficient operation with scriptable approach through various interfaces with an intention to reduce manual interventions. Entire Client and Server ecosystem ranging from Silicon Validation teams to Tools teams running on different OS. UFFAF (formerly XmlCli) Interface is basically a combination of 2 methodologies, XML (System or Platform Information to be consumed in XML format) & CLI (BIOS Command Line Interface protocol which acts as an interface between BIOS & outside environment via S/W SMI or UEFI runtime interface). In short UFFAF (formerly XML CLI) is the interface methodology between BIOS & External world Tool is the combination of Python Scripts and utilities that helps the end user/automation to perform desired operations using available BIOS Driver interface.
These reference scripts provides several capabilities including but not limited to:
- Parsing Information of UEFI BIOS Firmware as per Platform Initialization Specification
- Programming/Reading BIOS knobs with CLI and GUI
- Fetching Platform XML from target
- System information
- CommandLine and web based GUI support for get and set NVAR (UEFI NVRAM variable)
- Context Menu Integration for Windows
These scripts are generic and platform/program independent (as long as BIOS on SUT BIOS supports XML CLI interface).
These scripts are provided as reference scripts and requires to have bios driver enabled in order to use the functionality.
As scripts require to read/write memory of the target device/system, valid access interface would be required which can be configured at config file.
For Offline Binary modification, these scripts provide easier way to interpret and update the data bytes of binary. Irrespective of these scripts, changing undesired data in binary could be result to unexpected behavior hence, it is individual's responsibility to make sure to use valid configuration.
As Accessing target SUT is only possible at Elevated Privilege, we recommend proceeding with caution if service API of these scripts are exposed over network.
Interface means the way to access memory and I/O of target system. This scripts needs to read/write memory in order to achieve communication with BIOS driver. These interface works only when running with elevated privileges are available. It is responsibility of user to make sure to act with caution before making modification to avoid corrupting memory/registers with unwanted data.
Before proceeding with installation, make sure you have updated python setuptools:
![dependabot[bot]-](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAYAAACNiR0NAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAC7SURBVDhPY5wdue0/AxUB46iBFIfmaBgigpCRiZEheYkHWODv738MX958Z7h34jnD+fV3Gf79+YczrHGGIcjAhPluDPPjdzKwsDMzCMrwMFjGaTG8uvOB4cTi65QZCNPNK8bJENRuw7AweTd1DASZkrTInWFJ5l6GX1//YDWUKC/DXSgKdGEHFVzIzMYEDENeBstYTYbXdz8ynFhCZhjCYvnf3/8MX15DYvncujvkxTK5eXA065Ebcgh9AAvTekkevapEAAAAAElFTkSuQmCC){kind=small}
python -m pip install --upgrade setuptools
Now Proceed to installation of XmlCli as
python -m pip install <xmlcli-x.x.x.whl> --proxy <proxy-url>
Refer Installation-Steps for more alternate installation instruction.
Need to select the interface to indicate the scripts on which access method to use (depending on which environment we expect the script to operate in).
from xmlcli import XmlCli as cli
cli.clb._setCliAccess("<access-method>")
Below are listed valid <access-method>:
| Access Method | Remarks |
|---|---|
linux |
For using linux as interface, need to open Python Prompt in root permissions. |
winrwe |
For using RW.exe as Windows interface (slow, least recommended). For more details refer winrwe/README.md |
After initializing the desired interface, the use may run following commands.
If the commands return 0, it means the operation was successful, else there was an error.
from xmlcli import XmlCli as cli
cli.clb._setCliAccess("linux") # Set desired Interface (for example `linux` if using on `linux` SUT)
from xmlcli import XmlCli as cli
cli.clb.ConfXmlCli() # Check if XmlCli is supported &/ Enabled on the current system.
Return value of cli.clb.ConfXmlCli |
Meaning |
|---|---|
| 0 | XmlCli is already supported & enabled. |
| 1 | XmlCli is not supported on the current BIOS or the System BIOS has not completed Boot. |
| 2 | XmlCli is supported but was not enabled, the script has now enabled it and SUT needs reboot to make use of XmlCli. |
from xmlcli import XmlCli as cli
# For Online
# Run common import steps and make sure `cli.clb.ConfXmlCli()` returns `0`
cli.savexml() # Save Target XML as `<Path_To_XmlCliRefScripts>/out/PlatformConfig.xml` file.
cli.savexml(r"path/to/file.xml") # Save Target XML as absolute file location for `path/to/file.xml`.
# For Offline
cli.savexml(0, r"path/to/ifwi-or-bios.bin") # Extract the XML data from desired BIOS or IFWI binary. Will Save Target XML in `<Path_To_XmlCliRefScripts>/out/` folder.
cli.savexml(r"path/to/file.xml", r"path/to/ifwi-or-bios.bin") # Extract the XML data from desired BIOS or IFWI binary. Will Save Target XML as `path/to/file.xml`.
For Online command to run successfully, the target must complete BIOS boot. For Offline mode, you need to pass the link to BIOS or IFWI binary.
Knob_A & Knob_B in the below examples are the knob names taken from the name attribute from the <biosknobs> section in the XML, it is case sensitive.from xmlcli import XmlCli as cli
cli.CvReadKnobs("Knob_A=Val_1, Knobs_B=Val_2") # Reads the desired Knob_A & Knob_B settings from the SUT and verifies them against Val_1 & Val_2 respectively.
cli.CvReadKnobs() # same as above, just that the Knob entries will be read from the default cfg file (`<Path_To_XmlCliRefScripts>/cfg/BiosKnobs.ini`).
# For Offline
cli.CvReadKnobs("Knob_A=Val_1, Knobs_B=Val_2", r"path/to/ifwi-or-bios.bin") # Reads & verifies the desired knob settings from the given BIOS or IFWI binary.
cli.CvReadKnobs(0, r"path/to/ifwi-or-bios.bin") # same as above, just that the Knob entries will be read from the `cli.clb.KnobsIniFile` cfg file instead.
# the default cfg file pointer can be programed to desired cfg file via following command.
cli.clb.KnobsIniFile = r"path/to/bios-config.ini"
For Online command to run successfully, the target must complete BIOS boot. For Offline mode, you need to pass the link to BIOS or IFWI binary.
Knob_A & Knob_B in the below examples are the knob names taken from the name attribute from the <biosknobs> section in the XML, it is case sensitive.from xmlcli import XmlCli as cli
cli.CvProgKnobs("Knob_A=Val_1, Knobs_B=Val_2") # Programs the desired Knob_A & Knob_B settings on the SUT and verifies them against Val_1 & Val_2 respectively.
cli.CvProgKnobs() # same as above, just that the Knob entries will be Programed from the default cfg file (<Path_To_XmlCliRefScripts>\cfg\BiosKnobs.ini).
# For Offline
cli.CvProgKnobs("Knob_A=Val_1, Knobs_B=Val_2", r"path/to/ifwi-or-bios.bin") # Program the desired knob settings as new default value, operates on BIOS or IFWI binary, new BIOS or IFWI binary will be generated with desired settings.
cli.CvProgKnobs(0, r"path/to/ifwi-or-bios.bin") # same as above, just that the Knob entries will be Programed from the cli.clb.KnobsIniFile cfg file instead.
# the default cfg file pointer can be programed to desired cfg file via following command.
cli.clb.KnobsIniFile = r"path/to/bios-config.ini"
# To Load Default BIOS settings on the SUT. Offline mode not supported or not Applicable.
cli.CvLoadDefaults() # Loads/Restores the default value back on the system, also shows which values were restored back to its default Value.
Offline mode not supported or not Applicable.
Knob_A & Knob_B in the below examples are the knob names taken from the name attribute from the <biosknobs> section in the XML, it is case sensitive.from xmlcli import XmlCli as cli
cli.CvRestoreModifyKnobs("Knob_A=Val_1, Knobs_B=Val_2") # Programs the desired Knob_A & Knob_B settings and restores everything else back to its default value.
cli.CvRestoreModifyKnobs() # same as above, just that the Knob entries will be Programed from the cli.clb.KnobsIniFile cfg file instead.
# the default cfg file pointer can be programed to desired cfg file via following command.
cli.clb.KnobsIniFile = r"path/to/bios-config.ini"
Offline editing of BIOS will update FV_BB section of BIOS. This is an expected to produce boot issue with Secure Boot profiles (i.e. Secure Profile images)
To make sure offline Edited BIOSes for Knob changes boot fine with Secure Profile IFWI's, user need to supply the re-signing script/pkg. This is user's full responsibility to manage an executable script which syntax should follow as:
file/to/executable/signing-resigning.bat input.bin output/path.bin
from xmlcli import XmlCli as cli
cli.fwp.SecureProfileEditing = True # if not set to True, Re-Signing Process will be skipped
cli.fwp.ReSigningFile = r'path/to/resigning/executable/ResignIbbForBtG.bat' # by default this variable is empty, please populate this variable with Re-Signing Script File Ptr
cli.CvProgKnobs('BootFirstToShell=1, EfiNetworkSupport=3', r'path/to/ifwi-or-bios.bin')
Note - Providing Secure Profile resigning script/executable is out of scope of XmlCli, User need to gather required executable in order to utilize this functionality on SecureProfile.
Only for DCG)from xmlcli import XmlCli as cli
cli.IoAccess("<operation>", "<IoPort>", "<Size>", "<IoValue>")
cli.MsrAccess("<operation>", "<MsrNumber>", "<ApicId>", "<MsrValue>")
from xmlcli import XmlCli as cli
cli.IoAccess(cli.clb.IO_WRITE_OPCODE, 0x84, 1, 0xFA)
cli.IoAccess(cli.clb.IO_READ_OPCODE, 0x84, 1)
cli.MsrAccess(cli.clb.READ_MSR_OPCODE, 0x53, 0)
cli.MsrAccess(cli.clb.WRITE_MSR_OPCODE, 0x1A0, 0, 0x1)
EFI App is located under tools/XmlCliKnobs.efi, below commands can be executed on UEFI Shell:
| Command | Description |
|---|---|
XmlCliKnobs.efi CX |
Ensure XmlCli is enabled, if it's not enable, this command helps to enable XmlCli, Reboot SUT if XmlCli was not enabled. |
XmlCliKnobs.efi -v |
Get version information of the efi App |
XmlCliKnobs.efi GX |
Generate Bios Knobs xml dump |
XmlCliKnobs.efi |
List out all possible available commands |
These modules are extension of core XmlCli API also shows example of how it can be consumed in any independent modules.
| Feature/Module | Information |
|---|---|
| Context Menu for Windows OS | Installing context menu in windows OS for frequently used APIs |
| UEFI Binary Parsing | Parsing UEFI BIOS Binary file as json information, extracting firmware volumes, ffs etc. |
| Customizing Logging | Instruction guide on customizing logging |
此处可能存在不合适展示的内容，页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容，可点击提交进行申诉，我们将尽快为您处理。
马建仓 AI 助手