Intel Quark SoC X1000 User Manual page 16

Creating a file system and building the kernel using Yocto [Linux build environment only]
Two build methods are supported; the output is slightly different for each one. The
commands are different for the Intel
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
# source poky/oe-init-build-env yocto_build
# bitbake image-spi-galileo
For the Intel
include:

image-spi-galileo-clanton.cpio.gz

image-spi-galileo-clanton.cpio.lzma

bzImage

grub.efi
For other supported boards (not Intel
# 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
# source poky/oe-init-build-env yocto_build
# bitbake image-full-galileo
For the Intel
include:

image-full-galileo-clanton.ext3

core-image-minimal-initramfs-clanton.cpio.gz

bzImage

grub.efi

boot (directory)
For other supported boards (not Intel
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
Intel ® Quark™ SoC X1000
BSP Build and Software User Guide
16
® Galileo board, run:
® Galileo board, output files are found in ./tmp/deploy/images/ and
® Galileo board, run:
® Galileo board, output files are found in ./tmp/deploy/images/ and
® Galileo board.
® Galileo), run:
® Galileo), run bitbake image-full as
Order Number: 329687-007US