Gary Lin b337e80f46 Vlv2TbltDevicePkg: Reorganize the libraries | 5 years ago | |
---|---|---|
.. | ||
AdvancedFeaturePkg | 5 years ago | |
BoardModulePkg | 5 years ago | |
ClevoOpenBoardPkg | 5 years ago | |
DebugFeaturePkg | 5 years ago | |
KabylakeOpenBoardPkg | 5 years ago | |
MinPlatformPkg | 5 years ago | |
PurleyOpenBoardPkg | 5 years ago | |
QuarkPlatformPkg | 5 years ago | |
Tools | 5 years ago | |
UserInterfaceFeaturePkg | 5 years ago | |
Vlv2TbltDevicePkg | 4 years ago | |
Readme.md | 5 years ago | |
build.cfg | 5 years ago | |
build_bios.py | 5 years ago |
The Minimum Platform is a software architecture that guides uniform delivery of Intel platforms enabling firmware solutions for basic boot functionality with extensibility built-in.
Package maintainers for the Minimum Platform projects are listed in Maintainers.txt.
The key elements of the architecture are organized into a staged boot approach where each stage has requirements and
functionality for specific use cases. The generic control flow through the boot process is implemented in the
MinPlatformPkg
.
The generic nature of the tasks performed in MinPlatformPkg lends to reuse across all Intel platforms with no
source modification. Details for any particular board are made accessible to the MinPlatformPkg through a well-defined
statically linked board API. A complete platform solution then consists of the MinPlatformPkg and a compatible board
package.
The board packages supported by Intel follow the naming convention <xxx>OpenBoardPkg where xxx refers to the
encompassing platform name for a particular platform generation. For example, the KabylakeOpenBoardPkg
contains the
board code for Intel Kaby Lake reference systems. Intel uses the moniker «OpenBoardPkg» to indicate that this package
is the open source board code. A closed source counterpart may exist which simply uses «BoardPkg». Both directly use
the MinPlatformPkg from edk2-platforms.
Stage selection is controlled via the PCD gMinPlatformPkgTokenSpaceGuid.PcdBootStage
in MinPlatformPkg.dec
.
The stage should be configured in the board package DSC file to the appropriate value. For example, a board may disable
all advanced features by setting this value to 4 instead of 6. This may be used to improve boot time for a particular
use case. Decrementing the stage can also be used for debug since only the actions required for that stage objective
should be executed. As an example, ACPI initialization is not required for a Stage 3 boot.
The stages are defined as follows:
Stage | Functional Objective | Example Capabilities |
---|---|---|
I | Minimal Debug | Serial port output, source debug enabled, hardware debugger enabled |
II | Memory Functional | Basic hardware initialization necessary to reach memory initialization, permanent memory available |
III | Boot to UI | Simple console input and output to a UI, UEFI shell |
IV | Boot to OS | Boot an operating system with the minimally required features |
V | Security Enable | UEFI Secure Boot, TCG measured boot, DMA protections |
VI | Advanced Feature Enable | Firmware update, power management, non-essential I/O |
A UEFI firmware implementation using MinPlatformPkg is constructed using the following pieces.
EDK II |
Intel® FSP |
Minimum Platform (MinPlatformPkg ) |
Board Support (<xxx>OpenBoardPkg) |
KabylakeOpenBoardPkg
contains board implementations for Kaby Lake systems.PurleyOpenBoardPkg
contains board implementations for Purley systems.ClevoOpenBoardPkg
contains board implementations for Clevo systems.The board package follows the standard EDK II package structure with the following additional elements and guidelines:
Shared resources in the package root directory can include interfaces described in header files, library instances, firmware modules, binaries, etc. The UEFI firmware implementation is built using the process described below from the board-specific directory.
A board package must implement the board APIs defined in the MinPlatformPkg even if a «NULL» implementation is used to return back to the minimum platform caller.
C:\ASL
to match default tools_def.txt configuration.C:\NASM
to match default tools_def.txt configuration.C:\Python27
to match default tools_def.txt configuration.Create a new directory for the EDK II WORKSPACE.
Download below repository to this WORKSPACE:
edk2 repository
git clone https://github.com/tianocore/edk2.git
edk2-platforms repository
git clone https://github.com/tianocore/edk2-platforms.git
edk2-non-osi repository
git clone https://github.com/tianocore/edk2-non-osi.git -b devel-MinPlatform
FSP repository
git clone https://github.com/IntelFsp/FSP.git
Building with the python script
| Argument | Function | | ———————-|————————————-| | -h, –help | show this help message and exit | | –platform, -p | the platform to build | | –toolchain, -t | tool Chain to use in build process | | –DEBUG, -d | debug flag | | –RELEASE, -r | release flag | | –TEST_RELEASE, -tr | test Release flag | | –RELEASE_PDB, -rp | release flag | | –list, -l | lists available platforms | | –cleanall | cleans all | | –clean | cleans specified platform | | –capsule | capsule build enabled | | –silent | silent build enabled | | –performance | performance build enabled | | –fsp | fsp wrapper build enabled | | –fspapi | API mode fsp wrapper build enabled | | –hash | Enable hash-based caching | | –binary-destination | create cache in specified directory | | –binary-source | Consume cache from directory | | |
For more information on build options
Note
Configuration Files
Workspace view of the build scripts
WORKSPACE |——edk2 |——edk2-non-osi |——edk2-platforms | |—Platform | | |–Intel | | |——build.cfg: Default build settings. These are overridden by | | | platform specific settings (build_config.cfg) and | | | then command-line settings. | | | | | |——build_bios.py: Main build script. Generic pre-build, build, | | | post-build, and clean functions. | | | | | |——ClevoOpenBoardPkg | | | |——N1xxWU | | | |—build_config.cfg: N1xxWU specific build | | | settings environment variables. | | | | | |——KabylakeOpenBoardPkg | | | |——KabylakeRvp3 | | | |—build_config.cfg: KabylakeRvp3 specific | | | | build settings, environment variables. | | | |—build_board.py: Optional board-specific pre-build, build | | | and clean post-build functions. | | |——PurleyOpenBoardPkg | | | |——BoardMtOlympus | | | |—build_config.cfg: BoardMtOlympus specific | | | | build settings, environment variables. | | | |—build_board.py: Optional board-specific pre-build, | | | | build, post-build and clean functions. |——FSP
Building with the batch scripts KabylakeOpenBoardPkg does not support batch scripts, please use build_bios.py.
For PurleyOpenBoardPkg
The validated version of iasl compiler that can build MinPurley is 20180629. Older version may generate ACPI build errors.
For ClevoOpenBoardPkg
Users with access to the Intel proprietary FITC tool and ME ingredients can build full images for flash (BIOS + ME + DESC).
Users can also flash the UEFI firmware image to the highest area of the flash region directly.
KabylakeOpenBoardPkg
PurleyOpenBoardPkg
ClevoOpenBoardPkg
If you would like to help but are not sure where to start some areas currently identified for improvement include:
Please feel free to contact Michael Kubacki (michael.a.kubacki at intel.com) and Isaac Oram (isaac.w.oram at intel.com) if you would like to discuss contribution ideas.