Intel Quark SoC X1000 Software User's Manual page 53

SPI Flash Tools
Appendix B SPI Flash Tools
You do not need Appendixes unless necessary.
The main functionality of the SPI flash tools is provided by a Make file. By default the
Make file should be called from within a directory with a valid layout.conf and will
output a flash binary and capsule.
Example of usage is in
The Make file provides a number of targets which can be used to change the behavior
or output of the tool:
 all (default) - creates the flash binary, capsule and recovery image
 raw - create only the flash binary

capsule - create only the capsule
 recovery - creates a recovery image

clean - delete all intermediate files in the current directory
 sysimages - Search all subdirectories for a layout.conf file and if found build the
images
 sysimages-clean - as above but calls clean
 sysimages-install - as above but copies all of the output files into an "installs"
directory
There are also a number of variables which can be prefixed to the Makefile call on the
command line to modify the behavior of the tool:

KEYFILE - can be used to select an encryption key to use if assets are being signed
 LAYOUTFILE - specify the name of a layout file if it has a non-standard name
 PDAT_IN_CAPSULE - include the platform data in the capsule
 true ==> include the platform data in the capsule
 false ==> do not include the platform data in the capsule (default false)
 CAPSULE_FLAGS:
 0x00010000 ==> do NOT update MAC addresses
 0x00010001 ==> update the MAC addresses (default: 0x00010000)
 CAPSULE_SVN - update CAPSULE_SVN when changing KEYS for UEFI Secure Boot
Systems (default = 0)
Example: KEYFILE=/path/to/key.pem ../spi-flash-tools/Makefile
May 2017
Document Number: 329687-011US
Section 6.2, "Build a Small Linux for SPI
Intel® Quark™ SoC X1000 Board Support Package (BSP)
Flash".
Build and Software User Guide
53