doc: qsg: update with latest changes

.. _building_zephyr:

Building the Zephyr Kernel

############################

##########################

This section describes the procedure to build the kernel with a sample

application. in a development system and describes how to get access to the

application in a development system and describes how to get access to the

kernel's source code.

Building a Sample Application

.. code-block:: bash

   $ sudo yum update

   $ sudo dnf update

.. _required_software:

Installing the Zephyr Software Development Kit

==============================================

Zephyr's :abbr:`SDK (Software Development Kit)` provided by Yocto contains all necessary tools

and cross-compilers needed to build the kernel on all supported architectures.

Additionally, it includes host tools such as a custom QEMU and a host compiler for building host

tools if necessary. With this SDK, there is no need to build any cross compilers or

emulation environments. The SDK supports the following architectures:

Zephyr's :abbr:`SDK (Software Development Kit)` contains all

necessary tools and cross-compilers needed to build the kernel on all supported

architectures.

Additionally, it includes host tools such as a custom QEMU and a host compiler

for building host tools if necessary. With this SDK, there is no need to build

any cross compilers or emulation environments. The SDK supports the following

architectures:

* :abbr:`IA-32 (Intel Architecture 32 bits)`

Follow these steps to install the SDK on your host system.

#. Download the Yocto self-extractable binary from:

#. Download the SDK self-extractable binary from:

   https://zephyr-download.01.org/zephyr-sdk/zephyr-sdk-0.6-i686-setup.run

       Success installing SDK. SDK is ready to be used.

#. To use the Yocto SDK, export the following environment variables and

#. To use the Zephyr SDK, export the following environment variables and

   use the target location where SDK was installed, type:

    .. code-block:: bash

       $ export ZEPHYR_GCC_VARIANT=yocto

       $ export ZEPHYR_GCC_VARIANT=zephyr

       $ export YOCTO_SDK_INSTALL_DIR=/opt/zephyr-sdk/0.6

Installing a Custom QEMU for ARM Platforms

==========================================

The Yocto SDK comes with a QEMU binary suitable for running sample |codename|

The SDK comes with a QEMU binary suitable for running sample |codename|

applications. The steps below are needed only if you choose not to use the

provided binary and use a custom built binary instead.

If you require testing ARM builds, a localized patch to the QEMU source

If you require testing ARM builds, a local patch to the QEMU source

is needed. The patch corrects the issues with the locking interfaces

QEMU uses. If you are working with the x86 builds of the Zephyr kernel,

QEMU uses. If you are working with the x86 builds of the kernel,

install QEMU from your systems default package manager.

Follow these steps to enable a customized build of QEMU:

#. Clone the QEMU repository:

   .. code-block:: bash

      $ git clone git://git.qemu-project.org/qemu.git

.. toctree::

   :maxdepth: 2

   about_zephyr.rst

   installing.rst

   building.rst

   running.rst

**************************************

#. Set the platform configuration to Galileo by changing the :command:`make` command to:

#. Set the platform configuration to Galileo by changing the :command:`make`

   command to:

   .. code-block:: bash

#. Configure your host system to watch for serial data.

   * On Linux, minicom is a popular method for reading serial

   * On Linux, screen is a popular method for reading serial

      data.

   * On Windows, PuTTY has an option to set up configuration for

   .. code-block:: bash

      $ sudo yum install gnu-efi-i386 bison libopts25 \

      $ sudo dnf install gnu-efi-i386 bison libopts25 \

      libselinux1-dev autogen m4 autoconf help2man libopts25-dev flex \

      libfont-freetype-perl automake autotools-dev libfreetype6-dev texinfo

      $ configfile (hd0,msdos1)/efi/boot/grub.cfg

   The command uses the Galileo’s built-in GRUB to parse your config file

   The command uses the Galileo’s built-in GRUB to parse your configuration file

   and list the options you’ve set.