Intel Quark SoC X1000 Safety guide

Document Number: 329687-011US
Intel® Quark™ SoC X1000 Board Support
Package (BSP)
Build and Software User Guide
May 2017

Intel® Quark™ SoC X1000 Board Support Package (BSP)
Build and Software User Guide May 2017
2 Document Number: 329687-011US
You may not use or facilitate the use of this document in connection with any infringement or other legal analysis concerning Intel products
described herein. You agree to grant Intel a non-exclusive, royalty-free license to any patent claim thereafter drafted which includes subject
matter disclosed herein.
No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document.
All information provided here is subject to change without notice. Contact your Intel representative to obtain the latest Intel product
specifications and roadmaps.
The products described may contain design defects or errors known as errata which may cause the product to deviate from published
specifications. Current characterized errata are available on request.
Copies of documents which have an order number and are referenced in this document may be obtained by calling 1-800-548-4725 or by
visiting: http://www.intel.com/design/literature.htm
Intel technologies’ features and benefits depend on system configuration and may require enabled hardware, software or service activation.
Learn more at http://www.intel.com/ or from the OEM or retailer.
No computer system can be absolutely secure.
Intel, Quark, and the Intel logo are trademarks of Intel Corporation in the U.S. and/or other countries.
*Other names and brands may be claimed as the property of others.
Copyright © 2017, Intel Corporation. All rights reserved.

Intel® Quark™ SoC X1000 Board Support Package (BSP)
May 2017 Build and Software User Guide
Document Number: 329687-011US 3
Contents
1.0 About this Document.......................................................................................................................................6
Part 1 of 2 –Building the BSP Software.............................................................................................................7
2.0 Before You Begin ...............................................................................................................................................8
3.0 Downloading Software....................................................................................................................................9
4.0 Building the EDKII Software....................................................................................................................... 10
4.1 Dependencies................................................................................................................................ 10
4.2 Pre-build Setup ............................................................................................................................ 11
4.3 Building all the EDKII Firmware Validated Build Configurations [Linux build
environment only]....................................................................................................................... 12
4.4 Building a Single EDKII Firmware Build Configuration ................................................ 13
4.5 EDKII Firmware Build Standalone Output Files.............................................................. 15
5.0 Building the GRUB OS Loader [Linux* Build Environment Only] .............................................. 17
6.0 Creating a File System and Building the Kernel Using Yocto Project* .................................... 19
6.1 Build a Full-featured Linux for SD card, USB stick or eMMC .................................... 20
6.2 Build a Small Linux for SPI Flash........................................................................................... 21
6.3 Build a fast boot Linux for SD card or eMMC................................................................... 23
6.4 Applying a Custom Patch to the Linux kernel Using Yocto Project (optional).. 26
7.0 Building the Linux* Cross Compile Toolchain Using Yocto Project* [Linux Build
Environment Only]......................................................................................................................................... 28
7.1 Creating a cross toolchain in the current build directory .......................................... 28
7.2 Creating a cross toolchain installer...................................................................................... 28
8.0 Creating a Flash Image for the Board [Linux* build environment only]................................. 31
8.1 Using the SPI Flash Tools......................................................................................................... 31
9.0 Platform Data Tool......................................................................................................................................... 33
10.0 Programming Flash on the Board Using Serial Interface.............................................................. 36
10.1 Programming Flash to Release 1.2.1................................................................................... 36
10.2 Programming flash using UEFI shell ................................................................................... 38
10.3 Programming Flash Using Linux* Run-time System .................................................... 41
11.0 Programming Flash on the Board Using DediProg.......................................................................... 42
12.0 Booting the Board From SD Card ............................................................................................................ 43
Part 2 of 2 –Using the BSP Software................................................................................................................45
13.0 Capsule Update............................................................................................................................................... 46
14.0 Capsule Recovery ........................................................................................................................................... 47
15.0 Signing Files (Secure SKU only) [Linux* build environment only] ............................................ 48
15.1 To Program Secure SPI Flash ................................................................................................. 48
15.2 To Create a Secure Boot SD/eMMC..................................................................................... 49
16.0 Enabling the OpenOCD Debugger .......................................................................................................... 51
Appendix A ......................................................................................................................................Related
Documents.................................................................................................................................................52

Intel® Quark™ SoC X1000 Board Support Package (BSP)
Build and Software User Guide May 2017
4 Document Number: 329687-011US
Appendix B ................................................................................................................................... SPI Flash
Tools ...........................................................................................................................................................53
Figures
Figure 1. Updating Process from Release 1.0.x to Release 1.2.1 .................................................................. 37
Tables
Table 1. Related Documents ....................................................................................................................................... 52

