Edkii Firmware Build Standalone Output Files - Intel Quark SoC X1000 User Manual

Linux example usage:
Create a secure lockdown RELEASE build for an Intel
GCC version 4.3:
./quarkbuild.sh -r32 GCC43 QuarkPlatform –DSECURE_LD
Windows example usage:
Create a DEBUG build for a Quark platform. After executing quarkbuild.bat, a virtual
drive S: is created which is rooted to EDKII workspace directory.
>.\quarkbuild.bat –d32 S QuarkPlatform
4.5

EDKII firmware build standalone output files

Chapter 8
requires EDKII firmware in the SPI Flash on Intel
Sections 4.3 and 4.4 above create the following EDKII standalone output files:
 .\Build\....\FV\FlashModules\Flash-EDKII-missingPDAT.bin
Full 8 MB image for manufacture with just the EDKII SPI flash images. The user is
still expected to use
The platform data python script referenced in the
or Windows* build environments.
 .\Build\....\FV\RemediationModules\Flash-EDKII.cap
Capsule with just EDKII flash images that can be used instead of the capsule file
referenced in
the SPI flash (as provided in the capsule). All other SPI flash assets remain intact.
Note: If programming Flash-EDKII.cap on a board, it is required that the SPI
 .\Build\....\FV\RemediationModules\CapsuleApp.efi
UEFI application referenced in
 .\Build\....\FV\RemediationModules\FVMAIN.fv
Recovery file that can be used in
has the EDKII SPI flash images.
Intel ® Quark™ SoC X1000
BSP Build and Software User Guide
12
"Creating a flash image for the board" is not required if the user only
Section 9
Section 10. Applying this file only updates the EDKII components of
Flash version of the target board is at production level V1.0.0 or later.
(Provided by the Flash-missingPDAT.cap or Flash+PlatformData.bin
files referenced in the sections following.)
® Quark™ SoC platform based on
® Quark™ SoC Open SKU silicon.
following to create the final image for the board.
Section 9
Section 10.1 following.
Section 14 below. This version of the file only
Building the EDKII firmware
can be used in Linux*
Order Number: 329687-007US