Intel Quark SoC X1000 User manual

Order Number: 329687-007US
Intel®Quark™SoC X1000
Board Support Package (BSP)
Build and Software User Guide
Release: 1.0.1
16 June 2014

Contents
Intel®Quark™ SoC X1000
BSP Build and Software User Guide
2 Order Number: 329687-007US
Contents
1About this document .........................................................................................4
Part 1 Building the BSP software .............................................................................................5
2Before you begin ..............................................................................................5
3Downloading software .......................................................................................7
4Building the EDKII firmware ...............................................................................8
4.1 Dependencies ........................................................................................8
4.2 Pre build setup.......................................................................................8
4.2.1 Performing pre build steps in a Linux/gcc build environment ............9
4.2.2 Performing pre build steps in a Windows build environment .............9
4.3 Building all the EDKII Firmware validated build configurations [Linux build
environment only] ................................................................................10
4.4 Building a single EDKII Firmware build configuration .................................11
4.5 EDKII firmware build standalone output files ............................................12
5Building the GRUB OS loader [Linux build environment only].................................13
6Creating a file system and building the kernel using Yocto
[Linux build environment only] .........................................................................15
6.1 Applying a custom patch to the Linux kernel using Yocto (optional) .............17
7Building the Linux* cross compile toolchain using Yocto [Linux build environment only]18
8Creating a flash image for the board [Linux build environment only].......................20
8.1 Using the SPI Flash Tools ......................................................................20
9Patching flash binary files using platform data file................................................22
10 Programming flash on the board using serial interface ..........................................24
10.1 Programming flash using UEFI shell ........................................................24
10.2 Programming flash using Linux* run-time system .....................................27
11 Programming flash on the board using DediProg..................................................28
12 Booting the board from SD card ........................................................................29
Part 2 Using the BSP Software..............................................................................................31
13 Capsule update...............................................................................................31
14 Capsule recovery ............................................................................................32
15 Signing files (secure SKU only) [Linux build environment only] ..............................33
16 Enabling the OpenOCD debugger ......................................................................35
Appendix A Related documents..........................................................................................36

Contents
Intel®Quark™ SoC X1000
BSP Build and Software User Guide
Order Number: 329687-007US 3
Revision History .................................................................................................................37
Legal Disclaimers................................................................................................................38

About this document
Intel®Quark™ SoC X1000
BSP Build and Software User Guide
4 Order Number: 329687-007US
1About this document
This document, the Intel®Quark™SoC X1000 Board Support Package (BSP) Build and
Software User Guide, is divided into two major sections:
Part 1 Building the BSP Software contains instructions for installing and
configuring the Intel®Quark™SoC X1000 Board Support Package sources.
Part 2 Using the BSP Software provides information on BSP software features
and functionality.
Use this document to create an image to boot on your Quark-based board, and to
learn more about BSP software features.
The intended audience for this document are hardware/software engineers with
experience in developing embedded applications.
This software release supports the following software and hardware:
Board Support Package Sources for Intel®Quark™ SoC X1000 v1.0.0
Intel®Galileo Customer Reference Board (CRB) (Fab D with blue PCB)
Kips Bay Customer Reference Board (CRB) (Fab C with green PCB)
Intel®Quark™ SoC X1000 Industrial/Energy Reference Design (Cross Hill)
Intel®Quark™ SoC X1000 Transportation Reference Design (Clanton Hill)

Before you begin
Intel®Quark™ SoC X1000
BSP Build and Software User Guide
Order Number: 329687-007US 5
Part 1 Building the BSP software
This section contains the following topics:
Before you begin
Downloading software
Building the EDKII firmware
Building the GRUB OS loader [Linux build environment only]
Creating a file system and building the kernel using Yocto [Linux build environment only]
Building the Linux* cross compile toolchain using Yocto [Linux build environment only]
Creating a flash image for the board [Linux build environment only]
Patching flash binary files using platform data file
Programming flash on the board using serial interface
Programming flash on the board using DediProg
Booting the board from SD card
2Before you begin
Before you begin:
You need a host PC running either:
- Linux*; Intel recommends a 64-bit Linux system
- Microsoft* Windows* 7, x64
You need an internet connection to download third party sources.
The build process may require as much as 30 GB of free disk space.
To program the board you can use:
A serial interface using the UEFI shell or Linux* run-time (see Section 10)
A DediProg* SF100 SPI Flash Programmer (or equivalent) and the associated
flashing software (see Section 11)
An Intel®Galileo IDE (Galileo board only; see the Intel®Galileo Board Getting
Started Guide for details)
Note: Remove all previous versions of the software before installing the current version.
Individual components require very different environments (compiler options and
others). To avoid cross-pollution, the commands in each section below must
be run in a new command line window every time.