Intel® Quark™ SoC X1000 Board Support Package (BSP)
May 2017 Build and Software User Guide
Document Number: 329687-011US 5
Revision History
Date
Revision
Description
May 2017
011
Updated section 8.0
February 2016
010
Updated for Fast boot. Updated Chapters 6,9, and 15
October 2015
009
Updated Sections 4, 6, 7, 10, 13, and 14.
January 2015
008
Updated Sections 4 and 9
Added Appendix B
16 June 2014
007
General updates to coincide with the EDKII Update 1.0.2 release
including:
Updated Section 4, Building the EDKII Firmware (added Windows*
build environment).
22 May 2014
006
General updates for software release 1.0.1 including:
Updated Section 4, Building the EDKII Firmware (added TPM).
Added Section 6.1 Build a Full-featured Linux for SD card or USB Stick
Updated Section 9 Platform Data Tool (corrected platform-
data.ini filename).
Updated Section 14, Capsule Recovery (added DediProg information).
Updated with trademarked term: Intel® Quark™ SoC.
04 March 2014
005
General updates for software release 1.0.0 including:
Added Section 13 Capsule Update.
Added Section 14, Capsule Recovery.
20 January 2014
004
General updates for software release 0.9.0 including:
Added Section 4, Building the EDKII Firmware.
Added Section 10.3, Programming Flash Using Linux* Run-time
System.
Updated Section 15, Signing Files (Secure SKU only).
Removed OpenOCD details because patch is now open source.
Added Appendix A Related Documents.
15 November 2013
003
Added CapsuleApp.efi to Section 3, Downloading Software.
07 November 2013
002
General updates for software release 0.8.0 including:
Added supported boards to list of hardware.
Section 8: Changed SPI Flash tools path from clanton_peak_EDK2
to Quark_EDKII
Moved Signing Files (Secure SKU only) section to later in the
document.
15 October 2013
001
First release with software version 0.7.5.

Intel® Quark™ SoC X1000 Board Support Package (BSP)
Build and Software User Guide May 2017
6 Document Number: 329687-011US
1.0 About 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 of 2 - Building the BSP Software contains instructions for installing and
configuring the Intel® Quark™ SoC X1000 Board Support Package sources.
Part 2 of 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.2.1
Intel® Galileo Customer Reference Board (CRB) (Fab D with blue PCB)
Intel® Galileo Gen 2 Customer Reference Board (CRB)
Intel® Quark™ SoC X1000 Industrial/Energy Reference Design (Cross Hill)
Intel® Quark™ SoC X1000 Transportation Reference Design (Clanton Hill)
Intel® Quark™ SoC X1000 Air Quality Management Solution Reference Design
(Reliance Creek)

Intel® Quark™ SoC X1000 Board Support Package (BSP)
May 2017 Build and Software User Guide
Document Number: 329687-011US 7
Part 1 of 2 –Building the BSP Software
This section contains the following chapters:
2.0 Before You Begin ...............................................................................................................................................8
3.0 Downloading Software....................................................................................................................................9
4.0 Building the EDKII Software....................................................................................................................... 10
5.0 Building the GRUB OS Loader [Linux* Build Environment Only] .............................................. 17
6.0 Creating a File System and Building the Kernel Using Yocto Project* .................................... 19
7.0 Building the Linux* Cross Compile Toolchain Using Yocto Project* [Linux Build
Environment Only]......................................................................................................................................... 28
8.0 Creating a Flash Image for the Board [Linux* build environment only]................................. 31
9.0 Platform Data Tool......................................................................................................................................... 33
10.0 Programming Flash on the Board Using Serial Interface.............................................................. 36
11.0 Programming Flash on the Board Using DediProg.......................................................................... 42
12.0 Booting the Board From SD Card ............................................................................................................ 43

