michaelh/zephyr
1
0
Fork 0
Code Releases Activity

doc: adding :dfn: syntax where needed

Browse source 
Updated as per Allan's comments to correct use of Zephyr
kernel in lieu of codename variable

Change-Id: Iaf5f8531c5452b6d8fb13318f00050aa63d99200
Signed-off-by: L.S. Cook <leonax.cook@intel.com>
This commit is contained in:
L.S. Cook 2015-10-08 14:13:05 -07:00 • committed by Anas Nashif
commit 86f851c55a
1 changed files with 23 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

45
doc/kernel/overview/system_fundamentals.rst
View file

@ -3,27 +3,28 @@
System Fundamentals
###################
A Zephyr *application image* is an executable file that controls the operation
of a hardware system, or a simulated system running under QEMU.
Each application image contains both application code and a complete Zephyr
kernel, which are compiled into a single, fully linked executable.
Once an application image has been loaded onto a target system, it takes
control of the system, initializes it, and runs forever as the system's sole
application. Both application code and kernel code execute as privileged code
within a single shared address space.
An :dfn:`application image` is a binary that controls the operation
of a hardware system, or of a simulated system running under QEMU.
Each application image contains both the application's code and the Zephyr
kernel code needed to support it. They are compiled as a single,
fully-linked binary.
A Zephyr *application* is a set of user-supplied files that the Zephyr
build system processes to generate an application image. The application
consists of application-specific code, a collection of kernel configuration
settings, and a Makefile. The application's kernel configuration settings
enable the build system to create a Zephyr kernel tailor-made to meet the
needs of the application and to make the best use of the system's resources.
Once an application image has been loaded onto a target system, the image takes control
of the system, initializes it, and runs forever as the system's sole application.
Both application code and kernel code execute as privileged code within a single
shared address space.
The Zephyr kernel supports a variety of target systems, known as *platforms*,
each of which has its own set of hardware devices and capabilities.
One or more *platform configurations* are defined for a given platform,
each of which indicates how the devices that may be present on the platform
are to be used by the kernel. The platform and platform configuration concepts
make it possible to develop a single Zephyr application that can be used by
a set of related target systems, or even target systems based on different CPU
architectures.
A :dfn:`application` is a set of user-supplied files that the Zephyr build
system processes to generate an application image. The application consists of
application-specific code, a collection of kernel configuration settings, and at
least one Makefile. The application's kernel configuration settings enable the build
system to create a kernel tailor-made to meet the needs of the application
and to make the best use of the system's resources.
The |codename| supports a variety of target systems, known as *platforms*;
each :dfn:`platform` has its own set of hardware devices and capabilities. One or more
*platform configurations* are defined for a given platform; each
:dfn:`platform configuration` indicates how the devices that may be present on the
platform are to be used by the kernel. The platform and platform configuration concepts
make it possible to develop a single application that can be used by a set of related
target systems, or even target systems based on different CPU architectures.