Before you begin
Intel®Quark™ SoC X1000
BSP Build and Software User Guide
6 Order Number: 329687-007US
Note: If the commands fail or timeout, it may be due to your proxy settings. Contact your
network administrator. You may find answers here:
https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy
This release has been tested with Windows* 7, 64-bit and Debian* Linux* 7.0
(Wheezy), but will work with most other Linux distributions.
Linux builds have been validated on 64-bit Linux systems and may need additional
steps for operation on 32-bit systems.

Downloading software
Intel®Quark™ SoC X1000
BSP Build and Software User Guide
Order Number: 329687-007US 7
3Downloading software
Download the BSP sources zip file from the following location:
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23197
Note: If you are using an Intel®Quark™ Reference Design board, see your Intel
representative for the appropriate software download URL.
This release is comprised of:
Board Support Package (BSP) sources:
Board_Support_Package_Sources_for_Intel_Quark_v1.0.1.7z (2.6 MB)
For customers using the Clanton Hill FFRD, additional CAN software must be
downloaded from Intel Business Link (IBL). See your Intel representative for the URL.
The CAN package comprises:
•Fujitsu CAN Firmware:
CAN_Firmware_for_Intel_Quark_v1.0.1.zip (36 kB)
If building on a Debian host PC, use the Debian-provided meta package called build-
essential that installs a number of compiler tools and libraries. Install the meta
package and the other packages listed in the command below before continuing:
# sudo apt-get install build-essential gcc-multilib vim-common