Intel® Quark™ SoC X1000 Board Support Package (BSP)
Build and Software User Guide May 2017
8 Document Number: 329687-011US
2.0 Before 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 (Intel® Galileo Gen 2 board only; refer to Appendix A for
User Guide 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 that follows must
be run in a new command line window every time.
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.
§

Intel® Quark™ SoC X1000 Board Support Package (BSP)
May 2017 Build and Software User Guide
Document Number: 329687-011US 9
3.0 Downloading Software
Download the BSP sources zip file from the following location:
https://downloadcenter.intel.com/download/23197/Intel-Quark-BSP
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.2.1.7z
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.2.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
§

Intel® Quark™ SoC X1000 Board Support Package (BSP)
Build and Software User Guide May 2017
10 Document Number: 329687-011US
4.0 Building the EDKII Software
You need to build the open source EDKII firmware for the Intel® Quark™ SoC. Additional
details may be found here:
www.tianocore.sourceforge.net
https://github.com/tianocore/tianocore.github.io/wiki/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
nasm
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: https://github.com/tianocore/tianocore.github.io/wiki/Windows-
systems- 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 and they should be extracted to a
C:\ASL directory.

Intel® Quark™ SoC X1000 Board Support Package (BSP)
May 2017 Build and Software User Guide
Document Number: 329687-011US 11
4.2 Pre-build Setup
The following steps are performed one time 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 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
nasm
# 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

Intel® Quark™ SoC X1000 Board Support Package (BSP)
Build and Software User Guide May 2017
12 Document Number: 329687-011US
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.
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,
“Performing pre-build Steps in a Linux/gcc Build Environment”.
The script has the following options:
buildallconfigs.sh [GCC44 | GCC45 | GCC46 | GCC47 | GCC48 | GCC49] [GCC Path]
[PlatformName]
GCC4x
GCC flags used for this build. Set to the version of GCC you have installed.
Note: Tested on GCC46. GCC43 is not supported from release 1.2 onwards.
GCC Path
Location where the GCC is installed. GCC Path is not needed for release 1.1 and
earlier.
[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: For release
1.2 onwards:
./buildallconfigs.sh GCC46 /usr/bin/ QuarkPlatform
For release 1.1 and earlier:
./buildallconfigs.sh GCC46 QuarkPlatform

Intel® Quark™ SoC X1000 Board Support Package (BSP)
May 2017 Build and Software User Guide
Document Number: 329687-011US 13
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> = GCC44 | GCC45 | GCC46 | GCC47 | GCC48 | GCC49
In Section 8, you will run a script that creates a symbolic link to the directory where the
EDK binaries are placed.
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.
Build usage:
quarkbuild [-r32 | -d32 | -clean]
[GCC44 | GCC45 | GCC46 | GCC47 | GCC48 | GCC49 | subst drive
letter] [GCC Path [PlatformName] [-DSECURE_LD (optional)] [-
DTPM_SUPPORT (optional)]
[-DSECURE_BOOT_ENABLE=TRUE (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

Intel® Quark™ SoC X1000 Board Support Package (BSP)
Build and Software User Guide May 2017
14 Document Number: 329687-011US
LINUX ONLY: GCC flags used for this build. Set to the version of GCC you have
installed.
Note: Validated and tested on GCC46. GCC43 is not supported from Release 1.2
onwards.
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).
Note: The policy decisions taken during EDKII boot for this boot option are automatically
taken on secure SKU Quark SoC hardware even if SECURE_LD build option is not
specified.
[-DTPM_SUPPORT]
Create an EDKII build with TPM support (optional)
[-DSECURE_BOOT_ENABLE=TRUE]
Create an EDKII build with UEFI Secure Boot support (optional)
Note: The TPM and UEFI Secure Boot build options require the one-time prerequisite
described in the CryptoPkg\Library\OpensslLib\Patch-HOWTO.txt file. For more
details on TPM (Trusted Platform Module) and UEFI Secure Boot, refer to the Intel®
Quark™ SoC X1000 UEFI Firmware Writer’s Guide.
Linux example usage:
Create a RELEASE build with UEFI Secure Boot and TPM support for an Intel® Quark™
SoC platform based on GCC version 4.6:
For release 1.2 onwards:
./quarkbuild.sh -r32 GCC46 /usr/bin/ QuarkPlatform -
DSECURE_BOOT_ENABLE=TRUE -DTPM_SUPPORT
For release 1.1 and earlier:
./quarkbuild.sh -r32 GCC46 QuarkPlatform -
DSECURE_BOOT_ENABLE=TRUE - DTPM_SUPPORT

Intel® Quark™ SoC X1000 Board Support Package (BSP)
May 2017 Build and Software User Guide
Document Number: 329687-011US 15
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
The built binaries are used in conjunction with Section 8 to create Spi Flash binaries for
development / manufacture, capsules for firmware update and recovery files for
firmware recovery.
Note: A CAPSULE_FLAGS option can be used with the make utility in Section 8, this option is
UEFI specific and will override the default UEFI capsule flags used by the make utility,
example > ../../spi-flash-tools*/Makefile CAPSULE_FLAGS=0x00050000. See Create an
Update Capsule in Intel® Quark™ SoC X1000 UEFI Firmware Writer’s Guide for
information on UEFI capsule flags.
4.5 EDKII Firmware Build Standalone Output Files
Section 8 Creating a Flash Image for the Board [Linux* build environment only] 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 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.cap
or Flash+PlatformData.bin files referenced in the sections that follow.)
.\Build\....\FV\RemediationModules\CapsuleApp.efi
UEFI application referenced in Section 10.2.
.\Build\....\FV\RemediationModules\FVMAIN.fv
Recovery file that can be used is included in Section 14. This version of the file only
has the EDKII SPI flash images.

Intel® Quark™ SoC X1000 Board Support Package (BSP)
Build and Software User Guide May 2017
16 Document Number: 329687-011US
Note: To change the default UEFI Capsule flags for the EDKII standalone builds the
quarkbuild.bat or quarkbuild.sh files must be changed.
§

Intel® Quark™ SoC X1000 Board Support Package (BSP)
May 2017 Build and Software User Guide
Document Number: 329687-011US 17
5.0 Building the GRUB OS Loader [Linux* Build
Environment Only]
If you will run Yocto, skip this section and use the file output by Yocto in this directory:
yocto_build/tmp/deploy/images/quark/grub.efi
If you are only interested in building a Flash image without Linux* and not in using
Yocto, then proceed through this section.
Note: GRUB is provided in two places: inside the meta-quark Yocto BSP or independently.
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-quark.cpio.gz.
Dependencies:
GCC (tested with version 4.3.4 and 4.6.3, and libc6-dev-i386)
gnu-efi-3.0u library (tested with version >= 3.0)
GNU Make
Autotools (autoconf, automake, 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.

Intel® Quark™ SoC X1000 Board Support Package (BSP)
Build and Software User Guide May 2017
18 Document Number: 329687-011US
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.
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.
§

Intel® Quark™ SoC X1000 Board Support Package (BSP)
May 2017 Build and Software User Guide
Document Number: 329687-011US 19
6.0 Creating a File System and Building the Kernel
Using Yocto Project*
Dependencies:
git
diffstat
texinfo
gawk
chrpath
lzop
file
Note: Before running git, install patchutils so that the system can patch all external
sources that are required when running setup.sh.
git requires proxy configuration. If these commands fail, it may be due to your proxy
settings. Contact your network administrator. You may also find answers and tips about
proxy settings here:
https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy
Yocto Project* can be used to create a root file system and kernel which boots from an
SD card, USB key or SPI flash. 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-
quark tarball into a directory with a short path, for example /tmp.
First, open a new terminal session, extract the Yocto Project layer, and run the
setup.sh script to download the external sources required for the Yocto Project build:
# tar -xvf meta-quark*.tar.gz
# cd meta-quark*
# ./setup.sh
Note: The setup.sh script takes no parameters.
When this scripts runs successfully, it will add additional folders such as bitbake, meta-
yocto, repo-ext, etc.

Intel® Quark™ SoC X1000 Board Support Package (BSP)
Build and Software User Guide May 2017
20 Document Number: 329687-011US
Next, source the oe-init-build-env command to initialize the Yocto Project build
environment. This command takes the build directory name as its parameter:
# source ./oe-init-build-env yocto_build
After this command runs, the current directory will now be the directory specified in the
parameter (yocto_build in this case). From this directory, run bitbake <target> to
build the root file system and kernel.
The SoC-specific <target> commands described below will determine whether the
resulting components are built for SPI flash or for SD/USB/eMMC (memory media). The
output is different for each target.
Note: Starting from Intel® Quark™ v1.1 release, it is possible to perform both (memory media
and SPI) build methods from the same directory. However, the user should take note of
the DISTRO setting in conf/local.conf file. For the memory media image, please make
sure DISTRO ?=”iot-devkit-multilibc” is uncommented only. For SPI image, please make
sure DISTRO ?= “iot-devkit-spi” is uncommented only. The output of the memory
media image is under yocto_build/tmp and the output of SPI image is under
yocto_build/tmp-spi.
6.1 Build a Full-featured Linux for SD card, USB stick or eMMC
Note: A Yocto Project build can take several hours to complete, depending on your internet
connection speed and your machine’s specifications.
To build an image suitable for running on memory media, set the bitbake target to
image-full:
# bitbake image-full
When the image build completes, the following output files are found in the
./tmp/deploy/images/quark/ directory. Copy these files to the media device.
Rename the files according to the following instructions (resulting paths are relative to
the media’s root path):
image-full-quark-YYYYMMDDhhmmss.rootfs.ext3
(Rename this file to image-full-quark.ext3 because the initramfs will look for the file
in that name, unless the configuration is updated).
core-image-minimal-initramfs-quark-
YYYYMMDDhhmmss.rootfs.cpio.gz
(Optional: rename this file to core-image-minimal-initramfs- quark.cpio.gz)
bzImage--3.14-r0-quark-YYYYMMDDhhmmss.bin
(Optional: rename this file to bzImage.bin)
grub.efi