Building the EDKII firmware
Intel®Quark™ SoC X1000
BSP Build and Software User Guide
8 Order Number: 329687-007US
4Building the EDKII firmware
You need to build the open source EDKII firmware for the Intel®Quark™ SoC.
Additional details may be found here:
www.tianocore.sourceforge.net
http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Getting_Started
_with_EDK_II
4.1 Dependencies
Linux* build environment dependencies:
Python 2.6 or 2.7 (Python 3.x not supported)
GCC and G++ (tested with GCC 4.3 and GCC 4.6)
subversion client
uuid-dev
iasl (https://www.acpica.org/downloads/linux)
Note: An ACPI5.0 compatible version is required.
Windows* build environment dependencies:
Python 2.6 or 2.7 (Python 3.x not supported)
Microsoft* Visual Studio* 2008 Professional.
The Intel®Quark™ SoC EDKII build is validated with the Win7 x64 /
VS2008x86 option shown in
http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Windows_syste
ms_ToolChain_Matrix
In addition, the quarkbuild.bat below enforces the x86 postfix onto the Visual
Studio* option for building under x64 Windows.
TortoiseSVN (1.4.2.8580 or later) installed with optional SVN command line tools.
iASL Windows binaries (https://www.acpica.org/downloads/binary-tools)
Note: An ACPI5.0 compatible version is required.
4.2 Pre build setup
The following steps are done once to prepare the EDKII workspace directory with the
required source code before commencing the actual firmware build.
1. Create the EDKII workspace directory and extract the contents of the Intel®
Quark™ SoC EDKII BSP into this directory. The file will have the name
Quark_EDKII_<version>.tar.gz. After the contents have been extracted the

Building the EDKII firmware
Intel®Quark™ SoC X1000
BSP Build and Software User Guide
Order Number: 329687-007US 9
files quarkbuild.sh and quarkbuild.bat should be in the root of the created
workspace directory.
2. Fetch the upstream core EDKII packages using svn_setup.py and the SVN
command line tool.
3. Optionally, if OpenSSL is required by the build configuration in Section 4.3 or
Section 4.4 following, then perform the steps in the
CryptoPkg/Library/OpensslLib/Patch-HOWTO.txt file.
4.2.1 Performing pre build steps in a Linux/gcc build
environment
Open a new terminal session and enter the following commands:
# sudo apt-get install build-essential uuid-dev iasl subversion
# tar -xvf Quark_EDKII_*.tar.gz
# cd Quark_EDKII*
# ./svn_setup.py
# svn update
4.2.2 Performing pre build steps in a Windows build
environment
Use a preferred tool to extract the Quark_EDKII_*.tar.gz to a user created EDKII
Workspace directory and run the cmd.exe Windows command. Then, issue the
following commands:
>cd %USER_SELECTED_EDKII_WORKSPACE_DIR%
>.\svn_setup.py
>svn update
Note: The svn update command can take a few minutes to complete depending on the
speed of your internet connection.
Note: If these commands fail, it may be due to your proxy settings. Contact your network
administrator. You may find answers about proxy settings here:
https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy
Note: The examples above do not show the optional OpenSSL pre build step described in the
CryptoPkg/Library/OpensslLib/Patch-HOWTO.txt file.

Building the EDKII firmware
Intel®Quark™ SoC X1000
BSP Build and Software User Guide
10 Order Number: 329687-007US
4.3 Building all the EDKII Firmware validated build
configurations [Linux build environment only]
This section is only supported in Linux Build environments. The buildallconfigs.sh
file is used to build all the validated EDKII build configurations. Open a terminal
window and cd to the Quark_EDKII* directory created in Section 4.2.1 above.
The script has the following options:
buildallconfigs.sh [GCC43 | GCC44 | GCC45 | GCC46 | GCC47] [PlatformName]
GCC4x GCC flags used for this build. Set to the version of GCC
you have installed.
Note: Validated with GCC43; tested on GCC46.
[PlatformName] Name of the platform package you want to build.
Example usage:
Create a build for an Intel® Quark™ SoC platform based on GCC version 4.6:
./buildallconfigs.sh GCC46 QuarkPlatform
Note: Ensure the selected version of GCC matches the one installed on the system by
running the gcc --version command.
The build output can be found in the following directories:
Build/QuarkPlatform/<Config>/<Target>_<Tools>/FV/FlashModules/
Contains EDKII binary modules
Build/QuarkPlatform/<Config>/<Target>_<Tools>/FV/Applications/
Contains UEFI shell applications, including CapsuleApp.efi
Where:
<Config> = PLAIN | SECURE
<Target> = DEBUG | RELEASE
<Tools> = GCC43 | GCC44 | GCC45 | GCC46 | GCC47
In Section 8 you will run a script that creates a symbolic link to the directory where
the EDK binaries are placed.

Building the EDKII firmware
Intel®Quark™ SoC X1000
BSP Build and Software User Guide
Order Number: 329687-007US 11
4.4 Building a single EDKII Firmware build
configuration
This section is supported in Linux and Windows build environments. Use
quarkbuild.sh in a Linux terminal window or quarkbuild.bat in a Windows
command prompt (created by running cmd.exe) and the cd command to change
directory to the root of the EDKII workspace directory created in Section 4.2 above.
Build usage:
quarkbuild [-r32 | -d32 | -clean]
[GCC43 | GCC44 | GCC45 | GCC46 | GCC47 | subst drive letter]
[PlatformName] [-DSECURE_LD (optional)] [-DTPM_SUPPORT (optional)]
The following is the list of options for the quarkbuild.sh and quarkbuild.bat build
commands:
-clean Delete the build files/folders
-d32 Create a DEBUG build
-r32 Create a RELEASE build
GCC4x LINUX ONLY: GCC flags used for this build. Set to the
version of GCC you have installed.
NOTE: Validated with GCC43; tested on GCC46.
subst drive letter WINDOWS ONLY: quarkbuild.bat uses the letter
specified here with the Windows subst command to
associate a drive letter with the EDKII workspace
directory path. Associating a drive letter with the
EDKII workspace directory reduces flash space
requirements for debug executables.
[PlatformName] Name of the Platform package you want to build
[-DSECURE_LD] Create a Secure Lockdown build (optional)
[-DTPM_SUPPORT] Create an EDKII build with TPM support (optional)
Note: This option has a one-time prerequisite
described in the
CryptoPkg\Library\OpensslLib\Patch-HOWTO.txt
file.
For more details on TPM (Trusted Platform Module),
see the Intel®Quark™ SoC X1000 UEFI Firmware
Writer’s Guide.

Building the EDKII firmware
Intel®Quark™ SoC X1000
BSP Build and Software User Guide
12 Order Number: 329687-007US
Linux example usage:
Create a secure lockdown RELEASE build for an Intel®Quark™SoC platform based on
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 “Creating a flash image for the board” is not required if the user only
requires EDKII firmware in the SPI Flash on Intel®Quark™ SoC Open SKU silicon.
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 Section 9 following to create the final image for the board.
The platform data python script referenced in the Section 9 can be used in Linux*
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 Section 10. Applying this file only updates the EDKII components of
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
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.)
.\Build\....\FV\RemediationModules\CapsuleApp.efi
UEFI application referenced in Section 10.1 following.
.\Build\....\FV\RemediationModules\FVMAIN.fv
Recovery file that can be used in Section 14 below. This version of the file only
has the EDKII SPI flash images.

Building the GRUB OS loader [Linux build environment only]
Intel®Quark™ SoC X1000
BSP Build and Software User Guide
Order Number: 329687-007US 13
5Building the GRUB OS loader
[Linux build environment only]
Note: GRUB is provided in two places: inside the meta-clanton Yocto BSP or independently.
If you will run Yocto, skip this section and use the file output by Yocto in this
directory: yocto_build/tmp/deploy/images/grub.efi
If you are only interested in building a Flash image without Linux and not in using
Yocto, then proceed through this section.
Tip: If you want to build a Flash image without a Yocto Linux system (for example,
because you plan to boot a larger Yocto Linux system from an SD card or USB stick),
you should modify the appropriate layout.conf file and delete the sections for
bzImage and core-image-minimal-initramfs-clanton.cpio.gz.
Dependencies:
GCC (tested with version 4.3.4 and 4.6.3, and libc6-dev-i386)
gnu-efi library (tested with version >= 3.0)
GNU Make
Autotools (autoconf and libtool)
Python 2.6 or higher
git
gcc-multilib
texinfo
This GRUB build requires the 32 bit gnu-efi library which is included with many Linux
distributions. Alternatively, you can download the latest version from:
http://sourceforge.net/projects/gnu-efi/files
Unpack and compile the gnu-efi library using the commands:
# tar -xvf gnu-efi*
# cd gnu-efi*/gnuefi
# make ARCH="ia32"
# cd -
To build GRUB, first open a new terminal session, extract the grub package, and
run the gitsetup.py script. The script downloads all the upstream code required for
grub and applies the patch.
Note: If you are not using Debian and had to manually install gnu-efi in a non-system
location, then you must point GNUEFI_LIBDIR at the location where gnu-efi was
compiled or installed.

Building the GRUB OS loader [Linux build environment only]
Intel®Quark™ SoC X1000
BSP Build and Software User Guide
14 Order Number: 329687-007US
Run the following commands:
# sudo apt-get install git autoconf
# tar -xvf grub-legacy_*.tar.gz
# cd grub-legacy_*
# ./gitsetup.py
# cd work
# autoreconf --install
# export CC4GRUB='gcc -m32 -march=i586 -fno-stack-protector'
# export GNUEFI_LIBDIR=/full/path/to/gnu-efi-3.0/gnuefi/
# CC="${CC4GRUB}" ./configure-quark.sh
# make
# cd -
Note: If these commands fail, it may be due to your proxy settings. Contact your network
administrator. You may find answers about proxy settings here:
https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy
The required output from this build process is the work/efi/grub.efi file.

Creating a file system and building the kernel using Yocto [Linux build environment only]
Intel®Quark™ SoC X1000
BSP Build and Software User Guide
Order Number: 329687-007US 15
6Creating a file system and
building the kernel using Yocto
[Linux build environment only]
Dependencies:
git
diffstat
texinfo
gawk
chrpath
file
Note: git requires proxy configuration. If these commands fail, it may be due to your proxy
settings. Contact your network administrator. You may find answers about proxy
settings here: https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy
Use Yocto to create a root file system and kernel that boots the system from an SD
card or USB key. Do not run any of the commands in this section as root.
Note: See Section 7 to build development tools (gcc) for the Linux* operating system.
To avoid a known issue unzipping packages with long file paths, extract the
meta-clanton tarball into a directory with a short path, for example /tmp.
First, open a new terminal session, extract the Yocto layer, and run the setup.sh
script to download the external sources required for the Yocto build:
# sudo apt-get install diffstat gawk chrpath
# tar -xvf meta-clanton*.tar.gz
# cd meta-clanton*
# ./setup.sh
Note: The setup.sh script takes no parameters. To build the root file system and kernel for
the Intel®Galileo board, see the commands below.
Next, source the oe-init-build-env command to initialize the Yocto build
environment, and run bitbake <target> to build the root file system and kernel. You
will use SoC-specific <target> commands described below.
Note: If you need to patch the Linux kernel (optional), skip to Section 6.1 and apply the
patch before running the bitbake command.

Creating a file system and building the kernel using Yocto [Linux build environment only]
Intel®Quark™ SoC X1000
BSP Build and Software User Guide
16 Order Number: 329687-007US
Two build methods are supported; the output is slightly different for each one. The
commands are different for the Intel®Galileo board.
Note: You cannot perform the following build methods sequentially, they are mutually
exclusive. If you want both builds, you must perform them on two completely different
and isolated directories.
Build a small Linux for SPI Flash
For the Intel®Galileo board, run:
# source poky/oe-init-build-env yocto_build
# bitbake image-spi-galileo
For the Intel®Galileo board, output files are found in ./tmp/deploy/images/ and
include:
image-spi-galileo-clanton.cpio.gz
image-spi-galileo-clanton.cpio.lzma
bzImage
grub.efi
For other supported boards (not Intel®Galileo), run:
# source poky/oe-init-build-env yocto_build
# bitbake image-spi
Output files are found in ./tmp/deploy/images/ and include:
image-spi-clanton.cpio.gz
image-spi-clanton.cpio.lzma
bzImage
grub.efi
Build a full-featured Linux for SD card or USB stick
Note: A complete Yocto build can take several hours to complete, depending on your
internet connection speed and your machine’s specifications.
For the Intel®Galileo board, run:
# source poky/oe-init-build-env yocto_build
# bitbake image-full-galileo
For the Intel®Galileo board, output files are found in ./tmp/deploy/images/ and
include:
image-full-galileo-clanton.ext3
core-image-minimal-initramfs-clanton.cpio.gz
bzImage
grub.efi
boot (directory)
For other supported boards (not Intel®Galileo), run bitbake image-full as
shown below:
# source poky/oe-init-build-env yocto_build
# bitbake image-full
Output files are found in ./tmp/deploy/images/ and include:
image-full-clanton.ext3
core-image-minimal-initramfs-clanton.cpio.gz

Creating a file system and building the kernel using Yocto [Linux build environment only]
Intel®Quark™ SoC X1000
BSP Build and Software User Guide
Order Number: 329687-007US 17
bzImage
grub.efi
boot (directory)
The kernel and root file system (bzImage and image-nnnn.gz, respectively) can be
copied onto a USB stick or SD card and booted from grub. Also, the file grub.conf
must be located in the /boot/grub/ directory of the USB stick or SD card.
6.1 Applying a custom patch to the Linux kernel using
Yocto (optional)
If you need any customization of your kernel (such as additional debug statements or
custom driver behavior), then you may need to patch the Linux kernel. This optional
step must be done before you run the bitbake command.
1. For customization of Yocto source code, extract the updates to a patch from git
using the git diff or git format-patch commands.
2. Copy the patch to the location below:
$ cp mypatch.patch /PATH/TO/MY_BSP/meta-clanton/meta-clanton-
bsp/recipes-kernel/linux/files/
3. Locate the bitbake recipe file:
/PATH/TO/MY_BSP/meta-clanton-bsp/recipes-kernel/linux/linux-yocto-
clanton_3.8.bb
4. Append the following line:
SRC_URI += "file://mypatch.patch"
For example:
printf '%s\n' 'SRC_URI += "file://mypatch.patch"' >> linux-yocto-
clanton_3.8.bb
5. Return to Section 6 and run the bitbake command to get new images.
More information can be found here:
http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-
SRC_URI
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#platdev-
appdev-devshell

Building the Linux* cross compile toolchain using Yocto [Linux build environment only]
Intel®Quark™ SoC X1000
BSP Build and Software User Guide
18 Order Number: 329687-007US
7Building the Linux* cross
compile toolchain using Yocto
[Linux build environment only]
The steps to build the cross compile toolchain are the same as the steps for the Yocto
root file system and kernel build as described in Section 6, with the exception of the
bitbake command arguments.
To build the tool chain, open a new terminal session and follow the steps in
Section 6 but modify the bitbake command as follows:
# bitbake image-full -c populate_sdk
The same files can be used for both builds, however, you must source the
poky oe-init-build-env yocto_build every time you use a new terminal.
The output of the build process is a script that installs the toolchain on another
system:
clanton-tiny-uclibc-x86_64-i586-toolchain-1.4.2.sh
The script is located in ./tmp/deploy/sdk
Note: The script may change your environment significantly, thus breaking other, non-Yocto
tools you might be using (including anything which uses Python). You must open a
new terminal session to source the Yocto environment and run make, and run all
your other commands in other terminal sessions.
When you are ready to compile your application, first run the source command below
to define default values for CC, CONFIGURE_FLAGS, and other environment variables,
then you can compile:
# source /opt/clanton-tiny/1.4.2/environment-setup-x86_32-poky-linux
# ${CC} myfile.c -o myfile
or
# source /opt/clanton-tiny/1.4.2/environment-setup-x86_64-poky-linux
# ${CC} myfile.c -o myfile
For general details, see the Yocto Application Development Toolkit (ADT) information:
https://www.yoctoproject.org/tools-resources/projects/application-development-
toolkit-adt
Instructions about adding a package to the Linux build may be found here:
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-
extend-customimage-localconf
Quark Linux uses uclibc, which is a C library optimized for embedded systems. This
enables a very small Linux that can fit into SPI flash with the UEFI bootloader and
Grub OS loader.

Building the Linux* cross compile toolchain using Yocto [Linux build environment only]
Intel®Quark™ SoC X1000
BSP Build and Software User Guide
Order Number: 329687-007US 19
If you do not have any size constraints, you can change the C library to a more fully
featured C library. Detailed instructions are here:
http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html
specifically how to change the TCLIBC variable selecting the C library to be used.
To build an eglibc image, overwrite the default value of the DISTRO variable as
follows:
DISTRO="clanton-full" bitbake <image-name>

Creating a flash image for the board [Linux build environment only]
Intel®Quark™ SoC X1000
BSP Build and Software User Guide
20 Order Number: 329687-007US
8Creating a flash image for the
board [Linux build environment
only]
Dependencies:
GCC
GNU Make
EDKII Firmware Volume Tools (base tools)
OpenSSL 0.9.8w
libssl-dev
8.1 Using the SPI Flash Tools
The SPI Flash Tools, along with the metadata and flash image configuration in the
sysimage archive, are used to create a Flash.bin file that can be installed on the
board and booted.
Open a new terminal session and extract the contents of the sysimage archive:
# tar -xvf sysimage_*.tar.gz
Extract and install SPI Flash Tools:
# tar -xvf spi-flash-tools*.tar.gz
Note: Extract all files to a directory that does not include the original tar files.
The sysimage* directory contains the following preconfigured layout.conf files:
release build base SKU (non-secure)
debug build base SKU (non-secure
release build secure SKU
debug build secure SKU
Depending on what kind of image you want to build, you must be in either the
sysimage.CP-8M-debug or the sysimage.CP-8M-release directory.
The layout.conf file defines how the various components will be inserted into the
final Flash.bin file to be flashed onto the board. The layout.conf consists of a
number of [sections] with associated address offsets, file names, and parameters.
Each section must reference a valid file, so it is necessary to update the paths or
create symbolic links to the valid files.